We are seeing issues with PXE when we try to rebuild a host, we get an error "No response from Windows Deployment Services server"
What we are seeing is, the first time you try to build a machine, it goes through fine, in the SMSPXE log -
C8:1F:66:FA:85:19, 4C4C4544-004D-4E10-804D-B5C04F563132: device is in the database.
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16778461" ServerName=""><Machine><ClientID>GUID:D53F894A-6A5A-4FDA-A1E0-485B3B208DDA</ClientID><NetbiosName/></Machine></Identification><PXEBootAction
LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="AAA20154" OfferIDTime="1/1/1990" PkgID="AAA012E6" PackageVersion="" PackagePath="http://SCCMServer/SMS_DP_SMSPKG$/AAA01252"
BootImageID="AAA01252" Mandatory="1"/></ClientIDReply>
C8:1F:66:FA:85:19, 4C4C4544-004D-4E10-804D-B5C04F563132: using advertisement AAA20154
Looking for bootImage AAA01252
C8:1F:66:FA:85:19, 4C4C4544-004D-4E10-804D-B5C04F563132: Updating Device Cached LastAdv Time. Time=19/08/2014 18:23:35 LastAdvID=AAA20154
If we want to rebuild the same box one more time - we delete the machine from SCCM and import as a new machine, but it fails to PXE. We see the Deployment in the properties of this box in SCCM Console. We get the below -
Downloaded WDSNBP from 10.10.10.10
Contacting Server: 10.10.10.10 (Gateway: 2.2.2.2)..
No response from Windows Deployment Services server
Launching pxeboot.com...
In the SMSPXE logs -
Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="16778470" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
C8:1F:66:FA:85:19, 4C4C4544-004D-4E10-804D-B5C04F563132: device is in the database.
Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="16778470" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
C8:1F:66:FA:85:19, 4C4C4544-004D-4E10-804D-B5C04F563132: device is in the database.
It would not PXE boot, we have even tried to restart the WDS Service, still no luck. But if we wait for about an hour, sometimes couple of hours or so, it would work fine. I am not sure if there's something that SCCM is holding on to and would not let the machine PXE again. We even tried to set CacheExpire registry key to about 30 sec, still no luck.
Any ideas?