System Center Configuration Manager TechCenter >
System Center Configuration Manager Forums
>
Configuration Manager Inventory
>
Conflict GUID records
Conflict GUID records
- Hi,
I have rename all the client computer name recently, I realize that in the collection, I could see both entries for new and old computer name. But it's only old computer name acts as sccm client, the new computer name isn't sccm client. I tried to look for the conflict record, I click to merge the record, at the end I still see 2 entries but now it''s two new computer name entries! How could I do the clean up work. Should I enable the maintenance tasks such as delete inactive client, clear install flag? Anyway none of the client computer has inactive/obselete status. Please help to advice what I can do now. Thanks
All Replies
- How often is Heartbeat Discovery? I may not be remembering correctly, but I think it's Heartbeat (the client itself sending up a "here's my name, and I'm alive" which will swap around the old name / new name in your database.
It's worth testing anyway.
Standardize. Simplify. Automate. - The heartbeat discovery is one week once.
- Hi,
See the solution in this KB article:
837374 How to locate and clean Advanced Client Duplicate GUIDs in SMS 2003
http://support.microsoft.com/default.aspx?scid=kb;EN-US;837374 - So if you pick a box which currently has two entries in the collection (the one with the old name and all the data), and the one with the new name (and no data behind it), and use either a remote tool (like Roger Zanders' Client Center) or physically go to Control Panel, Configuration Manager, actions, and invoke a one-time Heartbeat discovey, then wait several minutes (5-30, that's so hard to tell how long it might take in any environment), and then update & refresh the collection, is the new-name computer entry now have the data behind it?
If so, then you may want to consider increasing heartbeat to daily. Let it all cleanup for a week or so. Then you could put Heartbeat back to weekly, once it's all back to normal (whatever normal means to you). Or of course you could just wait out the week.
Standardize. Simplify. Automate. - Hey,
I agree with the path shown by Sherry. In addition to it just make sure we have "Delete Aged Discovery Data Task" Maintenance Task as enabled. If it is not enabled then doing the steps mentioned by Sherry would be of no use. Just want to make sure that you check it too.
Delete Aged Discovery Data Task Overview
http://technet.microsoft.com/en-us/library/bb693856.aspx
Regards,
Harpreet Rana
Technikala
Harpreet Rana
