How to Use Windows Server WDS (Windows Deployment Services) to Image Computers

If you are an IT administrator tasked with provisioning 50 new laptops for the marketing department, installing Windows from a USB drive on every single machine is an agonizing waste of time. To scale Windows deployments across a corporate network efficiently, you must use Windows Deployment Services (WDS). WDS allows bare-metal computers to boot directly from the network card, pull a pristine, pre-configured Windows image from your server, and install it entirely over the network.

Prerequisites for WDS

WDS does not operate in a vacuum. Before installing the role, your network must have:

1. Active Directory (AD DS): While WDS can technically run standalone, it is designed to integrate heavily with AD for computer naming and domain joining.
2. DHCP: When a blank computer boots up, it uses PXE (Preboot Execution Environment) to broadcast for an IP address. You must have an active DHCP server to hand it an IP so it can talk to the WDS server.
3. DNS: Required for the network boot process to resolve the domain.

Step 1: Install the WDS Role

1. Open Server Manager on your Windows Server.
2. Click Add roles and features.
3. Click Next until you reach the Server Roles screen.
4. Check the box for Windows Deployment Services. Accept the prompt to add the necessary management features.
5. Click Next through the remaining screens and click Install.

Step 2: Configure the WDS Server

Once installed, WDS requires an initial setup.

1. In Server Manager, click Tools > Windows Deployment Services.
2. Expand the Servers folder, right-click your server name, and select Configure Server.
3. Choose Integrated with Active Directory.
4. Remote Installation Folder Location: Choose a path (e.g., D:\RemoteInstall). Crucially, this must be on an NTFS partition, and it should NOT be on your C: drive, as OS images take up massive amounts of space.
5. PXE Server Initial Settings: This determines which computers the server will respond to. For maximum security, choose Respond only to known client computers (which requires pre-staging MAC addresses in AD). For faster deployments, choose Respond to all client computers (known and unknown), but check the box that says Require administrator approval so rogue devices can’t pull an image without your permission.

Step 3: Add a Boot Image

Before a computer can install Windows, it needs a tiny operating system just to run the setup menu over the network. This is the Boot Image (usually Windows PE).

1. Mount a Windows 10 or Windows 11 ISO on your server (or insert the DVD).
2. In the WDS console, right-click the Boot Images folder and select Add Boot Image.
3. Browse to the mounted ISO, open the Sources folder, and select boot.wim.
4. Name it something descriptive (e.g., “Windows 11 Setup (x64)”).

Step 4: Add an Install Image

The Install Image is the actual massive operating system that will be permanently copied to the laptop’s hard drive.

1. Right-click the Install Images folder and select Add Install Image.
2. You will be prompted to create an Image Group (e.g., “Windows 11 Corporate”).
3. Browse to the same mounted ISO, go to the Sources folder, and select install.wim.
4. A single install.wim file often contains multiple editions of Windows (Home, Pro, Education). Check the box only for the edition you hold licenses for (e.g., Windows 11 Pro).

Step 5: PXE Boot a Client Computer

Your server is now ready. Take a blank laptop and plug it into the network via an Ethernet cable (PXE over Wi-Fi is generally unsupported).

1. Turn the laptop on and immediately press the key to enter the boot menu (often F12, F9, or Enter, depending on the manufacturer).
2. Select Network Boot (or PXE IPv4).
3. The laptop will get an IP from DHCP and then display a message: “Press F12 for network service boot.” You must press F12 quickly.
4. The laptop will load the boot.wim file over the network, displaying a Windows loading screen.
5. You will be prompted to enter domain administrator credentials. Once authenticated, you simply select your “Windows 11 Corporate” image, and WDS handles the rest, wiping the drive and deploying the OS seamlessly.