See all of the top support solutions for our most common issues here
This article is regarding an issue we originally blogged about over at The Configuration Manager Support Team Blog regarding issues with PXE booting caused by duplicate SMBIOS GUIDs.. At the time that we wrote the article we really didn’t have a good solution or workaround on the ConfigMgr/WDS side to fix the issue. Since the issue was a problem caused by an OEM not adhering to industry standards, the only recommendation we could make was contacting the OEM for a fix at the hardware level.
Although the recommendation is to still fix the root cause of the issue by obtaining and running a fix from the OEM, we have recently discovered a feature of WDS called BannedGUIDs that allows us to work around the issue. This is especially useful in environments where there may be a large amount of duplicate SMBIOS GUIDs or where a BIOS fix or utility is not currently available from the OEM vendor. The below article outlines the issue and how to use the WDS workaround.
Note: We are planning to publish the below article as a KB article. If not already available, it should be available soon as KB2591483.
No Assigned Task Sequence when initiating deployments caused by duplicate SMBIOS GUIDs (System UUIDs) in System Center Configuration Manager 2007
When trying to start a ConfigMgr 2007 OSD Task Sequence on a PC, ConfigMgr fails to find a Task Sequence to run on the PC.
If the PC is Known (either an existing client or prestaged via the Import Computer Information Wizard), it has been verified that the Task Sequence Advertisement is targeted to a Collection that the PC is a member of.
If the PC is Unknown, it has been verified that the Task Sequence Advertisement is targeted to a Collection with the Unknown Computer objects (x64 Unknown Computer and/or x86 Unknown Computer) and that the PC is truly unknown and does not exist in the ConfigMgr database.
This problem can be caused by more than one PC in the environment having the same SMBIOS GUID. ConfigMgr refers the SMSBIOS GUID as System UUID. Similar to a MAC Addresses being unique to a NIC card, the SMBIOS GUIDs should also be unique on each PC. Two PCs should not have the same SMBIOS GUID. The SMBIOS GUID is stored in the PC's BIOS.
The problem occurs because when the ConfigMgr database is queried for available Task Sequence that are advertised to that PC, it does so first by using the PC's SMBIOS GUID. Each record in the ConfigMgr database records the PC's SMBIOS GUID under the attribute System UUID. If it does not match a record with the SMBIOS GUID, it then uses the MAC Address instead.
However, if multiple PCs have the same SMBIOS GUID in the environment, when the query on the SMBIOS GUID is done on the ConfigMgr database, it may find the record for a PC other than the one that the Task Sequence is advertised to. If the Task Sequence is not also advertised to the PC that it found, it will return back that there are no task sequences available for the computer.
NOTE: Do not confuse the SMBIOS GUID with the SMS GUID. They are two separate, different, and distinct items. The SMBIOS GUID is a unique hardware identifier used universally, whereas the SMS GUID is a unique ConfigMgr client ID used exclusively by SMS/ConfigMgr.
To see if the problem exists in the environment, create a query or collection in ConfigMgr based on the suspected duplicate SMBIOS GUID using the System UUID attribute. If more than one PC has the same SMBIOS GUID, then the problem exists.
To obtain the SMBIOS GUID from a PC having the problem, use one of the below methods:
To create a query based Collection that finds all PCs with a particular SMBIOS GUID:
The newly created Collection should display all of the PCs affected by the duplicate SMBIOS GUID. Repeat the above steps if more than one set of duplicate SMBIOS GUIDs exist in the environment.
Please note that this problem is caused by an OEM vendor not adhering to industry standards. It is not an issue with ConfigMgr.
There are two possible solutions to the problem
For both solutions, use the methods described in the Cause section to discover what PCs are affected by duplicate SMBIOS GUIDs.