wds

All posts tagged wds

If you are like me using MDT 2012 Update 1, and recently decided to update old images with fresh install and latest Microsoft patches, there is a strong chance that you might run into following error during image deployment.Windows could not parse

Error is encountered during the processing of unattend.xml, more precisely on IE customization. It appears that IE10 does not support <IEWelcomeMsg>  tag  and that causes the whole deployment to hang. IEWelcomeMsg tag is present by default in unattend.xml file created by MDT 2012, so the solution is to either upgrade to MDT 2013 which has this issue resolved or to manually remove/comment this line.

You’ll find the unattend.xml file for each sequence under MDTDeploymentShare\Control\%Task Sequence ID%\

Just remove or comment the line like this:

<!-- <IEWelcomeMsg>false</IEWelcomeMsg> -->

I’ve ran in to the mentioned issue yesterday, our WDS stopped working just out of the blue. To make it more convenient , only few days after i experimented with PxeLinux one the WDS…

TFTP open timeout

After some googleing it turns out that culprit is the DNS server role located on the same box. Apparently DNS server is randomly allocating ports (2500 of them) in the range of 49152-65535 which can overlap with WDS range, which by default operates from 64001 to 65000.

On Server 2008 R2, the simple solution is to change dword value of “UdpPortPolicy” to 0 – located in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\WDSServer\Parameters.
Which will make WDS server check if the port is already in use before trying to use it.

There is no “UdpPortPolicy” parameter on Windows Server 2008, so the solution would be to broaden the port range of WDS server. You could do it through Server manager, under network properties of WDS server, or by command prompt
wdsutil /set-Server /Transport /StartPort:50000 /EndPort:65000

Microsoft KB article for more info: http://support.microsoft.com/kb/977512