Question on AD replication

hi

i had questions on ad replication hoping me with.

i have multi-domain forest, company.com, child domains eu.company.com, us.company.com , jp.company.com

in eu.company.com, have ad sites set in germany, uk, france, holland , switzerland. each site has 2 dc's apart swizterland has one.

if check ad sites , services, can see ip site link between uk , switzerland. there no preferred bridgehead servers. in ntds settings of swiss-dc1, can see entry replicate uk-dc1 (and likewise uk-dc1).

question 1: mean swiss-dc1 *only* replicate to/from uk-dc1? or replicate other uk dc's too?

question 2: recently, france had 3 domain controllers, 1 decommisionned , dcpromo'd down. can't see ip site link between france , switzerland. possible france-dc3 set replicate swiss-dc1, , when france-dc3 removed ad, site link automatically removed too?

question 3: if go inter-site transports > ip > properties, can see 'bridge site links' has been ticked. mean dc's can replicate other dc's aren't mentioned in ntds settings properties?

question 4: if go dc, ntds settings, can see other dc's set replicate from. meaning of if can replicate other dc's in forest/domain?

thanks in advance!

howdie!

1-if haven't changed the default setting of "bridge site links" domain controllers replicate through the bridgehead servers. if 1 of them fails, ad go elect dc in site new bridhead server. if see swiss-dc1 has entry uk-dc1 that's replicates to/from.

2-when dc fails, site link isn't affected. what's affected connections between dcs in sites cross site link. if dc3 bridgehead server , dies, ad going elect bridgehead server. kcc automatically. site link stays same.

3-it means that, in order reach destination dc, source dc may create additional connections if dc on "replication route" fail. if basl enabled , have topology a-b-c a,b replicate , b,c replicate data - , b failes, kcc automatically generates connections between , c. "bridge site links" makes sense if have routed network. otherwise may replication errors since , c can't talk each other.

4-replication "pull" based. dcs notify direct replication partners if have changes on ncs host. the notified dcs notification , "pull" changes off dc notified them. means "replicate from". created dual connection between dcs - make sure both "replication directions" work.

cheers,
florian

---

microsoft mvp - group policy (http://www.frickelsoft.net/blog)

Windows Server  >  Directory Services