Deploying Images with WDS
Once the environment is setup with Windows Deployment Services, a reference machine has been created, and an image of it is available for deployment, you are ready to start deploying it to other machines. There are three basic methods to accomplish this through WDS:
Manual Deployment: It is possible to use this method for deploying into a single machine, though it is tedious for deploying into a large set of machines.
Unattended Deployment. This method automates the Windows Deployment Services client and the latter stages of Windows Setup. This two-stage approach is accomplished by using two different unattend files:
a. Windows Deployment Services client unattend file: This file uses the Unattend.xml format and is stored on the Windows Deployment Services server in the \WDSClientUnattend folder. It is used to automate the Windows Deployment Services client user interface screens (such as entering credentials, choosing an install image, and configuring the disk).
b. Image unattend file: This file uses the Unattend.xml or Sysprep.inf format, depending upon the version of the operating system in the image. It is stored in a subfolder (either $OEM$ structure or \Unattend) in the per-image folder. It is used to automate the remaining phases of setup (for example, offline servicing, Sysprep specialize, and mini-setup).
Multicast Transmission Deployment. Multicast transmissions allow you to deploy an image to a large number of client computers without overburdening the network. When you create a multicast transmission, the image is sent over the network only once, which can drastically reduce the network bandwidth that is used.
You can also deploy images through Microsoft Deployment or SCCM.