I am seeing extremely long delays in the time it takes a server to be able to PXE to the assigned task sequence.

The system is imported and added to the correct collection.  I have confirmed it is in there, the MAC is correct and the task sequence is showing up in the deployment for the object.

The attempt to PXE shows there are no advertisements found.  I have confirmed the Item key is the resource ID of the computer in the correct collection with a task sequence deployed to it.

Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="16805113" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
 SMSPXE 6/23/2015 9:45:49 AM 2512 (0x09D0)
00:50:56:A2:67:D7, 02902242-23F3-53F3-9A27-355D6972BDBC: device is in the database. SMSPXE 6/23/2015 9:45:49 AM 2512 (0x09D0)
Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16805113" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply>
 SMSPXE 6/23/2015 9:45:49 AM 2512 (0x09D0)
00:50:56:A2:67:D7, 02902242-23F3-53F3-9A27-355D6972BDBC: no advertisements found SMSPXE 6/23/2015 9:45:49 AM 2512 (0x09D0)
00:50:56:A2:67:D7, 02902242-23F3-53F3-9A27-355D6972BDBC: No boot action. Aborted. SMSPXE 6/23/2015 9:45:50 AM 2512 (0x09D0)
00:50:56:A2:67:D7, 02902242-23F3-53F3-9A27-355D6972BDBC: Not serviced. SMSPXE 6/23/2015 9:45:50 AM 2512 (0x09D0)

Restarting WDS does not help. Just have to wait and it always works eventually.  The wait is usually around 15-20 minutes but has been up to an hour or more.

Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16805113" ServerName=""><Machine><ClientID>GUID:182A8871-C977-4EF5-B34E-8DDB0F6381DF</ClientID><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID="" LastPXEAdvertisementTime="" OfferID="A01203E8" OfferIDTime="9/18/2014 9:28:00 AM" PkgID="A010033E" PackageVersion="" PackagePath="http://My_DP/SMS_DP_SMSPKG$/A0100217" BootImageID="A0100217" Mandatory="1"/></ClientIDReply>
 SMSPXE 6/23/2015 10:05:57 AM 2512 (0x09D0)
00:50:56:A2:67:D7, 02902242-23F3-53F3-9A27-355D6972BDBC: using advertisement A01203E8 SMSPXE 6/23/2015 10:05:57 AM 2512 (0x09D0)
Looking for bootImage A0100217 SMSPXE 6/23/2015 10:05:57 AM 2512 (0x09D0)

This was 15 minutes later, nothing has changed but then it build correctly.

I have searched and I am unable to find what is causing this extremely annoying delay.  We have to go back to the server and reboot several times hoping this time it will build.  It is happening on all DPs and locations.

Any help would be appreciated.

Well from what i can see in your example ItemKey="16805113" this means that the computer was already in SCCM.

To see the issue i would add the ResouceID column in the device and look for the device. Make sure that those device are in the right collection to get the advertisement. Also look to see if you don't have 2 device with the same name and one being mark as obsolete. 

Also back in the hold days of SCCM 2007 you ad something called Cache for the PXE. This was a issue because people would boot up the computer to get the MAC address and it would register in the PXE you than would have to wait for that computer to expire from the cache to be able to be PXE booted again.

Hope this help you start looking in the right direction

• Edited by Frederick Dicaire 15 hours 2 minutes ago

Have you upgraded to SP2 or R2 SP1?

If so, there is a known issue related to DST. The easy fix is to set your available time on your TS deployment to a couple of hours in the past.

It am running CM 2012 R2 CU3. (5.0.7958.1401)

This is not a new deployment. The available time for the deploy is October 2014.

Well, then double and triple check the MAC particularly for transposed characters.

Also, when importing, are you using just the MAC Address or also attempting to put in the SMBIOS GUID?

Well from what i can see in your example ItemKey="16805113" this means that the computer was already in SCCM.

To see the issue i would add the ResouceID column in the device and look for the device. Make sure that those device are in the right collection to get the advertisement. Also look to see if you don't have 2 device with the same name and one being mark as obsolete. 

Also back in the hold days of SCCM 2007 you ad something called Cache for the PXE. This was a issue because people would boot up the computer to get the MAC address and it would register in the PXE you than would have to wait for that computer to expire from the cache to be able to be PXE booted again.

Hope this help you start looking in the right direction

• Edited by Frederick Dicaire Tuesday, June 23, 2015 4:44 PM

The MAC is correct.  The settings are all correct.  If I leave the machine without changing anything for anywhere from 15 - 45 the OSD does get picked up and deploys correctly.  It is just really painful randomly restarting the server for half an hour until it finally goes.

I've never ever seen this behavior.

Are you sure the resource is in the collection (not just in the membership rules), but actually shown in the collection at the time of the PXE boot?

Yes.  I have checked the collection and it is in there.  I have also checked the properties of the device and the Deployments tab shows several things deployed to it including the desired task sequence.

What does you SCCM topology look like? Do you have secondary sites? CAS? Are you using SQL DB replicas? These might have an impact on when the information in the Primary site DB is available to PXE on your DP.

Single Site.  No secondary, no CAS.

SQL DB sitting on an SQL cluster with no replicas.

This issue occurs even deploying from a DP in the primary datacenter where the management server sits.

I will be updating to CU5 then SP1 this weekend.  Really hope the issue is relate to....

https://support.microsoft.com/en-us/kb/3034183