Enterprise Batch OS Installation — WDS (Windows Deployment Services) Tutorial

The underlying principle is still PXE, but this time we leverage Microsoft's WDS (Windows Deployment Services). Compared to previous methods, this approach directly installs the OS image on client machines rather than restoring a system image. It works across different hardware configurations, regardless of UEFI or Legacy boot modes.

01 — What is WDS?

WDS (Windows Deployment Services) is Microsoft's batch deployment solution, still based on the PXE principle.

Think about it: normally we install systems using USB drives or optical discs step by step. But what if you need to install 50, 500, or even a whole building full of computers simultaneously? Installing one by one with USB drives is obviously impractical. With WDS, you can install systems on multiple machines at the same time. Combined with unattended answer files, you can achieve fully automated installation — from partitioning to activation, drivers, and office software — a true one-stop system deployment.

02 — Prerequisites for WDS Batch Installation

1. Client network cards must support PXE boot (PXE-capable NICs are now standard);

2. All computers and the server must be on the same local area network (LAN);

3. Router/switch must support DHCP, and only one DHCP server should exist on the LAN;

4. All computers must have IP addresses in the same subnet;

5. Since this is batch deployment, ensure adequate performance — router/switch/network environment/server configuration should not become bottlenecks.

03 — WDS Batch Installation Step-by-Step Guide

I'll include screenshots wherever settings need modification or attention. If no screenshot is provided for a step, the default settings can be used — simply click "Next."

The configuration parameters shown are for reference; adjust them to your needs. If this is your first time, I recommend following my settings to ensure a successful WDS deployment, then explore more customization once you understand the process.

3.1 Install Windows Server

Install Windows Server (2008/2012/2008R2/2012R2 — any will work). I'm using Windows Server 2012, which can be downloaded from MSDN. It's recommended to install it in a VMware virtual machine.

VMware virtual machine settings for Windows Server:

The VM network must be set to Bridged Mode. This way, the physical network adapter and virtual NIC are bridged through the VMnet0 virtual switch, placing them on the same subnet.

Once configured, power on the VM. Select the "Desktop Experience" installation option (GUI with Desktop), then wait for the automatic installation to complete. Restart when prompted, then log in with the password you set.

3.2 Copy the OS ISO to the VM

Drag and drop (or copy) the OS image you want to deploy into the virtual machine and mount it.

If copy/paste doesn't work, go to VMware menu → VM → Install VMware Tools.

3.3 Install DHCP Server and WDS Roles

Install the required roles: DHCP Server and Windows Deployment Services.

After installation, you'll see both services in the Server Manager dashboard. Now we need to configure them.

3.4 Configure DHCP

3.5 Configure WDS

3.6 Add Boot and Install Images

Locate the mounted ISO in Computer → DVD Drive → sources folder. You'll find two .wim files:

• install.wim — the installation image
• boot.wim — the boot image

Adding install.wim:

Adding boot.wim:

Configure WDS properties to streamline batch deployment operations:

Finally, start WDS:

3.7 Client PXE Boot Test

Configure the client machine to PXE boot (set Network Boot in BIOS), then test if WDS is working.

After PXE boot, the client will automatically fetch the image from the server and begin the setup process. Basic information will still need to be entered manually since we haven't configured an unattended answer file yet.

---

That covers the basic WDS deployment workflow. If you've used RIS (Remote Installation Service, WDS's predecessor), getting started with WDS should be very familiar. This tutorial only covers WDS's fundamental features. To unlock its full potential, combine WDS with unattended answer files for a truly hands-free, one-stop system deployment.