Tag: Task Sequence

How to enable OSD with duplicate UUID in Configuration Manager

On rare occasions vendors inadvertently release machines with an SMBIOS GUID exactly the same as others and if we already have another machine in our …

Roddy Gelberty 6 July 2020

0 Comments

Forum Description

On rare occasions vendors inadvertently release machines with an SMBIOS GUID exactly the same as others and if we already have another machine in our SCCM database with the same SMBIOS GUID, SCCM won’t allow another machine with the same SMBIOS GUID.

I’ve stumbled upon this scenario before, but unfortunately there is no clean fix available. This needs to be fixed at a hardware level. We need to contact the vendor to get this rectified.

I’ve found these workarounds online. The first workaround seem to be less intrusive and manageable than the second option.

Workaround 1: For Windows Deployment Services with SCCM, we can setup a BannedGuids registry entry for WDS which strips the SMBIOS GUID from the network packet of the machine which is PXE booting before the network packet is passed to SCCM. SCCM only sees the MAC address.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WDSServer\Providers\WDSPXE

Name: BannedGuids

Type: REG_MULTI_SZ

Value: GUID strings, with one string per line. The correct format is as follows: {1acbf4473993e543a92afadb5140f1c8}, which should match what you see when you perform a PXE boot on a client (without dashes).

This workaround only applies to PXE boot client. Boot media clients need to implement the second workaround.

Workaround 2:

Written By: idany at myitforum.com

Modify the following stored procedures:

NBS_LookupDevice

Change the line

MP_GetClientIDFromSmbiosID

Change the line