Link to home
Start Free TrialLog in
Avatar of RTM2007
RTM2007Flag for Afghanistan

asked on

Attempting to Xfer Primary DC/NTDS Roles from Domain/Forest - Old DC Still Shows NTDS Pull

So we consolidated the DCs in our environment to clean-up somethings.

We have a primative DC (GC) named: DC3 that we want to decommission but before we do want to make sure all the roles are off of it. We recently created a new DC1 and now that has been tasked as the "primary domain controller" (obviously no such thing in 03 environments).

When we go into AD Sites & Services however, the replication still shows from servers that it is "From Server" DC3.

Our business recovery site (separate site, same forest) still shows it as "Replace fro: Server: DC3" under the <automatically generated> Properties/NTDS Settings of our BR_DC server.When we try to manually change the setting it infoms us that it was auto generated by the directory service and to overwrite (which we don't want to do).

One thing I noticed is that under the properties of DC3 (old server) it shows that "This server is a preferred bridgehead server for the following transports" and lists IP. The new DC (DC1), doesn't shw it as a bridgehead server for any transports. Should that be changed manually? Is that as easy as going to the properties of DC1, adding IP to the list, apply OK?

Avatar of dhoffman_98
dhoffman_98
Flag of United States of America image

If you don't do anything, Windows 2003 AD uses it's built in ISTG (Inter-Site Topology Generator) to come up with a scheme so that each site has a primary replication partner.

However, you do have the ability to manually specify that a particular machine should be the preferred bridgehead.

Even if you were to leave this alone, it shouldn't cause a problem for you. If your goal is to take DC3 offline and decommission it, then the ISTG would automatically rebuild the replication partners and DC1 would become the replication partner automatically.
Avatar of RTM2007

ASKER

Well I wanted to NOT manually create the link to as a bridgehead. I was pretty sure that it would re-create itself as well, but alo wanted to see if there was any way to "manually" force auto sync to the new DC>
ASKER CERTIFIED SOLUTION
Avatar of dhoffman_98
dhoffman_98
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of RTM2007

ASKER

Nice I will give that a try. But I did notice that DC3 was still using the "IP transport" mechanism while DC1 was not