RE: AD <Automatically generated> site replication links

I would avoid disabling the KCC. Need to understand a bit more about your
setup to try and understand why the connections objects are being created.
Can you confirm?

1) Number of domains in your forest
2) Number of sites
3) Outline of the site links you have created - along with sites involved,
costs and schedule

In addition, have you fired up replmon. It will tell you why the KCC
generated a particular inter-site replication object.



"Nicolas Heyer" wrote:

that's the point.

We would like to force AD replication to reflect our topology. So we
manually created site links to do so, but as mentionned in the first post,
new site links are automatically generated after a while and these links use
a server in an outside location with relative slow connexion as their
favorite replication partner.

...And each site link that we create has just 2 sites, one on both end. I
found a documentation in the knowledge base that allows the disable the KCC
to create site links by itself...

but if there is another way, it would be nice...

Regards
Nicolas

"Steve B" wrote:

First point to note is that site links determine the inter-site replication
map. The KCC then uses this 'map' to create connection objects. Are you
creating connection objects manually?

Also, can you provide some more information on the site links you have
created. Sounds like you have multiple sites in one site link.

"Nicolas Heyer" wrote:

Hello

we have several locations that are all connected to our central main office
in a star tolopigy. All our windows DC server are installed with Windows
Server 2003 R2. Sites based on subnets have been created and we would like
all the servers in the outside locations to replicate from the main office.

One server in our main office has all the 5 FSMO roles.

If we manually configure the site links to replicate as we would like it to
be, we remark that after a few hours, the system creates additionally
<automatically generated> links where the main server is located outside the
main office and connected over a "relative" slow link when compared to other
links.

Why does AD ignore the actual configuration and tries to create its own
replication topology ? Is there a way to get over it ?

Thanks for any reply
Nicolas
.

Relevant Pages

  • Re: Migration coming - NT4 to WIN 2K3 - site config question
    ... build in the datacenter. ... you do this before your server goes out. ... In addition to creating sites and subnets you should also create site links. ... will it create connection objects that are appropriate from ...
    (microsoft.public.windows.server.active_directory)
  • RE: AD site replication links
    ... You could also look at weighting the replication links so that you'll have ... Outline of the site links you have created - along with sites involved, ... It will tell you why the KCC ... All our windows DC server are installed with Windows ...
    (microsoft.public.windows.server.active_directory)
  • Re: Role Transfers II [WILDPACKET]
    ... Think of site links as routes and connection objects as the data path over ... You create site links in AD Sites and Services. ... If your hub site is A, and you have child sites B - U, you need connection ...
    (microsoft.public.windows.server.active_directory)
  • Re: AD Replication Tips and hints
    ... -I think that manually removing the DCs from AD and From the DC itself and add it again is the safest way to solve that, however if cleanning DCs means that you must clean Domains, that could be a big problem... ... you must customize how Active Directory replicates information by setting up site links. ... transitive connections between two or more sites that mirror the network links and allow replication to occur. ... Once you have created site links, the KCC will then automatically generate the replication topology by creating the appropriate connection objects. ...
    (microsoft.public.windows.server.active_directory)
  • Re: moving to MPLS network
    ... Without having a full understanding of your network ... MPLS gives you the benefits of meshed/fully routed topology... ... connection objects). ... ALL AD site links were manually created ...
    (microsoft.public.windows.server.active_directory)