Safe to Execute WSUS SUSClientID script fix on PDC domain controller?

I have a bunch of VMs on our network that I had found out were provisioned using the same templates or are clones of each other, in a sort of base configuration golden image sense.  This has presented a problem when it comes to how these servers appear (or at times fail to) in our WSUS server.  The symptoms are, some VMs show up, then disappear, come back, change groups and names...etc.

I have been making a list of suspect VMs and correcting this problem using the following script, executed on a machine by machine basis.

Link to issue and script that fixes it...
http://blogs.technet.com/b/sus/archive/2009/05/05/resolving-the-duplicate-susclientid-issue-or-why-don-t-all-my-clients-show-up-in-the-wsus-console.aspx

Now, my problem, its seems our PDC Domain Controller is a clone of something, a long while back.  I want to fix it, but am very trepidatious about executing any kind of script on a PDC unless I absolutely have to or understand fully the ramifications of every line of code or command.  And since you cant take snapshots of non 2012 DCs I can't back out of this.

Does anyone know specifically the ramifications of executing this script on a PDC? Based on my experience, it seems like it will fix the WSUS console issue, but will it mess up anything on the DC.  IE stopping BITs service, changing the SUSclientID (which should be ok as its not the GUID of the server) or other things effect a PCDs ability to do its job in any kind of way, cause AD replication issues or corruption of any kind?

Thanks A LOT for the help.
CnicNVAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

DonNetwork AdministratorCommented:
Perfectly safe, no ramifications.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
DonNetwork AdministratorCommented:
I use psexec \\* to distribute the script to the whole domain.
0
CnicNVAuthor Commented:
Ok thanks for the heads up.  Just wanted to double check.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.