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

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

Frank Rojas — Thu, 12 Jul 2012 14:18:40 GMT

Thank you for your input. However pelase be aware that modifying the stored procedures is not only not supported by Microsoft, but also puts your environment in an unsupported scenario. The modified stored procedures have not been thoroughly tested by Microsoft. Changing them may result in unknown and unexpected behaviors. We strongly recommend against modifying the stored procedures for these reasons. There is also no reason to modify the stored procedures as there is a fully supported solution which is to use the BannedGUIDs registry entry of WDS.

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

agustig — Thu, 12 Jul 2012 13:58:53 GMT

Hi,

I have been suffering the same issue and I have solved it modifying two stored procedures following the instructions of this post:

Regards

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

Frank Rojas — Tue, 27 Mar 2012 19:11:15 GMT

The above blog post is an updated version of the original blog post that the above link mentions. The above blog post contains the additional workaround of using the BannedGUIDs registry key. Microsoft does not suggest making changes directly to the DB except in extreme circumstances, and this is not one of them. Additionally the changes mentioned on the above link regarding modifying the ConfigMgr DB would only get you past the PXE boot and is the equivalent of using the BannedGUIDs registry key. I would not recommend modifying the DB.

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

mariorami — Tue, 27 Mar 2012 18:44:02 GMT

I am curious to know if anybody out there has tried this fix to the duplicated SMBIOS GUID issue:

I am still trying to figure out how to be able to image with Configmgr those computers with the same SMBIOS GUID. I was able to make them PXE boot by banning the GUID, but when boot to ConfigMgr wizard I can make them see the task sequences. I have not tried to solution mentioned in the link above (I am tempted since nothing seem to work) and I am very cautious modifying the DB.

Thank you.

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

Douglas Gaigher TI — Mon, 13 Feb 2012 11:44:20 GMT

My SCCM 2007 SP2 R3 server does not have the registry entry HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WDSServer\Providers\WDSPXE probably because it doesn't have WDS installed.

It is normal, i need to create this key yet?

Thank you.

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

Frank Rojas — Mon, 06 Feb 2012 19:07:57 GMT

Although I have heard about the fix regarding modifying the stored procedure in the ConfigMgr database, we normally do not recommend directly editing the database except for extreme cases where there is no workaround or other fix. Based on the information you have given, I cannot really say what is going on. However is you open a case with CSS we can take a look at it and see if we can get it working without having to modify the database.

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

mariorami — Mon, 06 Feb 2012 18:52:15 GMT

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.

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

Frank Rojas — Tue, 06 Dec 2011 15:07:17 GMT

Your probably running into the PXE cache issue as mentioned in the article. See KB2019640.

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

PXE — Tue, 06 Dec 2011 13:11:33 GMT

I have a strange issue with my pxe. Newly imported PC´s do not pxe boot. Reinstallations do pxe boot!

If i restart the WDS service on the sccm server then the next newly imported PC´s can pxe boot. But after that the issue is back.

I have this in my smspxe.log

MAC=70:F3:95:19:34:3C SMBIOS GUID=57A17D00-FDF9-11E0-91C2-904C19ABCEC4 > Device not found in the database. smspxe 12/6/2011 1:03:13 PM 2304 (0x0900)

I have made a query for its SMSBIOS GUID but it finds nothing. This makes me think this is not just a matter of a duplicate. As i mentioned this seem to happen with every newly imported PC.

I have reinstalled WDS/PXE point twice but it does not seem to have helped.

Any idea what could be wrong here?

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

Frank Rojas — Mon, 14 Nov 2011 17:21:01 GMT

The best way is probably to delete the record of the PC in the ConfigMgr 2007 Admin console, and then force the PC to report hardware inventory again via the "Harware Inventory Cycle" action. This should recreate the record in ConfigMgr 2007 with the new information. You may also have to run the "Discovery Data Collection Cycle" action for it to recreate the record properly. You should not need to reinstall the client.