Change KCC Auto Generation

[PU36]

We currently have 6 DC in 6 different sites.

Out Main Site "MainSRV" is the HQ of the entire operation and hold all FSMO roles forest wide. All changes to AD occur at the MainSRV location. When you look in the AD Sites and Services the KCC has generated the replication topology so that MainSRV replicate to RemoteSite1. However, RemoteSite1 has a replication topology that replaces to EVERY other DC.

MainSRV -> RemoteSite1
RemoteSite2 -> RemoteSite1
RemoteSite3 -> RemoteSite1
RemoteSite4 -> RemoteSite1
RemoteSite5 -> RemoteSite1
RemoteSite6 -> RemoteSite1

then

RemoteSite1 -> RemoteSite2, RemoteSite3, RemoteSite4, RemoteSite5, RemoteSite6, MainSRV

It is posible to tell the KCC to use MainSRV to be the "Hub" of replication?

 

[ShackDaddy]

Manually set up site link bridges in AD Sites and Services so that each site only has one replication path (to MainSRV).

KCC creates what you haven't created. If you turn off automatic bridging (get properties on IP and SMTP in the InterSite Transports container) and manually set up a site link cost arrangement (using site link bridges), KCC will have less leeway to screw things up for you.

If your WAN speeds are relatively similar, KCC will be pretty random on how it sets things up if you let it.

ShackDaddy