Windows Deployment Services Notes

Windows Deployment Services (WDS) enables you to deploy Windows operating systems over the network, which means that you do not have to install each operating system directly from a CD or DVD.

Below are my notes to prepare the WDS server and install/configure the WDS feature on a Windows 2016 server

Prepare WDS Server

  • Prepare a Windows 2016 server with an additional disk (D: drive) of 100 GB
  • Change Drive letter of the CD-ROM to Z:
  • Create directories for Windows 10 images
    • D:\iso\win10-1803
    • D:\iso\win10-1903
  • Mount Win 10 images
    • Mount a Win10 (1803) ISO Image (will be mounted on E: drive)
    • Mount a Win10 (1903) ISO Image (will be mounted on F: drive)
  • Copy files
    • copy all files form E: to D:\iso\win10-1803 or D:\iso\win10-1803
    • copy all files form F: to D:\iso\win10-1903 or D:\iso\win10-1903
  • Create directories to store for driverpacks
    • D:\Driverpacks\Dell_Optiplex_3070
    • D:\Driverpacks\Dell_Optiplex_5070
  • Download Windows 10 driver packs
    • for Dell Optiplex 3070: to D:\Driverpacks\Dell_Optiplex_3070
    • for Dell Optiplex 5070 from to D:\Driverpacks\Dell_Optiplex_5070
  • Open a command prompt as administrator
    • EXPAND D:\Driverpacks\Dell_Optiplex_3070\3070-win10-A00-4GJTC.CAB /F:* D:\Driverpacks\Dell_Optiplex_3070
    • EXPAND D:\Driverpacks\Dell_Optiplex_5070\5070-win10-A00-4GJTC.CAB /F:* D:\Driverpacks\Dell_Optiplex_5070
  • Set an IPHelper to the IP address of the WDS Server

Install WDS

Open a powershell command (as admin)

  • Install-WindowsFeature wds-deployment -includemanagementtools
  • wdsutil /Initialize-Server /REMINST:”D:\RemoteInstall”
  • Import-WdsBootImage -NewImageName “Windows 10 Enterprise 1803” -NewDescription “Windows 10 Enterprise 1803” -Path “D:\iso\win10-1803\sources\boot.wim”
  • Import-WdsBootImage -NewImageName “Windows 10 Enterprise 1903” -NewDescription “Windows 10 Enterprise 1903” -Path “D:\iso\win10-1903\sources\boot.wim”
  • New-WdsInstallImageGroup -Name “Desktops”
  • Note: “Get-WindowsImage -imagePath “D:\iso\win10-1803\sources\install.wim” | select Imagename: lists the images available in the and needs to be used as “ImageName” when importing an image with command “Import-WdsInstallImage”
  • Import-WdsInstallImage -ImageGroup “Desktops” -ImageName “Windows 10 Enterprise” -NewImageName “Windows 10 Enterprise 1803” -NewDescription “Windows 10 Enterprise 1803” -Path “D:\iso\win10-1803\sources\install.wim”
  • Import-WdsInstallImage -ImageGroup “Desktops” -ImageName “Windows 10 Enterprise” -NewImageName “Windows 10 Enterprise 1903” -NewDescription “Windows 10 Enterprise 1903” -Path “D:\iso\win10-1903\sources\install.wim”
  • wdsutil /Set-Server /AnswerClients:All /ResponseDelay:5 /PendingDevicePolicy /Policy:Disabled /NewMachineNamingPolicy:PCWIN10-%03# /NewMachineOU /Type:Custom /OU:OU=Deploy,DC=yourdomain,DC=com /PxePromptPolicy /Known:OptIn /New:Noprompt /Transport /ObtainIpv4From:Dhcp /Authorize:Yes /PortPolicy:Fixed /StartPort:64001 /EndPort:65000
  • Copy C:\Windows\System32\RemInst\boot\x64\wdsmgfw.efi to D:\RemoteInstall\Boot\x64 ==> this is due to a bug in WDS install

Add driver packages for all models (Each in its own driver group)

Add driver packages to boot image (Use the default Settings)


Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.