z The logic of the one-way Connection Agreement was not designed to
support two-way replication. A one-way Connection Agreement assumes
that the source object is authoritative, and the target object is not, while
a two-way Connection Agreement treats the objects in both directories
as possible sources.
z One-way connection agreements do not support timestamp checking.
Timestamp checking is the process that a two-way Connection
Agreement uses to ensure that if matching objects are modified in both
directories between replication cycles, the latest change will apply.
Article ID: 303180 - Last Review: October 25, 2007 - Revision: 3.5
Active Directory Connector Connection Agreement Requirements for
Mixed Administrative Groups
This article was previously published under Q303180
Running Exchange 2000 Server or Exchange Server 2003 in mixed mode allows
coexistence with earlier versions of Microsoft Exchange Server. This article is
intended to document the Active Directory Connector (ADC) configuration
requirements for organizations that have Exchange 2003 servers, Exchange
2000 servers, and Exchange Server 5.5 or earlier computers. For the purposes
of this document, the term "mixed site" refers to an administrative group that
has at least one Exchange 2000 or Exchange 2003 server installed that is
running a Site Replication Service (SRS). This administrative group may also
have additional Exchange servers.
Every Mixed Site Must Have a Two-Way Connection
To allow proper replication between Active Directory and the Exchange Server
5.5 directory, every mixed site in the organization must have a two-way
Connection Agreement configured. The server specified under Exchange
Server information on the Connections tab of the Connection Agreement
properties must be either an Exchange Server 5.5 computer or an SRS server in
the mixed site. Note that the SRS server is hard-coded to use port 379 for
Lightweight Directory Access Protocol (LDAP) traffic, so if you choose to use an