Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

XADM: Directory Replication Takes Too Long

View products that this article applies to.


This article explains why, depending on the Directory Replication topology, the time required to replicate directory changes to all parts of a Microsoft Exchange Organization may be several days.

↑ Back to the top

More information

Consider the following two Directory Replication topologies.

Topology A: Hub
Site X  <------->  Site W   <------> Site Z
                    Site Y

Topology B: Cascade
Site W  <----> Site X  <---> Site Y  <-----> Site Z

In each of the above topologies, the arrows indicate a directory replication connector. Assume that each connector is scheduled to replicate at one time during the day.

In Topology A, if a new mailbox is added to Site X, the maximum delay for that directory entry to be propagated to all the other Sites would be 2 days (one day for each directory replication connector hop).

In Topology B, if a new mailbox was added to Site W, the maximum delay for that directory entry to reach all the other sites (specifically Site Z) would be 3 days.

Hence, the time required to propagate directory changes to all sites in an Exchange Organization depends on the replication schedule as well as the number of hops involved and the number of hops depends on the Directory Replication Topology.

↑ Back to the top


Retired KB Content Disclaimer
This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.

↑ Back to the top

Keywords: KB148381, kbinfo, kbenv

↑ Back to the top

Article Info
Article ID : 148381
Revision : 6
Created on : 10/28/2006
Published on : 10/28/2006
Exists online : False
Views : 373