Troubleshooting advertisements stuck in - Waiting for content

Sometimes an Advertisement gets stuck in Waiting state, like this:

Upon viewing the execmgr.log file, you may see this line:

And, in the contentTransfermgr.log, you can see this line:

Cause:

This is due to some error in BITS transfer from the DP to the client cache.

Resolution:

1.     First disable BITS on the DP from where the client is downloading the content (you can get this from datatransferservice.log).

2.     Wait for 10 minutes for changes to take effect.

3.     Reset the policies on the client (use SCCM Client Center->Policy Reset (Hard-Reset)).

4.     Delete the cache folder for that advertisement.

5.     Request the Machine Policy.

6.     Rerun the Advertisment.

7.     Check the execmgr.log for success.

8.     To rerun the Advertisement on ALL the failed computers, create a new Program with same settings and rerun the Advertisement,

Error - PXE test request failed, status code is -2147467259, 'Error receiving replies from PXE server'.

Sometimes, after your configure WDS on a secondary site server, and then enable PXE role on it, you get the above error in the pxecontrol.log file.


And, the wdsserver service will also not start (error code 87).

Solution:

Change the below regitry key

HKLM\SYSTEM\CurrentControlSet\Services\WDSServer\Providers\WDSPXE\IsCritical from 1 to 0

If you get  error code 10048 while starting the wdsserver service, then do the following:

1. Click Start, click Run, type wdsmgmt.msc, and then press OK.
2. In the Windows Deployment Services window, expand Servers, right-click the WDS server name, and then click Properties.
3. In the Server Properties dialog box, click the DHCP tab.
4. Click to select the Do not listen on port 67 check box, and then click Apply.