Re-installing WDS in Windows 2003 for Mixed Mode

  • Article

1. Run the following command from a CMD prompt and save the results for later reference:

WDSUTIL /get-server /show:config

2. Stop the WDS Service. To do this, run the following command from a CMD prompt:

net stop wdsserver

3. Rename the “Remote Install” folder (R:\RemoteInstall). You will received a message that the share will be lost. That is OK.

4. Go to Add or Remove Programs control panel and click Add/Remove Windows Components and click Windows Deployment Services to clear and uninstall the WDS component.

5. Go to Add or Remove Programs control panel and click Add/Remove Windows Components and click Windows Deployment Services to select and install the WDS component.

WARNING: Make sure that you are installing Windows files from a Windows Server 2003 with Service Pack 2 (SP2) media source. This is very important for WDS and RIS to function properly.

6. Restart Windows (if prompted).

WARNING: Do not launch and configure WDS using the "Windows Deployment Services" MMC. If you do, WDS will be in Native mode and you will not be able to access your legacy images.

7. Launch RISetup ("Windows Deployment Services Legacy") and click Next and specify your original remote install path and click Next and import a legacy OS. You will need to use any Windows XP or Windows Server 2003 media. This must be done to allow us to get back into WDS Mixed mode and we can delete this added image later.

8. Run the following command from a CMD prompt to change the mode of WDS to Mixed Mode:

WDSUTIL /Initialize-Server /REMINST:"R:\RemoteInstall"

Considering R:\ is your resource directory

9. Now, stop the WDS service:

net stop wdsserver

10. Rename the R:\RemoteInstall\OSChooser folder and the R:\RemoteInstall\Setup folder and copy back from your backup (which is the folder renamed from step 3).

11. Start the WDS service:

net start wdsserver

You should have all the images back.

12. Now you can open the WDS MMC and add your Windows PE images as a boot images and configure other settings which you noted from step 1.

Disclaimer: The information on this site is provided "AS IS" with no warranties, confers no rights, and is not supported by the authors or Microsoft Corporation. Use of included script samples are subject to the terms specified in the Terms of Use .