client with no GUID ---does not have SCCM client installed on them.These computers are just discovered .If you want to manage them,then you can install sccm client onto them(use client push) else ignore /delete them and ensure they are not discovered again .this can be done by removing the OU from AD system discovery or denie access onto the OU for SCCM server.//Eswar Koneti @ www.eskonr.com

Just to clarify Eswar's (correct) statement, systems without the client agent will not have a GUID. The GUID is generated by the client at the time it is installed. Simply deleting will get rid them but they may be regenerated depending upon how they discovered in the first place. If they were created because of AD discovery, make sure you clean up AD also.Jason | http://myitforum.com/myitforumwp/members/jasonsandys/ | Twitter @JasonSandys

Hi Karim, You WMI query will query out all the computers discovered but do not have SCCM client installed. So these records are discovered by your discovery methord (AD system discovery or others), if you just delete then they will be regenerated at next discovery. Are these records are bad record in AD? if so you should clear AD first and delete them in SCCM. If not, will you want to manage them through SCCM? If so deploy clients to these computers and SMS Client GUID will be generated as the client agent installed. If you do not manage them, you can leave them alone they will not affect any SCCM functionality. Hope this will help. Thanks

Hi Karim, You WMI query will query out all the computers discovered but do not have SCCM client installed. So these records are discovered by your discovery methord (AD system discovery or others), if you just delete then they will be regenerated at next discovery. Are these records are bad record in AD? if so you should clear AD first and delete them in SCCM. If not, will you want to manage them through SCCM? If so deploy clients to these computers and SMS Client GUID will be generated as the client agent installed. If you do not manage them, you can leave them alone they will not affect any SCCM functionality. Hope this will help. Thanks

Hi, I created a collection for clients with GUIDs is null. Total numbers of resources in collection: 312, all of these resources are not SCCM clients. Query of the collection : select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_SYSTEM.SMSUniqueIdentifier is NULL What are the operations to do for those resources ? Can I delete these resources?

client with no GUID ---does not have SCCM client installed on them.These computers are just discovered .If you want to manage them,then you can install sccm client onto them(use client push) else ignore /delete them and ensure they are not discovered again .this can be done by removing the OU from AD system discovery or denie access onto the OU for SCCM server.//Eswar Koneti @ www.eskonr.com

Technet Blog has very good post on this... you can check steps to resolve the Duplicate GUID Issues and WQl also given here.... with more explanation .... http://blogs.technet.com/b/csloyan/archive/2010/04/27/system-center-configuration-manager-and-duplicate-guid-s.aspx 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.

Technet Blog has very good post on this... you can check steps to resolve the Duplicate GUID Issues and WQl also given here.... with more explanation .... http://blogs.technet.com/b/csloyan/archive/2010/04/27/system-center-configuration-manager-and-duplicate-guid-s.aspx 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. I think he is not referring to Duplicate GUID's rather client with NO GUID but its an information how to resolve duplicate GUID's :)//Eswar Koneti @ www.eskonr.com

Just to clarify Eswar's (correct) statement, systems without the client agent will not have a GUID. The GUID is generated by the client at the time it is installed. Simply deleting will get rid them but they may be regenerated depending upon how they discovered in the first place. If they were created because of AD discovery, make sure you clean up AD also.Jason | http://myitforum.com/myitforumwp/members/jasonsandys/ | Twitter @JasonSandys