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 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.


Name: BannedGuids


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

Modify the following stored procedures:


Change the line



Change the line


Related Articles

SCCM task sequence UI – Set computer name and more during an SCCM task sequence deployment

It is always a unique challenge of having to build an OSD experience that includes providing a great user experience during the deployment of a new operating system.

The attached application would allow you to present a front-end to an active end-user who is executing the SCCM task sequence……

Keywords: SCCM tasksequence UI, SCCM Task Sequence User interface, SCCM task sequence Set computer name.


DCOM hardening issue.

This application fails to authenticate with WMI on the SCCM server because Microsoft has not yet hardened DCOM on their Windows Preinstallation Environment. We are working on a different approach, but it will only be released during the first quarter of 2024. But until that time, the only workaround will be to uninstall the update corresponding to KB5004442.