Okay I've searched high and low, maybe I'm not able to put two and two together on this so I'm here at your mercy. I have a large number of computers that are getting renamed. We've been using the netdom tool to rename the machines. Each batch of these renames is generating a duplicate guid in SCCM 2007. I think tranguid.exe might be the answer to my woes but, I'm not sure how I would want to use it and what does it do with the already existing record. Does anyone else have experience in renaming workstations in a large environment using netdom that has the sccm advanced client installed on them?

I've read some official sms 2003 documentation on how to handle duplicate guids and it explains that renaming a client does not create them it goes on later to say it does in the same material. I can see them there as well after run the queries. I'm reaching out again for some help on this issue. Not sure why what I wrote was a proposed answer. I've read this document: Managing Duplicate GUIDs.DOC this explains how to resolve the duplicates that I have currently in the environment which is great. It does not address the bigger issue at hand, "Why are my clients after getting renamed through netdom creating duplicate SMSIDs. I can consume that if the agent doesn't report back before the next AD Discovery I'll get a blank recorded created. I'm pretty sure I have some ideas how to automate that reporting after the rename but I don't believe what I'm going to use to force the heartbeat discovery will reconcile the issue of computer named aaa111 renamed to bbb222 from creating a second record. Link to the Managing clients doc: http://www.microsoft.com/en-us/download/details.aspx?id=17957