Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 359
  • Last Modified:

Adding a DC, Sites and Services

I am in the process of adding a Server 2003 DC to our existing 2000AD domain. Some info on our current config: We have three DC's, one on our main campus, and two at remote locations, connected by dedicated T1. The plan is to add a Server 2003 DC to the main campus vlan, let it run for a few days to make sure there are no issues, bring down the existing main campus DC (old hardware), bring up another Server2003 controller for the main campus, and upgrade the remote locations DC's to Server2003.

My question involves how the AD connections in Sites and Services should be configured now that there will be two DC's on the main campus vlan. Currently I have Sites setup for the main campus and the two remote locations, with the appropriate links between them. When I added the new Server2003 DC I noticed that it auto-created a link between itself and the current main campus DC, but did not create links to the two remote location DC's. Not surprising I suppose, but do I need to create them? Or is such a thing only recommended when a DC is acting as a bridgehead?
0
mvogts
Asked:
mvogts
  • 2
1 Solution
 
CharliePete00Commented:
I'm guessing that you manually created links between the sites?  Are you also using scheduled replication?

There are only 2 real reasons to manually create  diffrent sites.
1.  To control bandwidth by using scheduled replication
2.  To control the flow of replication (ex - to make sure remote sites replicate with a central site instead of other remote sites)

If there is no real need for either you may wish to consider a single site and let the KCC manage the links.

Since you are planning to retire the existing DC you will need to add links between the new DC and the DCs at the remote sites to maintain your existing configuration.  You should then remove the links to the old DC (before retiring it anyway), move any FSMO and GC server roles to other DCs, DCPROMO it down (demote it from a domain controller), and remove it fom the domain -  making sure to wait for (or force) repliction between each step.

If you haven't done so you may want to look into establishing global catalogue servers at each site.  This will help reduce traffic between sites.

Good luck!
0
 
mvogtsAuthor Commented:
Bandwidth really isn't an issue, but we would like the remote DC's to get their replication from our main site one, since the vast majority of DC changes are done here. What you say is what I suspected but I just wanted to make sure I wasn't overlooking something obvious. Thx.
0
 
CharliePete00Commented:
It always help to get a reality check.

Good Luck!
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now