I was formerly a single site, single domain, using 5 Windows 2000 DCs. For a
couple of reasons, I'm placing Windows 2003 R2 DCs at my two remote sites
(we'll call them REMOTE1 and REMOTE2). Both are connected back to main site
(we'll call it MAIN) by 100MB microwave links (hub and spoke, if you will).

I created two new sites, and associated the correct subnets to them, but I
think I made a mistake by leaving the default site link with all three sites
in them. The auto generated replication that took place was fine for
REMOTE1 - it found a partner on a DC at MAIN.

But REMOTE2 created a link to REMOTE1. Besides the extra hop and traffic on
the microwave, problem is, since my physical connections are hub and spoke,
if the microwave to REMOTE1 goes down, so does replication to REMOTE2.

I tried manually creating replication partners the way I thought they should
be (DC at REMOTE1 to DC at MAIN, DC at REMOTE2 to another DC at MAIN), but
it doesn't appear as though the DCs at the remotes are picking up on the
changes. And if I try to replicate manually, I get this error:

The following error occurred during the attempt to synchronize the domain
controllers: The naming context is in the process of being removed or is not
replicated from the specified server.

Then I got to thinking about the site links. If I had two site links, one
with MAIN and REMOTE1 and the other with MAIN and REMOTE2, the auto
generated replication partners probably would have come out fine, right?

So I've done that...two site links now, each with two sites as above...but I
still need to fix the above error. Should I just DCPROMO down the two DCs at
the remote sites, delete the links I manually made, and because I have two
site links properly defined everything should be okay?

Thanks in advance,
Bruce

Re: Changing replication partners mess by Bruce

Bruce
Fri May 09 08:51:23 PDT 2008

Sorry, I left out the obvious last step...I would promote the servers back
to DCs...

Bruce