Follow the three important phase to fix them-
PhaseI: Identify & Access - Add the below three query rules to one collection and update the collection membership. You will find machines with duplicate GUIDs listed on the right pane of SMS console.
Duplicate GUID Query#1
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 join SMS_GH_System_System on SMS_R_System.ResourceID = SMS_GH_System_System.ResourceID where SMS_R_System.Name <> SMS_GH_System_System.Name
Duplicate GUID Query#2
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 join SMS_G_System_System on SMS_R_System.ResourceID = SMS_G_System_System.ResourceID where SMS_R_System.Name <> SMS_G_System_System.Name
Duplicate GUID Query#3
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.ResourceID in (select SMS_GH_System_System.ResourceID from SMS_G_System_System join SMS_GH_System_System on SMS_G_System_System.ResourceID = SMS_GH_System_System.ResourceID where SMS_G_System_System.Name <> SMS_GH_System_System.Name)
Once done, go to phase2
Phase2: Manage and Control
1. SMS client should either be repaired or client should uninstall first and then reinstall.
2. Swapping hard disk or renaming same computer name with another machine name should be avoided.
Phase3: Maintain and Record
1. Maintain a list of computers with Duplicate GUIDs
2. Categorize them
3. Record the reason why they get duplicate GUIDs
4. Compare the list of machines having duplicate GUIDs issue with how many machines are getting fixed.
5. Record the fix steps accordingly.
No comments:
Post a Comment