Best procedure and config of soon to be purchased DC.

We have 2 DC's here, the one does all DNS, DHCP and the other is has Exchange installed. THe main one that does the DNS and DHCP is going to be replaced. I know fom reading on here that you can/should possibly split the loads of DNS, DHCP to each DC.

COuld some one recommend a correct procedure/configuration to do this.

1. Should i just take the DNS, DHCP roles off the old one in the holidays and install them on the the new DC and split them later?
2. Should i then DCpromo the old server and just leave the two DC still.? (i was told 3 is over kill for our network)

I have been left to do this as our NM is off long term sick and no one knows when he will be back.

I just need advice on the best way/time/process to do this please.

I would say two DCs both DNS servers. As far as DHCP goes I have one currently and a backup of the config. The touted best practice is an 80/20 % split between 2 servers. I know some people do a 50/50 split as well.
Preferably dont have your Exchange server as a DC. It works fine as you well know but it is advised against for certain reasons.

I'd agree with Chris and in fact follow all of those recommendations apart from the Exchange on a DC thing (it was the only available server at the time :()

DNS (and WINS if you still use it) on both DCs and DHCP with the failover configuration. I'd also put GCs on both as well.

One thing to take into account, does the DC you're replacing hold any FSMO roles? If it does, I would install Windows on the new machine first, transfer the FSMO roles over to the new server then demote the old one. If you don't, interesting things will happen to your network

Ok, seems to be more work involved than i thought.

They to put Exchange on a DC because it was the only available server at the time.

Dont be daunted by the FSMO roles it wont take that long to transfer them. You are best using the NTDSUTIL for that as well just google those terms and you will find a suitable guide.

Just been looking, lol

I prefer to do it the GUI way i think. I know that the one DC in question at work holds all 5 FSMO roles.

I will look into sharing the roles or possibly giving them all to the brand new DC when it comes and is configured.

Questions,

1. If i transfer all the roles to the new DC will it have any affect on the second DC that is runnign Exchange?
2. Should i get the new one up and running with AD etc ( si iw ill have 3 DC's for a short while) before i DCpromo the old DC


I suppose my next Google will be to look for info on sharing the DNS and DHCP on 2 servers.

All good fun and experience................at least the longer he is off sick the more i get to do........lol

1) Shouldn't do, no
2) I would personally

Sharing DNS on two servers is dead easy, especially if you integrate your DNS into Active Directory. It would just be a matter of installing DNS on Windows and that would be pretty much it.

DNS takes a while to replicate, you don't need to create a zone with the wizard if your zone is ad integrated (which it most likely is). Just wait :)

If exchange is installed on a dc it can increase the shutdown times to around 20-30 minutes. I've seen it happen on a test server :o There is a kb about it.

Quote:

---

Originally Posted by ChrisH

Dont be daunted by the FSMO roles it wont take that long to transfer them. You are best using the NTDSUTIL for that as well just google those terms and you will find a suitable guide.

---

Daniel Petri has a good guide to transferring FSMO roles as well as loads of other useful stuff.

Quote:

---

Originally Posted by DMcCoy

DNS takes a while to replicate, you don't need to create a zone with the wizard if your zone is ad integrated (which it most likely is). Just wait :)

If exchange is installed on a dc it can increase the shutdown times to around 20-30 minutes. I've seen it happen on a test server :o There is a kb about it.

---

The trick is to stop all the exchange services before shutting down.

Im pretty sure you can only transfer about 3 of the FSMO roles using the GUI.

@Chris Thanks for your help so far, You can transfer all 5 roles via GUI according to the link AJ provided.

I have a script that huts down all the Exchange sevrices before i do reboot/shutdown, i have no delays because of this. If anyone would like hte script let me know.


While we are on the subject does anyone know of any good links that will rum me through splitting current DNS and DHCP to 2 servers?

I stand corrected. You need to use more than one of the GUIs is what I should been thinking of as one does three of them and you have to go elsewhere for the others.

DNS:

You dont split DNS you just set it up on another server and they will replicate with each other as long as you set up the entries on the name server tab etc.

As for DHCP it just a case of splitting the scope between two server so....
Say you currently are dishing out a range of :
192.168.0.1-192.168.0.100

You would simply reduce that servers scope to

For an 80/20 split

192.168.0.1-192.168.0.80

and on the new server set up

192.168.0.81-192.168.0.100

or the 50/50 split in the obvious way.

I'd be interested in that script Kyle.

Always wondered why our mail server was so slow to shut down compared to the rest of them.

Will the new DC automatically be a Global Catalogue server, or do you not have to set it up as such?