WDS TFTP Error (WDS PXE-E32)

If you have a 2008R2 or 2008 server running WDS and DNS, you may run into an issue where the client boots, gets an IP address but fails to load the PXE environment with the error: WDS PXE-E32: TFTP open timeout.

This issue can be caused by the DNS service binding to WDS UDP ports on the server. This will generally occur after security update MS08-037 is installed on the server.

To fix this, follow these steps:

1.Start Registry Editor. To do this, click Start , type regedit in the Start Search box, and then press ENTER.
2.Navigate through the regisrty to find the key:
HKEY_LOCAL_MACHINESystemCurrentControlSetServicesWDSServerParameters.
3.Right-click UdpPortPolicy, and then click Modify.
4.In the Value data box, type 0, and then click OK.
5.Close the registry editor.
6.Open the Windows Deployment Services (WDS) snap-in and restart the WDS server.

Bootstrap.ini

[Settings]
Priority=Default
[Default]

SkipBDDWelcome=YES
DeployRoot=\\Server\DeploymentShare$
UserID=SA_mdt
UserDomain=yourdomain
UserPassword=Password

Customsettings.ini

[Settings]
Priority=Default
Properties=MyCustomProperty

[Default]
OSInstall=YES
_SMSTSORGNAME=YourCompany Deployment
SkipCapture=NO
SkipAdminPassword=YES
SkipProductKey=YES
SkipDeploymentType=NO
DeploymentType=Newcomputer
SkipDomainMembership=YES
JoinDomain=yourdomain
DomainAdmin=Admin
DomainAdminDomain=yourdomain
DomainAdminPassword=Password
SkipUserData=YES
SkipBuild=NO
SkipComputerName=YES
SkipPackageDisplay=NO
SkipLocaleSelection=YES
SkipTimeZone=YES
SkipApplications=NO
SkipBitLocker=YES
SkipBitLockerDetails=YES
SkipSummary=YES
SkipFinalSummary=YES
UserDataLocation=NONE
SkipAppsOnUpgrade=YES
TimeZoneName=W. Europe Standard Time
TimeZone=110
AreaCode=0413
UserLocale=nl-NL
Language=00000413
SystemLocale=00000413
UserLocale=00000413
InputLocale=0413:00020409
InputLocale=nl-US
KeyboardLocale=nl-US
WSUSServer=http://wsus
FinishAction=REBOOT

Replace WDS Boot images

When you regenerate boot images from MDT you have to replace the images in WDS.
Right click Boot Images --> Replace Image

The default location is \Deploymentshare\Boot

Deploying A Captured Image

Deploying A Captured Image

Once your capture has finished you will need to add the created .wim file to your operating systems node
Right click on the operating system node and select Import Operating System and select the Custom image file option.

A common question about captured images is: why creating a new .wim file? The reason is simple the deployment of the newly created image is quicker than installing a default .wim image. A standard .wim installation with security essentials & pdf reader takes 27min. A custom made image with the same settings and applications takes 19min. When you update your image with the latest windows updates and additional applications the difference will be bigger. 

Browse for the location of the captured file(normally in a folder called captures in the deployment share) and put a tick in the move the files option (this saves on disk space by moving the file and not copying it).

• Select the option to copy the windows setup files and browse for the location of the original source files you copied to the server.
• Specify a name for the destination directory.
• Check the summary screen and click Next to import the captured image
• Once the import is complete you will need to f create a new task sequence to deploy your newly imported image.
• You are now able to boot your computers to the network and using MDT 2010 to deploy your captured image.

Capturing a Reference Image - Deploying Windows 7

Deployment Share Rules

Right click on the Deployment Share and select Properties

 

Select the Rules tab and ensure that the Skip Capture rule is set to NO

If you have to change this rule then you need to update the deployment share and completely regenerate the boot images.

Once the boot images have been regenerated then you will need to replace your current boot images in Windows Deployment Services with the newly regenerate ones

Capture Task Sequence

The next step is to create a task sequence that will capture an image from your reference computer.

Right click on the task sequence node and select New Task Sequence.

1. Complete all the information to identify this task sequence.
2. Select Sysprep and Capture from the drop down menu.
3. Select the operating system that will be used (this will not effect the image being captured).
4. After accepting the defaults on the next screen complete all the relevant details on the OS settings screen.
5. Enter a password for the local administrator and click Next.
6. At the last screen check the summary and click Next to complete the task sequence.