Windows Server 2022 AD Sites and Services Replication Topology Not Updating – Fix & Prevention

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Environment & Reproduction
3. Root Cause Analysis
4. Quick Triage
5. Step-by-Step Diagnosis
6. Solution – Primary Fix
7. Solution – Alternative Approaches
8. Verification & Acceptance Criteria
9. Rollback Plan
10. Prevention & Hardening
11. Related Errors & Cross-Refs
12. References & Further Reading

Symptom & Impact

KCC does not generate expected connection objects, replication latency rises, and directory changes take too long to converge across sites. Authentication and policy consistency are affected in branch offices.

Environment & Reproduction

Seen after site/subnet changes, stale site links, or DC IP readdressing. Reproduce by moving a subnet to the wrong site and forcing KCC recalculation.

Root Cause Analysis

Common causes are incorrect site-subnet mapping, disabled bridgehead assumptions, and DNS records pointing to outdated DC addresses. AD topology logic then optimizes around bad metadata.

Quick Triage

Run repadmin health checks, validate subnet mappings in Sites and Services, and verify SRV records for each DC before making topology edits.

Step-by-Step Diagnosis

Check replication failures by naming context, confirm each DC appears in the intended site, and inspect site link costs and schedules for blocked windows.

Solution – Primary Fix

Correct subnet-to-site assignments, clean stale connection objects, force KCC recalculation, then run an immediate replication cycle to restore normal convergence.

Solution – Alternative Approaches

If topology remains unstable, temporarily reduce site link costs for preferred paths and pin bridgehead servers while network remediation is completed.

Verification & Acceptance Criteria

repadmin shows no sustained failures, connection objects reflect design, and object changes replicate between all sites within the expected SLA window.

Rollback Plan

Revert recent site/subnet edits from change log, restore prior site link costs, and remove only newly created connection objects if behavior worsens.

Prevention & Hardening

Require change control for AD Sites and Services updates, keep subnet inventory synchronized with IPAM, and run weekly automated replication topology audits.

Related Errors & Cross-Refs

Often appears with RPC 1722 replication errors, DNS SRV lookup issues, and SYSVOL replication lag. Resolve naming and transport dependencies first.

Related tutorial: View the step-by-step tutorial for Windows Server 2022.

View all Windows Server 2022 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Use Microsoft Learn guidance for AD replication, repadmin, and site topology planning as baseline runbook references for ongoing operations.