AD bridghead/replication changes

[Jim]

I have a root domain located in a central site (netowrk
hub) for a statewide network of 13 child domains. AD
replication always had chosen one the the root DC's with
the site links going to the remote locations. Somehow a
remote site, not very well connected, has all of the
site links associated with it. KCC has apparently made
this change for some reason.

I previously had in place for months a spoke/hub and ring
configuration of site links and set all DC's in each site
as IP bridgeheads. Is there any way to force AD to
select DC's in the central site only? Can I force AD to
reconsider it's decisions? I thought maybe adjusting the
cost on the site properties might help. Thanks.

 

[Tim Springston [MSFT]]

Hi Jim-

Have you defined IP subnets associated with the respective sites? That
would be the first thought. That way, the clients (and DCs) would discover
their site based on their own subnet matching one defined in AD, and give a
natural preference to DCs in their own site.