1. [ Server 2012 R2, 20411D Taught by Jawad Safari ]
October 14 2015
Submitted by Ratan Mohapatra
A Class Project in Windows Deployment Service
Part 1: Adding Images from an Installation Media to a WDS Server
#Disk Management (Add an extra disk for storing images):
Get-Disk | Where-Object IsOffline -EQ $true | Set-Disk -IsOffline $false
Get-Disk -Number 1 | Set-Disk -IsReadOnly $false
Get-Disk -Number 1 | Clear-Disk -RemoveData
Initialize-Disk -Number 1 -PartitionStyle MBR
New-Partition -DiskNumber 1 -UseMaximumSize -AssignDriveLetter | Format-Volume `
-NewFileSystemLabel "WDSdata" -FileSystem NTFS
Install-WindowsFeature DHCP, DNS, WDS -IncludeManagementTools -IncludeAllSubFeature
Ratan Mohapatra 10/10/15 Page 1 | of 9

2. Configure the above installed server roles.
Note: When I configured the WDS as a Stand Alone server to use the second drive it gave error
“Improper Drive Syntax” -I restarted the VM and it was alright!
Make sure the click the
● Don not listen on DHCP and DHCPV6 ports
● Configure DHCP options for proxy
At the end the following message:
Right click on the Server > All Tasksstart to start the service
wdsutil /set-server /AutoAddPolicy /Message:"Your Request is being authorised. Please wait."
Ratan Mohapatra 10/10/15 Page 2 | of 9

3. Import (Add) the images:
Import the files Boot.wim and Install.wim from a Windows 2012 R2 ISO file (DVD) from the Sources
folder into the Boot Images and Install Images folders in WDS by right click and Add. Before adding
installation images an Image Group was created.
The above was redone with the help of the following Script:
# Add Images:
#Boot Image (Both wsutil and PS were tried)
#wdsutil /verbose /progress /add-image /imagefile:"d:sourcesboot.wim" /imageType:boot
Import-WdsBootImage -path "d:sourcesboot.wim" -NewImageName "Win2012Boot" `
-NewDescription "Windows Setup 64Bit"
#Install Images
New-WdsInstallImageGroup -Name "WinServer 2012R2"
Get-WindowsImage -Image "D:Sourcesinstall.wim"
Import-WDSInstallImage -Path "D:Sourcesinstall.wim" -ImageGroup "WinServer 2012R2" `
-ImageName "Windows Server 2012 R2 SERVERDATACENTER" -skipverify
● These images were used for the installation of Server 2012 R2 on another VM by PIXE Boot
that used a Synthetic Nework Adapter. Please note that in 2012 R2 you do not require to use
a Legacy Adapter for PIXE Boot.
● As part of the class project the images were used for successful installation on two physical
machines that were connected to the Virtual WDS Server (RM2) by a switch.
Ratan Mohapatra 10/10/15 Page 3 | of 9

4. Part 2: Capture Image:
● A capture image was created by using the Boot image in the image store by right click on the
image. Sore the file in a different name in the RemoteInstallBootx64images folder
● The reference server was PIXE boot with the above image to capture the Syspreped OS
Ratan Mohapatra 10/10/15 Page 4 | of 9

5. The infamous Error (seems like MS has a KB patch)!
Ratan Mohapatra 10/10/15 Page 5 | of 9

6. Seems like this is Bug. As suggested by Joe I just mount and unmout the image that crated the new
BCD
Dism /Mount-Image /ImageFile:"E:RemoteInstallBootx64Imagesboot_Capture.wim" /index:1
/MountDir:"E:RemoteInstallmount"
Dism /unmount-Image /mountdir:"E:RemoteInstallmount" /commit
Ratan Mohapatra 10/10/15 Page 6 | of 9

7. Ratan Mohapatra 10/10/15 Page 7 | of 9

8. Ratan Mohapatra 10/10/15 Page 8 | of 9

9. Added the image to a new VM:
Ratan Mohapatra 10/10/15 Page 9 | of 9