SCCM Client with lowercase GUID does not work properly
We have an SCCM 2007 SP2 R3 environment and are seeing something strange with client connectivity. If a client has a GUID with its letters as lowercase, the client will appear to be loaded and communicating with the SCCM Site Server, but if you look in the
SCCM Console, it will show as Client = No. The client will not receive advertisements, provide inventories, etc..
Using the SCCM Client Center tool, we can force a new GUID upon a restart of the SMS Agent Host service, and the client will always get a GUID with uppercase letters and will then work fine; shows as cliented, gets advertisements, sends inventories,
etc..
Saw some of this on XP clients, but am seeing it on a lot of our Windows 7 machines deployed thru OSD.
1) What causes the client to receive a GUID containing lowercase letters?
2) Why do the Site servers care?
3) Is there an easy way to fix the servers so they respond to GUIDs without regard to their case?
Thanks in advance --
Jon
May 3rd, 2011 11:16pm
Hello - How do you build machines and install SCCM clients in your environment? Do you have client installed in the image ? Have you seen any duplicate GUID issue? Check the SCCM default report "Computers that may share the same SMS Unique
ID" Report ID - 71 (I think).
If it's a duplicate GUID issue then checkout
http://blogs.technet.com/b/smsandmom/archive/2007/11/07/duplicate-guids-fix-it-with-scripts.aspx
Anoop C Nair - This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually
answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
May 3rd, 2011 11:30pm
We are getting lowercase GUIDs on bare-metal machines that are imaged using OSD, where the SCCM client install is called in the Task Sequence.Jon W. Burlingham Sr.
May 3rd, 2011 11:38pm
Hello - So, I hope you have confirmed that there is no chance of duplicate GUID.
How about if you install a machine through a process other than task sequence? (Manual install, client push?)Anoop C Nair - This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually
answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
May 4th, 2011 12:16am
Hi Jon,
I agree with A00p, please check if there are any duplicate GUID. GUIDs should be treated as case sensitive. A GUID not exactly matching the case of the
record in the database will be processed as a new record.
Regards,
Sabrina
This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question.
This can be beneficial to other community members reading the thread.
May 8th, 2011 10:39pm
Thank you for the posts suggesting Duplicate GUIDs. I know they cause problems and have been checking for them. This problem is happening on new pc's getting installed thru an OSD Task Sequence, and their SCCM Client is installed using CCMSETUP called in
that sequence. It is not a duplicate GUID problem.jburling
Free Windows Admin Tool Kit Click here and download it now
May 9th, 2011 8:40am
I have the same problem in an SCCM 2007 SP2 R3 environment. We have PCs built from a PXE OSD Task Sequence with lowercase GUIDs which flatly refuse to get policy. I have connected to the offending PC with SCCM Client Center and regenerated the GUID which
is then in upper case and within 30mins the device is registered and in the database.
To add a bit more weirdness we have several machines in the database with lower case GUIDs!
July 1st, 2011 11:41am
What is your db collation set to? Ie. What is the Case Sensitivity set to : Case Sensitive or In-Sensitivity?
http://www.enhansoft.com/
Free Windows Admin Tool Kit Click here and download it now
July 1st, 2011 12:16pm
Case-Insensitive -- SQL_Latin1_General_CP1_CI_ASjburling
July 1st, 2011 2:16pm