[SCCM CB] SCCM Duplicate SMBIOS GUIDs

[smarties11]

Hi All,

 

We're in the process of rolling out Windows 10 across our estate. I've come across a batch of computers that have an identical SMBIOS GUID. The GUID is 03000200-0400-0500-0006-000700080009. I think this is essentially a 'default' GUID if the manufacturer hasn't set one themselves. They are mainly all the same make and model (Zoostorm AIO) - plus two further random machines.

 

This basically means when you PXE boot the machine, SCCM thinks it is already in the database. I've added the GUID as duplicate hardware identifier in the site hierarchy settings - this gets past the initial issue and SCCM recognises the computer by it's MAC address instead. However, the task sequence then attempts to join the computer to the domain using the computer name belonging to one of the duplicates, rather than the one I specified via the OSDComputer variable. The task sequence progress but eventually fails.

 

Can anyone advise how they got around this? I've seen a few options.....using AMIDEWIN to set a different SMBIOS GUID (that doesn't work for me)…altering the stored procedures in SCCM so that it only goes off the MAC address and not the SMBIOS GUID (not sure if that's a good idea, plus you have to remember to change the stored procedures each time you update SCCM). These are older machines and the chances of getting updated BIOSs with the SMBIOS GUID updated are slim!

 

Thanks!

[jslate1980]

Randomly yesterday I noticed we are also having the same issue. I upgraded my CB version from 1710 to 1810 to see if it would fix it. No change. I am a member of a couple sccm forums, will post something and keep you updated if I find a fix.

 

is there anything in the smsts.log during the build process?

Edited February 14, 2019 by jslate1980

[markwilfan]

I remember having this a while back. Only fix I found was to delete the sccm entry for the client, image the next one and rinse and repeat.

 

You can create a collection to find the duplicate guids

[mdrabble]

You can download a guid editor from the motherboard manufacturer. I had to do this with a few zoo and Lenovo all in ones.

[smarties11]

Thanks to all for the responses! I've been in touch with Zoostorm and they are going to send me a tool to change them. Fingers crossed it works....

 

However, I ran a task sequence again yesterday (after having blocked the duplicate hardware ID in site hierarchy) and it went through fine. It asked me for OSDComputer name and joined to AD with that correct name (despite the duplicate hardware ID). Perhaps you have to wait a certain amount of time for this setting to become active?