Domain Controller Replacement. Need some real advise.
Posted on 2008-09-30
I come to the experts again for guidance. I would like to replace our current Domain controller. We are running at 2K3 Functional Level. We have about 40-ish users on at any given time. We now have 3 domain controllers. The third was today's addition. I am savvy enough to add a domain controller, however, I am not experienced enough nor am I confident in my predecessors builds that the domain won't take a hit in some way. Sooooo ...
This is what I would like to do ...
1.) Use DCPROMO on the #2 DC and remove it and its metadata from the domain. Rebuild it and rejoin it to the domain as the #2 once again. <=== I think I can do this, However guidance is appreciated. :)
2.) I want to seize the FSMO rolls on the #1 DC and move them to the newly built and added #3. Then I would like to remove it completely from the domain. This is where my problem begins. I would like to know where/what to keep my eyes on when doing this because as mentioned I am not confident in my experience or my predecessors builds that the domain wont take a hit somehow. Thoughts, Ideas ... help ... PLEASE?! :)
3.) Rebuild the #1 box and seize the FSMO roles back to it from the #3 box.
4.) Finally .... Retire the #3 box to its role as my 'TestServer'. <== I got this part I think.
... The reason for this is that I do not trust the builds in place now. Reason's like the %systemroot% on the #2 is on the 'E' drive ... yes ... the 'E' drive. Also, on the #1 box I have been getting gpt.ini errors. Chasing down issues that were here before me is not something I want to do if I can help it ... easy fix or not. If I built the box and loaded the OS ... then at least ... I know I did it and won't be that afraid of poking around when problems do arise.
In any case, any help is appreciated.