Windows Server

Windows – Slipstream Windows Server in 3 simple steps

Posted in Microsoft, Windows Server on March 1st, 2010 by Ryan Lowdermilk – Be the first to comment
  1. Copy “i386” folder from Windows CD/DVD folder to C:\
  2. Copy the service pack .exe (filenames differ with varying service packs) to C:\service_pack and run c:\service_pack\servicepack.exe /x
  3. Run c:\service_pack\update\update.exe /s:c:\

Bonus Steps – Change the default installation location i.e. the prompt for the Windows CD

  1. From a command line:
    reg add "HKLM\Software\Microsoft\Windows NT\CurrentVersion" /v "SourcePath" /d c:\i386
  2. One more, from a command line:
    reg add "HKLM\Software\Microsoft\Windows\CurrentVersion\Setup" /v "SourcePath" /d c:\i386

Windows – Directory Listing to CSV

Posted in Microsoft, Windows Server on March 1st, 2010 by Ryan Lowdermilk – Be the first to comment

I have been performing a lot of system administration tasks as of late. I needed to create a quick report which displayed all subdirectories and files on an FTP server. Additionally, the report needed to have the ability to be “sliced and diced” – by user, file extension, created date, etc. Jam Software to the rescue. Their FileList command line application worked like a charm. You can find FileList and some other great tools they have created here.

Microsoft DirectAccess Connectivity Assistant

Posted in Microsoft, Windows Server on February 17th, 2010 by Ryan Lowdermilk – Be the first to comment

For those of you deploying Microsoft DirectAccess, Microsoft just released a new Connecitivty Assistent which boasts the following features:

  • Informs mobile users of their connectivity status at all times
  • Provides tools to help them reconnect on their own if problems arise
  • Runs diagnostics to help mobile users provide IT staff with key information if necessary—all to help customers operate with more efficiency, and at a lower cost.

Download Here

Windows – Disable IPv6 including 6to4, Terredo and ISATAP adapters

Posted in Microsoft, Windows Server on October 9th, 2009 by Ryan Lowdermilk – Be the first to comment

Perfect article on how to disable IPv6 on Windows including those pesky Terredo and 6to4 adapters. It was driving my nuts to see IPv6 entries in my DNS. Yes, my OCD is THAT bad.

Quick Steps:

  1. Download this
  2. Copy to all your domain controllers.
  3. Place the ADMX file under %SYSTEMROOT%\PolicyDefinitions
  4. Place the ADML file under %SYSTEMROOT%\PolicyDefinitions\en-US
  5. From one of the domain controllers, open Group Policy Management and create a new GPO. I created a domain level GPO. I don’t want any machine on the domain talking IPv6 (sorry).
  6. A smidge out of order, but, next, let’s write a quick Startup script. This script will copy the the ADMX and ADML files to the other machines on the domain.
  7. From one of the domain controllers, navigate to %SYSTEMROOT%\SYSVOL\sysvol\{domain}\Policies\{GUID}\Machine\Scripts\Startup. NOTE: You can grab the GUID by clicking on the new GPO and clicking the “Details” tab on the right under Group Policy Management.
  8. Create a new batch file with the following contents. NOTE: You have to change some of the values to match your environment.
  9. @echo off
    copy /y \\Arxdc01\sysvol\arxis.local\Policies\{5D4BA0A1-4932-4377-9F7E-05727A9295BF}\Machine\Scripts\Startup\IPv6Configuration.admx %SYSTEMROOT%\PolicyDefinitions
    copy /y \\Arxdc01\sysvol\arxis.local\Policies\{5D4BA0A1-4932-4377-9F7E-05727A9295BF}\Machine\Scripts\Startup\IPv6Configuration.adml %SYSTEMROOT%\PolicyDefinitions\en-US

  10. Copy the ADML and ADMX files and place them in the same folder with the login script.
  11. Edit the new GPO and find the new settings under Computer Configuration > Policies > Administrative Templates > Network > IPv6 Configuration >> Enable and choose your setting.
  12. Edit the new GPO and find the Startup script setting under Computer Configuration >> Policies >> Windows Settings >> Scripts. Add the script file.
  13. Reboot machines
  14. Type ipconfig
  15. Wooo hoo! :)

Microsoft – HOWTO Windows 2008 Server Failover Clustering with VMWare Step by Step

Posted in Microsoft, VMWare, Windows Server on October 7th, 2009 by Ryan Lowdermilk – Be the first to comment

Create the Shared Disk

  1. Create a VM (don’t worry we are going to delete it, we just need the disk) 
    1. Name: “VMCLUSTERSTORAGE”
    2. Guest Operating System: "Windows 2003 Server” (doesn’t really matter)
    3. Virtual Disk:
      1. Size: whatever
      2. DO NOT Check Allocate and commit space on demand (shared disks need to be thick NOT thin)
      3. Check Support clustering features such as Fault Tolerance (required if you want to share the disk)
    4. Right click new VM Remove from Inventory
    5. Browse Datastore >> Browse to new VM >> Delete all files but the VMDK file

Attach the Shared Disk to each VM

  1. On each VM – Edit Settings >> Add >> Hard Disk >> Use Existing >> Browse to shared VMDK file
  2. Choose new SCSI bus i.e. 1:0, 2:0,3:0, etc.
  3. Change SCSI Controller to Paravirtual

Configure each Windows 2008 Server VM

  1. My Computer >> Manager
  2. Right click disk >> Online >> Initialize Disk >> Format >> NTFS
  3. Install File Services Role on each Windows 2008 Server VM
  4. Install Failover Clustering on each Windows 2008 Server VM
  5. Open Failover Clustering Management
  6. Validate each Windows 2008 Server VM
  7. Create Cluster
  8. Add Application / Services