OSD Task Sequence fails with "There are no task sequences available for this computer" if multiple machines have the same SMBIOS GUID


Note: There is an updated version of this article over at the Configuration Manager OSD Support Team Blog. For the latest version, please visit the below article:

No Assigned Task Sequence when initiating deployments caused by duplicate SMBIOS GUIDs (System UUIDs) in System Center Configuration Manager 2007


Here's an issue we still seem to see on a fairly regular basis here in support so I thought it might be worth a mention here in case you happen to run into it.

Issue:  When attempting to deploy an operating system using OSD in System Center Configuration Manager 2007, the Task Sequence may fail with the following error:

There are no task sequences available for this computer.

If you look in the SMSTS.log you may also see the following error:

No assigned task sequence.
Setting wizard error: There are no task sequences available for this computer.

The SMSTS.log may also show the SMBIOS GUID as follows:

Setting SMBIOS GUID = 4C4C4544-0000-2010-8020-80C04F202020.


Setting SMBIOS GUID = 03000200-0400-0500-0006-000700080009.

Note: Analyzing the Advertisement and the Collection confirms that the target computer is in the proper Collection that the Advertisement is pointing to. Deleting the computer from the SCCM database and re-adding it back to the SCCM and the Collection via the Import Computer Information wizard using the MAC address or SMBIOS GUID does not resolve the problem.

Cause:  The issue can be caused by there being more than one computer in the environment with the same SMBIOS GUID (aka System UUID). Similar to MAC Addresses, SMBIOS GUIDs should be unique on each computer and no two computers should have the same SMBIOS GUID. The SMBIOS GUID is stored in the computer's BIOS. Do not confuse the SMBIOS GUID with the SMS GUID. These are two separate, different, and distinct items.

The problem occurs because when the SCCM database is queried for available Task Sequences that are advertised to that PC, it does so first by using the computers SMBIOS GUID. Each record in the SCCM database records the computers SMBIOS GUID under the field System UUID. If it does not match a record with the SMBIOS GUID, it then uses the MAC Address.

However, if multiple computers exist in the environment and are in the SCCM database with the same SMBIOS GUID, it may find the record for a PC other than the one where the Task Sequence is trying to be initiated. It will then query policy for that other PC, and if that other PC does not have a Task Sequence advertised to it, it will return back that there are no task sequences available for this computer.

Resolution:  To see if this problem exists in your environment, create a query or collection in SCCM based on the suspected duplicate SMBIOS GUID. If more than one computer has the same SMBIOS GUID then the problem exists in the environment and needs to be fixed at a hardware level. You will need to contact the OEM vendor for a fix.

Additional Information:  The SMBIOS GUID can be found in the SMSTS.log in the line:

"Setting SMBIOS GUID = "

It can also be found by inspecting the SMSPXE.log as the PC tries to PXE boot. In addition, it can also be obtained by hitting the Pause/Break key on the keyboard on the affected PC at the PXE boot screen. The SMBIOS GUID should be displayed somewhere on that screen.

Frank Rojas | Support Escalation Engineer

