Results 1 to 1 of 1

Thread: SCCM and duplicate UUID SMBIOS GUIDs

  1. #1

    Join Date
    Jan 2009
    Thanked 0 Times in 0 Posts

    Default SCCM and duplicate UUID SMBIOS GUIDs

    I just had to make a forum post about this problem. This one had us scratching our heads a bit. We had a cluster of brand new systems in a computer lab that just would not PXE boot in SCCM and allow us to do a bare metal installation of the OS. The systems always came up with the dreaded "TFTP Download: smsboot\x64\" "PXE Boot aborted. Booting to next device" error messages.

    We couldn't figure out for the life of us why these new systems wouldn't take an image. Then we started doing a bit of troubleshooting. After looking at the smspxe.log file we found that there were error messages for the system stating "device found in the database". This was a bit odd seeing as these were new systems. So we did an SCCM query to list the SMBIOS / UUIDs and lone behold there were duplicates.

    The query used was:

    select SMS_R_System.Name, SMS_R_System.MACAddresses, SMS_R_System.SMSUniqueIdentifier, SMS_R_System.SMBIOSGUID from SMS_R_System

    So what to do now? Well, there are two choices:
    1. Fix the UUID / SMBIOS ids in the BIOS of the system so that they are unique
    2. Use a feature in WDS to ban the duplicate SMBIOS / UUIDs.
    Fixing the UUID / SMBIOS IDs

    The only way to do this is with a software tool from your hardware manufacturer, or in some cases you can edit the UUID directly in the BIOS. If your hardware manufacturer doesn't have a tool and you can't edit it in the BIOS, you cannot use this option. FYI, the HP 8200 Elite series we use allow you to edit this in the BIOS, by hitting F10, once in the BIOS, press CTRL-A to enable editing.

    Ban Duplicate SMBIOS / UUIDs in WDS

    I stumbled across an interesting article which described a feature in WDS which allows you to ban the duplicate UUIDs in WDS. Essentially it's a registry key in which you list all of the offending UUIDs, one per line. The UUID is stripped from the PXE packet before SCCM receives it leaving your MAC address to provide uniqueness.

    Here is the registry hack information:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\WDSServer\Providers\WDSPXE
    • Name: BannedGuids
    • Type: REG_MULTI_SZ
    • Value: GUID strings, with one string per line. The correct format is as follows: 1acbf447-3993-e543-a92a-fadb5140f1c8, which should match what you see when you perform a PXE boot on a client.

    Thanks to everyone for their feedback to finding the above solutions.

    Ernest A.
    Last edited by Ernest Aleixandre; 08-30-2011 at 01:21 AM.
    All information posted is provided AS IS with no warranty or liability. Use it at your own risk! This posting is Copyright (c) by it's owner, you may not copy or reproduce this posting without written permission from the author. You are granted permission to distribute links back to this document.

Tags for this Thread


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts