I was recently working with a customer who had a CAS and 9 primary sites. We were noticing machines were receiving abortpxe when attempting to PXE boot. This happens when the machine PXE booting does not have a OSD task sequence targeted to it.
The interesting thing was there was a OSD task sequence targeting the “All Unknown Computers” and “All Desktops and Servers” collection for PXE and Media based deployments. In theory, this would mean that any machine that’s ever PXE booting should have a task sequence targeting it.
The first thing I did was look at the SMSPXE.log on the DP the machine was PXE booting from. I noticed the following (Notice ItemKey=16787541 this is referring to the ResourceID of a ConfigMgr Client):
The first thing I did was go to the Devices node added the ResouceID column on the CAS and search for “16787541” the ItemKey from the SMSPXE.log. I went to the properties of the device and verified that device did infact have a task sequence targeting it.
The client we were looking at was assigned to site 001 but was using a PXE enabled DP from site 002. This customer often had machines roam to other locations that could be part of another primary site.
The only database that is treated as being definitive for a PXE enabled distribution point is the database of the primary site that the PXE enabled distribution point is in. That means that a PXE enabled distribution point in a hierarchy will only know of task sequence deployments to KNOWN clients if it’s in the same site as the distribution point.
We also had a few unknown machines that were unable to boot. This was for older Dell laptops. It ended up being caused and duplicate SMBIOD GUID’s. When a machine PXE boots it check if there is a Mac address or a SMBIOS GUID for the device. If there is not, the device would be considered an unknown machine. Since some of these machines has duplicate SMBIOS GUID’s, it would think the device is a known machine and the other machine with the same GUID would sometimes be assigned to a different primary site. This would cause the machine to not see the task sequence deployment.
There are a few workarounds for this scenario:
This behavior is by design and won’t likely change.
Do you have any idea why Task sequence won't update after deploying?
What do you mean by won't Update?
Ever ran into TFTP Open Timeout?
@ help. This is likely an issue outside of ConfigMgr is there any activity in the SMSPXE log when you get this error. If you machine is in a separate subnet than the PXE enabled DP you likely need IP Helpers configured.
Sorry to get back to you know Justin. Didn't do much with SCCM in awhile. Right now, I still get the error and unable to to located the SMSPXE log.