Moved DC to another Site, Role in AD?

[astull]

We have 4 sites, our main site where i am, has 2 DC's. DC1 is a GC with DHCP and DNS running, DC2 is our file server, also a GC with DNS running. At the 3 other sites basically we have 1 DC at each performing the sames roles as the 2 we have here. My main question involves replication but any other suggestions are welcome. Here is what happened.... We recently close one of our offices and moved the remote DC to our main site. We removed DHCP from the server and gave it a static IP to match our site, and turned it on ( still running DNS and Wins i believe, also a GC). Once it was up and running, we moved the server to the correct site using AD sites and services. Its been up and running for a few days, everything seems to work fine, but i noticed in the logs that DC2 cannot repilcate with the new DC3. I thought that was kinda weird, since DC1 has always been our main replicator. By that i mean that DC1 replicates to DC2 (our main site), and DC1 also replicates to all other remote sites, DC2 replicates to nothing else. So i started looking around in AD sites and services and sure enough, DC2 and DC3 are "automatically generated" to replicate with each other (under NTDS settings). So in short here is what is happening... DC1 -> DC2, DC1 -> DC3, and what i do not want DC2 -> DC3. I deleted the DC2 -> DC3 repication yesterday by removing them from the NTDS settings of each server, however today they came back. How can i permanently remove them?? And is there any thing else i should remove from DC3 such as DNS, or wins, or GC??

thanks for reading
Aaron

 

[dankelt]

I'm not quite sure I understand why you want to disable the KCC, but this is how you do it:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;242780

 

[Firm]

Hello,
The DCs choose their own replication partners, you might not be able to assign them partners. Generally replication partners are chosen based on primarily location and or fast links; this explains why DC2 is now automatically synchronizing with DC3.

You mentioned that DC1 is running DHCP server and DNS seerver and one of remote DCs (DC3) was a DHCP client. This will also explain why DC2 have not replicated with DC3 in the past.

Is there a reason why you would want to prevent this replication?

My guess is that if you remove the DC2 -> DC3 replication and that you revert DC3 back to a DHCP client, the replication should stop.

Hope this helps.

 

[astull]

the only reason i quesitoned the DC2 -> DC3 replication is before this move, all replication involved DC1 ( it was the central point of replication ). so if we had to make a change in AD or wanted to check something, DC1 was the place to check. Of course this was prior to the move and to this point there had never been 3 DC's in one site. I did find a MS document that talks about 3 DC's in one site, something to the fact that for each DC there is 2 connections, just in case something would happen to one DC the other 2 could replicate. makes sense to me. So as far as the repication from DC2 -> DC3, i'll leave it alone. Is there any other suggestions about removing DNS, WINS or GC from the new DC3. Currently at this site there are 3 GC's 3 DNS servers, and 2 WINS servers. Everything seems to be running ok now, log files are clean of errors.

thanks for the help
Aaron