Re: site replication

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Thanks to all of you for your quick response.
Joe


"Chriss3 [MVP]" <removethis_christoffer.andersson@xxxxxxxxxx> schrieb im
Newsbeitrag news:35D467FD-B99C-4420-9135-63255B434884@xxxxxxxxxxxxxxxx
In addition, connection objects will be created to at least one DC in each
domain if the DC also are a GC, since the GC need a partial set of
attributes and objects from each Domain/NC in the entire forest. KCC
mostly
dose it's job very well in Windows Server 2003, so there is no need to
worry
about connection objects mostly.

--
Regards
Christoffer Andersson
Executive Consultant - TrueSec
Microsoft MVP - Directory Services

----------------------------------------------------------------
http://www.chrisse.se - Active Directory Resources

"Jeremy" <jeremy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:A50DCB8A-D824-497A-945C-7E2B5FF408CF@xxxxxxxxxxxxxxxx
If they are automatic connectors then the KCC has created them to
minimse
replication lag. If you want to control how replication flows EG have
all
"spoke" sites replicate to a "hub" site then you can either manually
create the replication links (not recommended) or create a bunch of site
links between the hub site and each spoke site and leave everything
automatic. If you use this configuration then the intersite replication
connectors will only go between the linked sites. To ensure that
replication continues you should ensure that all site links are
transitive. This means that if Site A in connected to Site Hub and Site
B
in connected to Site Hub then Site A and Site B can make a routing
connection if there are no DCs available to replicate with in Site Hub.
Understand? If not let me know and I'll try to make it a bit clearer.

Cheers,
Jeremy.
"Joe" <kandelj@xxxxxxx> wrote in message
news:%23txxgX7kHHA.3264@xxxxxxxxxxxxxxxxxxxxxxx
Hi guys,

I´ve a question regarding the site replication between our dc´s.
We´ve a couple of sites and the current configuration is like that:
All the dc´s in the sites (subdomains) have connections to dc´s in the
headquater office
and also to other sites. My question is: Do we really need these
connectors
from one site into another site
or is it sufficient only to configure connectors from the site dc to
the
headquater dc´s?
Many thanks in advance.

Joe






.

Relevant Pages

  • Re: cannot remove SRS
    ... > This issue can occur if there is any trace of directory replication ... > 2) Expand the Configuration naming context, expand Services, expand ... > 6) Follow the same procedure for other administrative groups. ... >> Replication Connectors, ...
    (microsoft.public.exchange2000.setup.installation)
  • Re: cannot remove SRS
    ... > This issue can occur if there is any trace of directory replication ... > 2) Expand the Configuration naming context, expand Services, expand ... > 6) Follow the same procedure for other administrative groups. ... >> Replication Connectors, ...
    (microsoft.public.exchange.admin)
  • Re: cannot remove SRS
    ... > This issue can occur if there is any trace of directory replication ... > 2) Expand the Configuration naming context, expand Services, expand ... > 6) Follow the same procedure for other administrative groups. ... >> Replication Connectors, ...
    (microsoft.public.exchange2000.win2000)
  • Re: site replication
    ... If you want to control how replication flows EG have all "spoke" sites replicate to a "hub" site then you can either manually create the replication links or create a bunch of site links between the hub site and each spoke site and leave everything automatic. ... If you use this configuration then the intersite replication connectors will only go between the linked sites. ... This means that if Site A in connected to Site Hub and Site B in connected to Site Hub then Site A and Site B can make a routing connection if there are no DCs available to replicate with in Site Hub. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Replication Message (Ver 5.5.1960)
    ... >The sites are connected by an Exchange server that has X400 ... >Connectors. ... >find any permanent solution. ... >replication schedule to delay the problem but this is not ...
    (microsoft.public.exchange.admin)