This is a step by step explanation of what I have done to setup Windows Deployment Services(WDS) in my work environment. I have generalized a few steps to make it generic enough to work in any environment with a few tweaks here and there. In this post, I assume you have Active Directory and a Windows DHCP server deployed. I am also assuming you have a good familiarity with Windows Server 2008.
Step 1
Add the Windows Deployment Service Role using the Server Manager Tool.
Windows Deployment Services is the only server role that needs to be selected.
Choose both Deployment Server and Transport Server from the Role Services screen.
Step 2
Initialize the WDS server using the following command:
wdsutil /initialize-server /reminst:C:\RemoteInstall
Use the wdsutil command to initialize the server and set the Remote Install path.
Step 3
Configure the WDS Properties. I only needed to change the settings in the “PXE Response Settings” and “Advanced” tabs.
Change the response policy to accept all client computers. You can further restrict this after WDS is confirmed working in this same tab.
Select "Authorize this Windows Deployment Services server in DHCP".
Apply the changes and click OK to complete. At this point you may want to restart the WDS services or simply reboot the server.
Step 4
In order for the client computer to find the WDS server during a PXE boot, you may need to setup an ip-helper address in on your switch/router. This enables the PXE broadcast to be seen by the WDS server if it is on a different subnet/VLAN. On a Cisco device you can use:
config t
interface [VLAN Interface ID]
ip helper-address [IP of WDS server]
exit
Related posts:
