Skip to content

Fixing Latency & Site Links

Active Directory replication latency and site link issues are common challenges in multi-site environments, often caused by misconfigured schedules, suboptimal replication intervals, or network constraints. Properly tuning site link properties and replication schedules ensures efficient data synchronization across domains. This section covers strategies to adjust site link schedules, optimize replication intervals, and reduce latency.


Site link schedules determine when replication occurs over a specific site link. By default, replication is scheduled during off-peak hours (23:00–05:00), but this may not align with your network's usage patterns. Adjusting schedules to match low-bandwidth periods can reduce latency.

Use dsmod to update the schedule for a site link (e.g., SiteLink1):

dsmod sitelink "SiteLink1" -schedule "02:00-06:00"
This sets replication to occur between 2:00 AM and 6:00 AM. Ensure the schedule avoids peak hours for your network.


Optimizing Replication Intervals

The default replication interval is typically 15 minutes, but this can be adjusted based on network bandwidth and update urgency. Increasing the interval reduces replication traffic but may delay updates. Conversely, shorter intervals improve freshness at the cost of bandwidth.

Example: Changing the Replication Interval

Use repadmin to set the interval for a site link (e.g., SiteLink1):

repadmin /setsitelinkinterval "SiteLink1" 30
This sets the interval to 30 minutes. Always test changes in a non-critical environment before applying them broadly.


Site link costs influence which links are used for replication. Lower-cost links are prioritized, so ensure your most reliable and high-bandwidth links have the lowest costs.

repadmin /showsitelink
Check the Cost column. If a link has a higher cost than another with better connectivity, adjust it using:
dsmod sitelink "SiteLink1" -cost 10
This sets the cost to 10, making it a preferred path for replication.


Using Repadmin to Monitor and Force Replication

The repadmin tool is critical for diagnosing and resolving replication issues. Use it to force replication, check replication status, and identify delays.

Example: Forcing Replication

repadmin /syncall "DC01" /e /a
This forces replication from the domain controller DC01 to all other domain controllers. Use /e for extended replication and /a to include all partitions.


Key takeaways

  • Adjust site link schedules to align with network usage patterns to minimize latency.
  • Optimize replication intervals based on bandwidth availability and update urgency.
  • Prioritize low-cost site links to ensure efficient replication paths.
  • Use repadmin for real-time monitoring, troubleshooting, and forced replication.
  • Test changes in staging environments before applying them to production to avoid unintended disruptions.