Setting up Copy Domain Controller for new site

[siphongwenya]

Hi All,

I've got 2 domain controllers at our site (about 120 users), half the company is moving to another location. the two groups only share domain controller. I would like to leave the domain controllers at the old site and setup a new one for the new site. Can i just add another controller to to the current site and change the ip address when moved to the new site. Will that work

I dont want to change anything on the workstations

 

[irBosOtter]

Yes just add a 3rd one at the remote site, and make sure the IP ranges are specified under sites and services for the respective sites

 

[DMNknight]

There are several things to keep in mind here:
With 120 users you really shouldn't need a 3rd domain controller. Just move your second DC to the new site. As long as your memory is greater than or equal to your NTDS database size, your DC should be able to handle 5000 concurrent users.
Really, you don't need a third DC.

Before you move the DC and before you change it's IP address, make sure all your networking is in place.
Change the Primary DNS IP address of the DC that is being moved, to the one that is staying. This is to enable the DC at the remote site to authenticate with the remaining DC over the WAN.
Change the IP address on the DC to it's new IP address for the remote site and shut down and then physically move it.

All things going well, your DC will start up no problems at the remote site. Be sure to check for replication issues via dcdiag and repadmin.

In Sites and services, be sure to create the new site and it's associated IP range. Move the Remote DC object if it doesn't update by itself.
Make sure the KCC creates the replication paths.

Monitor your replication and dcdiag's. They will be your first warning signs of issues.