Demoting and promoting a DC

[w33mhz]

I have a W2k DC that is also a TS license server. I am having some replication issues and I was going to demot it and promote it back. Will this cause issues with the licensing server?

 

[GrimR]

Have you tried deleting and recreating the connections.
Have you tried resetting the DC account in AD

 

[w33mhz]

Well there was something goofy with that box has been for awhile. Yes I did try creating new connections and that didn't work. I just cloned the machine and demoted it. I had to dcpromo /force because it couldn't talk to AD, then use ntdsutil and remove the server off of my FSMO, and then remove the computer account out of ad. Then I dcpromo'd the box again and everything came back up. I was really only worried about the licensing getting messed up, I really don't like calling the clearing house. My citrix licenses were not affected either.
One note that I found was that if something went wrong with the box and I had to use the clone, just bringing the clone up would have added it back to the FSMO, I would probably have to recreate the AD computer account if I had deleted it. So it wasn't as big a deal as I thought.
Thanks for your post.

 

[TechyMcSe2k]

If you did a Metabase Cleanup of your DC, it is Microsoft recommended practice to not use the same computername when promoting the new server to a DC.

http://support.microsoft.com/kb/216498/

Cliff, MCSE/MCSA/MCTS/CCNA/VCP/CCA

http://www.samtechconsulting.com