AD and KCC Problem

[V]

All,

I am not sure if this is by design from Microsoft, but I need to ask
this because it is driving me crazy.

Here is the scenario:

I have 3 AD sites, loacted in NY, London, and Hong Kong. Here is the
breakdown od each site:

Primary: NY-Site-DC1, NY-Site-DC2

Backup: LN-Site-DC1, LN-Site-DC2

Remote: HK-Site-DC1

Currently, NY-Site-DC1 is the primary DC where the KCCs are created.
Here are the KCC links:

NY-Site-DC1 <-> LN-Site-DC1
NY-Site-DC1 <-> LN-Site-DC2
NY-Site-DC1 -> HK-Site-DC1

But when I check the NTDS Settings on the HK-DC, it created a KCC link
to NY-Site-DC2. So it looks like this:

HK-Site-DC1 -> NY-Site-DC2

As I understand it, all the KCCs links should be created goiing to
NY-Site-DC1.

So how come, from NY-Site-DC1 there is a KCC link to HK-Site-DC1 and
on the return, if you will, there is a KCC link between HK-Site-DC1 to
NY-Site-DC2?

I restarted all DCs in all there sites and it still re-established the
links the same way. What am I doing wrong?

Any help is very much aprreciated.

Thanks!

 

[Eric Fleischman [MSFT]]

Check out the branch office deployment guide for details, but you've
probably got one of two things going on:
1) A site link exists that links the two sites in question
2) "Bridge all site links" is enabled for the site links.

If either of them is linking the two sites where you don't want replication
to take place, it will cause the KCC to generate connection objects that
link the two sites in question.

Again, branch office deployment guide should have some details that would
probably help.

~Eric