AutoCreated Server Connector

  • Thread starter Thread starter Mike
  • Start date Start date
M

Mike

Can not remove autocreated NDTS server connections. Our
domain consists of an empty root, and 3 child domains
with resources, USA, Europe, and Asia. Each domain has
at least 2 DCs. Site Links are IP. We have the
following sites, NFK, VB, Rich, Atl, Rec, Mir, HKG, LON,
Wse. the site that is autocreating is NFK. The problem
occurs when I create 2 server objects in NFK to ATL, one
in USA domain and one in root domain and create the
partner objects, then delete the autogenerated server
objects for the LON, HKG, MIR sites and delete NFK from
the same sites. After a directory update occurs new
autocreated server objects are show up again for LON,
HKG, and MIR. The IP site link is ATL-NFK, and no direct
link exists to any other site from NFK. I've changed the
server objects from autocreated to Admin created, deleted
and again the objects are recreated.

Thanks in advance for help/ideas to troubleshoot.
 
Here's some information about the way that KCC creates and
manages connection objects. If you only want manually
created connection objects then you can disable the KCC
for intersite replication.
Steve



The KCC attempts to build a spanning tree for all naming
contexts (domain, schema, and configuration). Generally,
the spanning tree algorithm strives to have one intersite
connection between any two pair of sites. However, the KCC
or an administrators may create duplicate connection
objects between a given pair of Active Directory
replication partners in the same domain.


The KCC may create duplicate connection objects in the
following situation: Two systems in a site, both believing
that they are the site topology generator, each make a
connection on behalf of a third server in the site that is
the real bridgehead. When the partition clears up, a
duplicate connection on that bridgehead to the same remote
server may exist for a brief period until the KCC cleans
up the unnecessary one.


An administrator may create duplicate connection objects
when more than one administrator, typically at different
Active Directory sites, adds manual connection objects.
Or, seeing no KCC-generated connection, the administrators
add manual connections in a remote site where a KCC-
generated site has not yet been replicated.


Administrator-generated connection objects are never
removed or overridden by the KCC.


The KCC manages duplicate connection objects in the
following manner:



- It favors administrator-created (manual) connection
objects over
automatic connection objects.

- If more than one manual connection object exists, it
uses the last
one (newer over older).

- If more than one connection object exists with same
create time and
type (manual or automatic), it arbitrarily selects one
(with manual
connections favored over KCC-generated connections).




If multiple connections exist between <Computer 1> and
<Computer 2>, FRS treats it as an invalid configuration,
skipping both connections and halting outbound replication
on the server(s) that are experiencing duplicates. If
these connections are generated by the KCC, the redundant
connection is eventually removed. Manual connections that
are created by an administrator are not deleted by the KCC.
 
-----Original Message-----
Here's some information about the way that KCC creates and
manages connection objects. If you only want manually
created connection objects then you can disable the KCC
for intersite replication.
Steve



The KCC attempts to build a spanning tree for all naming
contexts (domain, schema, and configuration). Generally,
the spanning tree algorithm strives to have one intersite
connection between any two pair of sites. However, the KCC
or an administrators may create duplicate connection
objects between a given pair of Active Directory
replication partners in the same domain.


The KCC may create duplicate connection objects in the
following situation: Two systems in a site, both believing
that they are the site topology generator, each make a
connection on behalf of a third server in the site that is
the real bridgehead. When the partition clears up, a
duplicate connection on that bridgehead to the same remote
server may exist for a brief period until the KCC cleans
up the unnecessary one.


An administrator may create duplicate connection objects
when more than one administrator, typically at different
Active Directory sites, adds manual connection objects.
Or, seeing no KCC-generated connection, the administrators
add manual connections in a remote site where a KCC-
generated site has not yet been replicated.


Administrator-generated connection objects are never
removed or overridden by the KCC.


The KCC manages duplicate connection objects in the
following manner:



- It favors administrator-created (manual) connection
objects over
automatic connection objects.

- If more than one manual connection object exists, it
uses the last
one (newer over older).

- If more than one connection object exists with same
create time and
type (manual or automatic), it arbitrarily selects one
(with manual
connections favored over KCC-generated connections).




If multiple connections exist between <Computer 1> and
<Computer 2>, FRS treats it as an invalid configuration,
skipping both connections and halting outbound replication
on the server(s) that are experiencing duplicates. If
these connections are generated by the KCC, the redundant
connection is eventually removed. Manual connections that
are created by an administrator are not deleted by the KCC.
.
I'm still not clear as to why some sites are recreating
Click to expand...
connections and others are not ie 12 total sites and this
is the only site that is doing this?
 
Back
Top