Comments (21)
  1. Anonymous says:

    Banning the GUID did the trick to be able to PXE boot, but I am still not able to image those computers with the duplicate GUID. The configMgr db does not recognize those computers. I created a collection and query for all of those computers with duplicate GUID (over 700) and then I advertised my image to that collection but still no success. I always get the message "There is no task sequence available for this computer".

    I am waiting on the OEM hardware vendor to see if they have a patch that creates a unique GUID for each of those computes.

    I read an article the other day about a way to fix my problem by editing the ConfigMgr database to make it look for MACs instead of GUID, but I am not confident with doing that….

    I would like to know if any of you have tried that fix.

    At his point offline imaging is the only choice I have.

  2. Anonymous says:

    There's a way to circumvent this problem, by setting the BannedGUIDs key inside the registry of the SCCM server, but we haven't got it to work. Any chance you could have a look at my thread over at the myitforum and possibly come with some suggestions…? Thanks


  3. Anonymous says:

    Thank you! That's a great blog article with a very detailed description of the problem and the reasons behind it. It also describes the work-around solution of setting the BannedGuids value inside the registry, but we're still not convinced that it's actually working.

    Yes, it works at PXE boot time when the WDS is running, but after you enter the WinPE session and SCCM takes over, will the bannedguids-feature still work…? We have not tested this because we don’t have any machines with duplicate GUIDS just yet in this domain, but my guess is that SCCM task sequence will relate to the GUID and not the MAC address. From the other posts inside the myitforum topic ( http://www.myitforum.com/…/Issues-with-the-BannedGuids-feature-m231980.aspx ), it doesn't sound like it should work..

    Anyway, we've observed that SCCM will take care of the problem itself if the duplicate GUID is of the special case of all 'F's, since we didn't ban this GUID, and when testing imaging two machines with this special GUID, no problems will occur, and the following can be found inside the smspxe.log for the 2nd machine, and where the text "Device found in the database. MacCount=1 GuidCount=0" is important to notice…:

    [] Recv From:[] Len:283 1654d30           smspxe                25.10.2011 13:17:25        6076 (0x17BC)

    Parsing Database name 'DB1,1435SCCM_DB' for SQL named instance.   smspxe                25.10.2011 13:17:25        5704 (0x1648)

    Executing LookupDevice(00000000-0000-0000-0000-000BCD1348B0, 00:0B:CD:13:48:B0)             smspxe                25.10.2011 13:17:25               5704 (0x1648)

    CDatabaseProxy :: LookupDevice succeeded: 0 0 14034 1           smspxe                25.10.2011 13:17:25        5704 (0x1648)

    MAC=00:0B:CD:13:48:B0 SMBIOS GUID=00000000-0000-0000-0000-000BCD1348B0 > Device found in the database. MacCount=1 GuidCount=0         smspxe                25.10.2011 13:17:25        5704 (0x1648)

    [] Recv From:[] Len:303 12741f0            smspxe                25.10.2011 13:17:25        6076 (0x17BC)

    Parsing Database name 'DB1,1435SCCM_DB' for SQL named instance.   smspxe                25.10.2011 13:17:25        5704 (0x1648)

    Executing GetBootAction(14034, SAD-012)        smspxe                25.10.2011 13:17:25        5704 (0x1648)

    vLastPXEAdvertisementID is NULL         smspxe                25.10.2011 13:17:25        5704 (0x1648)

    vLastPXEAdvertisementTime is NULL   smspxe                25.10.2011 13:17:25        5704 (0x1648)

    GetBootAction: MAC:00:0B:CD:13:48:B0 SMBIOS:FFFFFFFF-FFFF-FFFF-FFFF-FFFFFFFFFFFF SMSID:GUID:8403bb9d-d508-4189-8793-321b5d22197f LastAdv:          smspxe                25.10.2011 13:17:25        5704 (0x1648)

    Advertisement results: OfferId:DGI20054 OfferTime:17/01/2011 08:28:00 PackageID:DGI000AD BootImageID:DGI00041 PackageVer: PackagePath:\SCCMSMSPXEIMAGES$SMSPKGAB100041 Mandatory:0        smspxe                25.10.2011 13:17:25               5704 (0x1648)

  4. Anonymous says:


    this post solved my problem,

    For some reaosn it was a computer which for a brief time had sccm client, i did not see this computer in any collection, the "All Clients" found it tho, i created collection from that query and deleted the computer.


  5. Terry Johnson says:

    This issue cost me 2 hours of work and only caught it by looking at the properties of the computer that I was imaging and seeing the netbios name of a computer that I imaged last week.  Same smbios guid on a Optiplex 620 and a Precision 380.

    <Sarcasm>I can't believe I didn't think to look for this first!</Sarcasm>

  6. boredazfcuk says:

    I received the the same error:

    There are no task sequences available for this computer.

    Also the log was the same:

    No assigned task sequence.

    Setting wizard error: There are no task sequences available for this computer.

    …but mine was because the Site Server signing certificate had expired.

    Hope this helps someone.

  7. Dave says:

    If this problem is on a Dell….one could try this:


  8. Richard says:

    Hi, I searched and red many posts but couldn't find a solution to my problem. I can image any computer just fine but one that was already imaged before. I ran the MAC address report and didn't find 2 machines with the same one. I created a collection for the SMBIOS GUID but didn't find 2 with the same one either. I deleted the machine I try to reimage and imported it manually again.. It has task sequence assigned to it (same container as other machines I image successfully) but no go. I tried to boot it with a boot media but it gives me the same :no task sequence avilable.." I rebooted my SCCM server many times, restarted the WDS service every time I would create/delete my machine to do tests but no luck. At this point I wonder if there is a way to manually edit the database and search for the mac address and manually delete that entry.. We had to do this for obselete DP before.  Can anyone help?


  9. Richard says:

    I think I found the problem but I don't understand what's going on.. on the computer I want to image the guid it shows at pxe boot is: 9FCCA401-4A32-11CB-BB88-E188D65A0F68. When I look in the smspxe.log file on the server, I see: MAC=00:22:68:0D:C5:9F SMBIOS GUID=01A4CC9F-324A-CB11-BB88-E188D65A0F68 > Device found in the database. MacCount=1 GuidCount=1. The GUID has the same letters and numbers for the first 3 sets but all mixed up.. the last 2 parts are in the same order though. Odd isn't it?

    Anyhow, I took that last GUID and put it in the GUID querry and it came up with another computer that has that last GUID… I agree that they both have  the same letters/numbers but they are in a different order so what's wrong with it?? and how do I fix this..

  10. Richard says:

    Well.. I deleted the 2nd machine and now it works on the one I want to image.. can someone explain why sccm scramble up the GUID as explained before?? I assume that the last time the 2nd machine was online it was on WIFI so that would explain why I couldn't find it with MAC address since I use the rj45 connection to push the image..

  11. How to change UUID in the DDR? says:

    We have a problem with generic UUIDs.  We got an updated BIOS from the vendor and have now changed the UUID listed in the BIOS.  How do we get the SCCM record updated?

  12. One of the best ways to delete the duplicated Guid will be to goto reports,check for a report called "Computers for a specific MAC address" and then check the host name and delete that Host name from the "All systems Collection" and then try to deploy the OS using Task Sequence/OSD and that should work.

  13. Andrew says:

    Hey Mariorami, we have been having this issue with our iMacs, none of which would see a task sequence, we tried the banned guids option, but it didn't help. We finally tried the solution posted here: myitforum.com/…/how-to-enable-osd-with-duplicate-uuid-in-configuration-manager.aspx and lo and behold, it WORKED!! So after wasting quite a lot of time troubleshooting this issue, we can now get on with other things.

  14. artem says:


    Your solution worked!  Turns out that the problem was that SCCM was using the wireless NIC with a similar GUID.  I searched for the last 12 digits of the GUID since it is the same on both wired and wireless NIC's and found the duplicate.  I then deleted the duplicate and I am now able to image it!  Thank you Richard for your input!!!

  15. Don says:

    What about ConfigMgr 2012 SP1, situation is the same?

  16. Roger Truss says:

    I am bumping this as we too have gotten around the WDS issue but still systems with dupe guids will not run a task. They just restart. Looking at the deployment tab on all the units in question shows that there is a task available to them too but no go. We have over a 100 systems in this state.

  17. Anonymous says:

    Nicholas Dille recently posted a good blog on GUID management in PowerShell Desired State Configuration

  18. Homebrewed says:

    We have a bare metal "catch all" collection for re-imaging known devices with SCCM. I was able to simply put all of our devices that share this SMBIOS GUID into the collection so they would be offered a new OSD. We have our PXE setup so that it only works
    on specific VLANS, thus our production machines wouldn’t be affected and I could image the gear I needed to.

  19. Brian says:

    Good article! You save a lot of my time to figure out why I keep getting Task Sequence error without any error code. I wish SCCM report the duplicate SMBIOS GUID message in smts.log instead of reporting No assigned Task Sequence then terminated.
    Many Thanks!

Comments are closed.

Skip to main content