Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Replacing Domain controller

Status
Not open for further replies.

csjoseph

MIS
Joined
Jan 2, 2001
Messages
247
Location
US
Windows 2000 Server

I need to replace an existing domain controller w/ a new server. I would perfer to keep the same server name.

What is the best way to go about this?
 
First explain or justify why you need to keep the same server name. Then the rest of us will talk you out of it. You are asking for a big headache otherwise.


=====================================
The good ole days weren't always good
and tomorrow ain't as bad as it seems
=====================================
 
In that case, screw the server name.

I guess the only question is what differences do I need to do for setup. I've setup a secondary AD server but have never had to replace the main one.

Also, one note, it is not the parent AD server. It is the primary AD server for a child domain.

Chris
LAN Analyst
 
Let me see if I understand. You only have two DCs and each of the DCs are in different domains? If that is the case you might have an issue. The first Domain you create is called the Forest Root Domain. As far as I know the Forest Root Domain can never go away. I might be wrong, but I don't think so. DCs in the Forest Root Domain, can come and go, but at least one needs to always hang around.

Let me know if I'm understanding you.

=====================================
The good ole days weren't always good
and tomorrow ain't as bad as it seems
=====================================
 
Sorry, my last post was sketchy at best.

Out root domain xxx.com will stay intact, no changes. We have a child domain france.xxx.com whose domain controller needs to be replaced.
 
Cool, that should be easy then. Set up the new DC in france.xxx.com. Make sure you have access to a DNS for this domain, or make sure it is set up and working on your new DC. Move all of the FSMO roles over to the new DC. You might also need to make this new DC a Global Catalog server. Run DCPROMO on the "old" server, to remove it from the domain. Here's an article on moving the FSMO roles.




=====================================
The good ole days weren't always good
and tomorrow ain't as bad as it seems
=====================================
 
I should have also said that not all FSMO roles will need to be moved in your Child domain. There a couple of FSMO rules that stay in your Forest Root Domain. The Schema Master and Domain Naming Master are only in your Forest Root Domain. The only FSMO roles you should see on your Child domain should be the: RID Master, PDC Emulator, and Infrastructure Master. Also, the Global Catalog service as I said before.


=====================================
The good ole days weren't always good
and tomorrow ain't as bad as it seems
=====================================
 
As always, wonderful advice guys.

Thanks again.
 
If you bring a new DC up (via DCPROMO) into france.xxx.com, install all of the necessary services on the new DC (DNS, DHCP, GC, etc), then DCPROMO the old DC out of france.xxx.com, it will automatically transfer all of it's FSMO roles over to your new DC.

I'm Certifiable, not certified.
It just means my answers are from experience, not a book.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top