Question Locked

Need to replace failing Domain Controller ASAP. What is best practice?

0 helpful
4 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We have 5 domain controllers. 2 are located in one office, one of which has all FSMO roles. The other 3 DCs are in remote offices and run DNS and DHCP.

One of these DCs is randomly rebooting among other random issues. We believe the OS is possibly corrupt and my boss wants it rebuilt on new hardware.

This DC is also a SQL 2005 Server, provides roaming profiles, as well as mapped network drives to users(I know this is all bad but this is how things were setup before I started). Keeping the same name is very important.

Given that the server is still functional what is the best way to rebuild this DC/SQL/DNS/DHCP server on to new hardware using the same name?

4 replies

by bart777

First is the obvious backup. (Also doing an SQL backup for each database)
Next I would disable the Vscanner. That has caused me more heartache than I care to remember. It may actually be the root of your reboot issue.
Once the DBs are off the box just do a DCPROMO and take AD off of the box. If this is the FSMO role holder you will want to get that moved before the demotion.
Migrate all of the data in those shares and the profiles to another box. You might consider leaving them wherever you move them to and just change the login script.
Then take the server out of the domain and put it in a work group. This will remove the server name from the domain.
Take down DHCP on that server and bring it up on the other DC.
Verify that your network and AD are stable.

Then format C and rebuild that bad boy.

Once you're back up and running you can DCPROMO the box and be good to go.

Migrate the data back if you need to and recreate the shares.

If you have the luxury, leave SQL on whichever server you moved it to. If you don't have one then you will need to restore the DBs from that backup.

It seems duanting but really not that big of a deal. You just want to be REAL careful with SQL.

I've done this before and the only time I had an issue was when a customer already had AD problems to begin with.

Best of luck.
Let me know how it turns out.

by davidb

Thanks for the reply.

We don't have the luxury of extra servers to seperate SQL from the DC. Will I be able to use the same server name for the DC when rebuilding it or will that cause issues? SQL does replication/DTS jobs to other SQL servers which is another reason we want to keep the same server name. Do you think SQL will get angry because of rebuilding the server with the same name?(SID problem?) or does SQL mainly look at the name when being references in replication jobs, etc.

by bart777

Yes you can reuse the name. The only reason that would prevent you is if you cannot gracefully demote this box from AD. If you have to sieze the roles to the other server then the name may have to change.

I'm not sure how SQL will behave. It will obviously depend on the applcation calling it. It SHOULD be fine though. I would say that I'm 99% sure it would move without error. This is the normal process for migrating DBs from one server to another. Most times I've moved SQL from server to server it's only looked at the DNS name. It didn't care about the servers SID.

I wouldn't worry about it too much.

This discussion is closed to new replies.