SMBIOS GUID/UUID problems in SCCM OSD

When deploying a image to baremetal in SCCM you need to create a DDR since the Task Sequence is like any other deployment, that is a an advertisement targetting a resource in SMS.

How this works in the background however is that the Task Sequence uses the SMBIOS UUID to match the advertisement policy and chain the Task Sequence to the same system during the reboots needed for the whole process and computer association. So even if you import a record using only the new name of the system and the MAC address the the UUID will be used.The SMBIOS GUID/UUID is not the same as SMS GUID and should be hardcoded and unique just like MAC of a network card, this however is not always the case.If there is a problem with the UUID's on your systems you will run into problems:

UUID is empty: The Task Sequence will crash.

Duplicate UUID: The Task Sequence fails because there is already a system in the SCCM database with the UUID and there is no advertisement policy for that system or UUID.

If the Task Sequence fails because no advertisement can be found you can find out if this is the problem by starting the Boot Media with Command Prompt enabled and read through the smsts.log located under %temp%\smsts:

No assigned task sequence.      TSMBootstrap    2/8/2008 5:18:11 PM1480 (0x05C8)

Search above this error above the Processing Policy Assigments for a line similar to this:

Client GUID = GUID:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx. Netbios Name = ABC

If ABC is a different name than you imported then this one has the same UUID. You can search for duplicates of systems already having a client by running this SQL query:

SELECT     SMBIOS_GUID0, COUNT(SMBIOS_GUID0) AS CountFROM         v_R_SystemGROUP BY SMBIOS_GUID0, Active0, Client0, Obsolete0HAVING      (Active0 = 1) AND (Client0 = 1) AND (Obsolete0 = 0) AND  (COUNT(SMBIOS_GUID0) > 1)

If you have duplicates you can either create a stand alone media or contact the PC manufacturer and ask for a tool to fix the UUID If there is no UUID then the plan fix that in SCCM 2007 sp1, not I've not tested that yet.