How to Deploy Windows Using Windows Deployment Services

Deploying Windows across multiple computers in an organization manually can quickly become tedious. That’s where Windows Deployment Services (WDS) steps in. WDS is a role in Windows Server that automates Windows installations over a network, removing the need for DVDs or USBs at each machine.

This guide walks through how to use WDS for network-based deployments, from prerequisites to full image deployment.

What Is Windows Deployment Services (WDS)?

WDS enables Preboot Execution Environment (PXE) booting, allowing clients to boot from the network and install Windows OS images hosted on a central server. Here’s how it works at a high level:

1. Client boots via PXE.
2. Gets an IP address from a DHCP server.
3. DHCP points to the WDS server.
4. WDS delivers a boot image.
5. Client boots into WinPE and selects an install image.
6. WDS deploys the OS to the client.

Key Components

• WDS Server: Hosts boot/install images and provides PXE services.
• Active Directory (AD DS): Often required unless using standalone mode.
• DHCP: Provides IP addresses; must be on the same network.
• DNS: Required for network name resolution.
• .WIM Files: Windows images used for deployment.

Prerequisites

• Windows Server (2016/2019/2022).
• AD DS (domain membership).
• DHCP and DNS configured.
• NTFS-formatted partition for image storage (e.g., 50-100GB+).
• Admin privileges.
• Official Windows ISO files.

Step-by-Step: Set Up WDS

Step 1: Install WDS Role

1. Open Server Manager.
2. Click Manage > Add Roles and Features.
3. Choose Role-based or feature-based installation.
4. Select your server.
5. Check Windows Deployment Services.
6. Ensure both Deployment Server and Transport Server are selected.
7. Click through to install.

Step 2: Configure WDS

1. Open WDS console from Server Manager > Tools.
2. Right-click your server name > Configure Server.
3. Choose Integrated with Active Directory.
4. Choose an NTFS folder for RemoteInstall (e.g., D:\RemoteInstall).
5. DHCP configuration:
   • If on same server: Check both PXE-related options.
   • If separate: Leave unchecked.
6. PXE settings: Choose how WDS responds (e.g., all clients or known only).
7. Finish and start the WDS service.

Step 3: Add Boot Images

1. Mount your Windows ISO.
2. Go to \Sources\boot.wim.
3. In WDS, right-click Boot Images > Add Boot Image.
4. Point to boot.wim, give it a name/description, and add it.

Step 4: Add Install Images

1. Find install.wim or install.esd in the ISO \Sources folder.
2. In WDS, right-click Install Images > Add Install Image.
3. Create/select an image group.
4. Select the .wim/.esd file.
5. Choose Windows editions to add (e.g., Pro, Enterprise).
6. Finish the wizard.

Step 5: Configure Client PXE Boot

1. Enter BIOS/UEFI on client PC.
2. Enable Network Boot / PXE Boot.
3. Set boot order to prioritize network.
4. Save and reboot.

Step 6: Deploy Windows

1. Client boots via PXE and connects to WDS.
2. Downloads boot image and launches Windows Setup.
3. Select language, layout, and login if needed.
4. Pick an install image.
5. Proceed with Windows installation.

Advanced Features (Optional)

• Driver Injection: Add drivers to boot/install images.
• Unattended Installations: Use unattend.xml to automate installs.
• Capture Images: Create custom Windows images from a reference PC.
• Multicast Deployments: Save bandwidth when deploying to many PCs.
• Security Controls: Limit to known devices or require admin approval.

Final Thoughts

WDS dramatically reduces the overhead of installing Windows across multiple systems. With careful setup and planning, you can deploy clean, consistent OS installations from a central server, improving both efficiency and standardization.