How do I use MDT with WDS (Windows Deployment Services)?

by · Published · Updated

Applies to: Microsoft Deployment Toolkit (MDT) 8456 and Windows Deployment Services (WDS)
Last updated: May 2025

Problem

You want to deploy operating systems over the network using PXE boot, allowing machines to boot into MDT Lite Touch without USB drives or ISO files.

Solution

Integrating MDT with WDS allows you to boot into the MDT LiteTouchPE image using PXE. This provides a seamless and scalable way to deploy Windows across a network.

Step-by-Step Guide

1. Install Windows Deployment Services

On your MDT server (or another server):

  1. Open Server Manager
  2. Go to Add Roles and Features
  3. Install Windows Deployment Services
    • Ensure both Deployment Server and Transport Server roles are selected
  4. After installation, configure WDS:
    • Choose Integrated with Active Directory
    • Set up RemoteInstall folder on a non-system drive if possible

2. Update the MDT Deployment Share

In Deployment Workbench:

  • Right-click your Deployment Share > Update Deployment Share
  • This regenerates the LiteTouchPE_x64.wim and .iso boot images in:
<DeploymentShare>\Boot\

3. Import Boot Image into WDS

  1. Open the WDS console
  2. Expand your server > Boot Images
  3. Right-click > Add Boot Image
  4. Browse to:
<DeploymentShare>\Boot\LiteTouchPE_x64.wim
  1. Give it a name like MDT LiteTouch x64
  2. Finish the wizard

Repeat with LiteTouchPE_x86.wim if you support 32-bit machines.

4. Enable PXE Boot and Test

  • Ensure DHCP is working on the same subnet
  • In WDS, right-click the server > Properties > PXE Response tab:
    • Select Respond to all client computers
    • Optionally require admin approval for unknown clients

Boot a test machine to the network (PXE):

  • It should load the LiteTouchPE image
  • MDT Deployment Wizard will start automatically

Optional: Automate PXE Boot Behavior

To fully automate deployments via PXE:

  • Customize bootstrap.ini and customsettings.ini to skip prompts
  • Set SkipBDDWelcome=YES, TaskSequenceID, and OSDComputerName in rules

Notes

  • The .wim file from MDT must be re-imported to WDS if updated
  • WDS and DHCP should be on the same server or configure DHCP options 66 and 67
  • WDS logs and event viewer can help diagnose PXE boot issues

Tags:

You may also like...