Study guide
1.6 AD DS Replication: Topology Generation, Convergence & Diagnostics
Administering Windows Server Hybrid Core Infrastructure AZ-800
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
About Exam AZ-800: Format, Scoring & the September 2026 Retirement
2 Chapter 1: Active Directory Domain Services Architecture & Deployment
1.1 Deploying & Managing Domain Controllers On-Premises 1.2 Domain Controllers in Azure IaaS & Virtualized DC Cloning 1.3 Read-Only Domain Controllers (RODCs) & Password Replication Policies 1.4 Flexible Single Master Operation (FSMO) Roles & Troubleshooting 1.5 Active Directory Sites, Subnets & Site Link Topology 1.6 AD DS Replication: Topology Generation, Convergence & Diagnostics 1.7 Forest and Domain Trust Relationships
3 Chapter 2: AD DS Security Principals, Service Accounts & Domain Join
2.1 Managing Users, Groups & Objects in Multi-Domain and Multi-Forest Environments 2.2 Service Account Types & Group Managed Service Accounts (gMSA) 2.3 Joining Windows Server to AD DS, Microsoft Entra Domain Services & Microsoft Entra ID 2.4 Creating & Managing Users, Groups and Organizational Units at Scale
4 Chapter 3: Hybrid Identity & Microsoft Entra Integration
3.1 Microsoft Entra Connect Sync Architecture, Installation & Filtering 3.2 SourceAnchor, Synchronization Rules & Microsoft Entra Connect Health 3.3 Microsoft Entra Cloud Sync & Disconnected Multi-Forest Topologies 3.4 Hybrid Authentication Methods & Staged Rollout 3.5 Microsoft Entra Domain Services 3.6 Integrating Microsoft Entra ID, AD DS & Entra Domain Services: Choosing an Architecture
5 Chapter 4: Group Policy in AD DS and Hybrid Environments
4.1 Group Policy Architecture & Processing Order (LSDOU) 4.2 Group Policy Filtering, Loopback Processing & Client-Side Extensions 4.3 Group Policy Preferences, Item-Level Targeting & Central Store 4.4 Group Policy in Microsoft Entra Domain Services & Fine-Grained Password Policies
6 Chapter 5: Remote Server Management in Hybrid Environments
5.1 Windows Admin Center (WAC) Deployment On-Premises and in Azure 5.2 PowerShell Remoting, WinRM & the Kerberos Double-Hop Problem 5.3 Just Enough Administration (JEA) for Constrained PowerShell Endpoints 5.4 OpenSSH on Windows Server & PowerShell Remoting over SSH 5.5 Secure RDP Access, Remote Desktop Gateway & Azure Bastion
7 Chapter 6: Hybrid Management with Azure Arc and Azure Services
6.1 Azure Arc-Enabled Servers Architecture & Onboarding 6.2 Azure Machine Configuration & VM Extensions on Arc Servers 6.3 Azure Update Manager: Assessment, Maintenance Configurations & Dynamic Scoping 6.4 Azure Automation for Hybrid Workloads: Runbooks & Hybrid Runbook Workers
8 Chapter 7: Hyper-V Virtualization & Virtual Machine Configuration
7.1 Hyper-V Type 1 Architecture, Installation & Hardware Prerequisites 7.2 VM Generations, Secure Boot, vTPM, Enhanced Session Mode & Direct VM Access 7.3 Compute, Dynamic Memory & Hardware Acceleration 7.4 VM Resource Controls, CPU Groups & Host Compute Partitioning 7.5 Hyper-V Virtual Hard Disks & Checkpoint Management 7.6 Hyper-V Virtual Switches, NIC Teaming & Switch Embedded Teaming (SET) 7.7 Integration Services, Guest Components & Time Synchronization
9 Chapter 8: Hyper-V High Availability, Security & Containers
8.1 Hyper-V Failover Clustering & Cluster Shared Volumes (CSV) 8.2 Hyper-V Replica & Azure Site Recovery (ASR) 8.3 Guarded Fabric & Shielded Virtual Machines 8.4 Windows Server Container Hosts, Isolation Models & Images 8.5 Managing Container Instances & Linux Containers with WSL 8.6 Windows Container Networking & AKS Enabled by Azure Arc 8.7 Managing Container Images, Tags & Azure Container Registry
10 Chapter 9: Azure IaaS Virtual Machine Administration
9.1 Azure VM Sizing, Series Selection & Managed Disk Tiers 9.2 Azure VM Host Caching, Disk Bursting, Ephemeral OS Disks & Disk Operations 9.3 Azure VM High Availability: Availability Sets, Zones & Proximity Placement Groups 9.4 Virtual Machine Scale Sets, Autoscale & Azure Dedicated Hosts 9.5 Azure VM Networking, NSGs & Connectivity
11 Chapter 10: Hybrid DNS Infrastructure & Name Resolution
10.1 Active Directory-Integrated DNS Architecture, Dynamic Updates & Zone Types 10.2 DNS Records, Aging & Scavenging and the GlobalNames Zone 10.3 DNS Forwarding, Conditional Forwarding & Azure DNS Zone Integration 10.4 Hybrid Name Resolution with Azure DNS Private Resolver 10.5 Windows Server DNS Policies & DNSSEC
12 Chapter 11: IP Addressing, DHCP & IPAM Management
11.1 DHCP Server Role, the DORA Lifecycle & Active Directory Authorization 11.2 DHCP Scopes, Option Hierarchy, Reservations & Relay Agents 11.3 DHCP High Availability & Failover Configurations 11.4 IP Address Management (IPAM) Deployment & Auditing 11.5 Resolving IP Address Issues in Hybrid Environments
13 Chapter 12: Hybrid Network Connectivity, Remote Access & Private Access
12.1 Remote Access Role, VPN Protocols & Site-to-Site VPN to Azure 12.2 Network Policy and Access Services (NPAS), RADIUS & Policy Processing 12.3 Azure Network Adapter & Azure Extended Network 12.4 Web Application Proxy & Microsoft Entra Application Proxy 12.5 Microsoft Entra Private Access & Global Secure Access 12.6 Azure Relay & Hybrid Connections
14 Chapter 13: File Services, DFS, SMB & Azure File Sync
13.1 Windows Server File Share Access, NTFS Permissions & Access-Based Enumeration 13.2 File Server Resource Manager: Quotas, File Screens & Storage Reports 13.3 DFS Namespaces (DFS-N) & DFS Replication (DFS-R) 13.4 BranchCache: Distributed Cache and Hosted Cache Modes 13.5 Modern SMB Protocols, SMB Multichannel & SMB over QUIC 13.6 Azure File Shares, Tiers & Hybrid Permissions 13.7 Azure File Sync, Cloud Tiering & Monitoring 13.8 Migrating DFS Namespaces & DFS Replication to Azure File Sync
15 Chapter 14: Windows Server Storage Infrastructure & High Availability
14.1 Disk Partitioning, Volumes & Enterprise File Systems (NTFS vs ReFS) 14.2 Data Deduplication Architecture, Usage Types & Management 14.3 Storage Spaces & Storage Spaces Direct (S2D) 14.4 Storage Replica & Storage Quality of Service 14.5 iSCSI Target Server, IQNs, CHAP Authentication & Multipath I/O
1.6 AD DS Replication: Topology Generation, Convergence & Diagnostics
Key Takeaways Explain This Topic AI
The KCC evaluates the replication topology every 15 minutes; one Intersite Topology Generator per site builds the inter-site connections and nominates bridgehead servers.
Intra-site replication uses change notification and is uncompressed; inter-site replication polls on the site link interval and compresses payloads to save WAN bandwidth.
Tombstone lifetime is 180 days in forests created at Windows Server 2003 SP1 functional level or later; a domain controller offline longer than that must be forcibly demoted and metadata-cleaned, never simply reconnected.
Strict replication consistency (the default on modern forests) halts inbound replication and logs Event ID 1988 instead of reanimating a lingering object.
SYSVOL replicates through DFS-R; a domain still in FRS mode must reach the dfsrmig Eliminated state before a Windows Server 2016 or later domain controller can be promoted.
Last updated: August 2026
AD DS Replication: Topology Generation, Convergence & repadmin Diagnostics
Every domain controller holds a writable copy of the directory, so Active Directory is a multi-master database with no single authoritative source for ordinary object changes. Convergence is therefore not a background detail — it is the mechanism that decides whether a password reset in London is honoured in Seattle, whether a disabled account is really disabled everywhere, and whether an object deleted six months ago can be resurrected as a lingering object . This section covers how the replication topology is generated, how changes propagate and converge, and how to diagnose a partnership that has stopped working.
1. Intra-Site vs Inter-Site Replication Mechanisms
Active Directory enforces fundamentally different replication engines depending on whether traffic stays within a local site or crosses a WAN site link.
- Dimension Intra-Site Replication Inter-Site Replication
- Network Speed High-speed LAN (>= 100 Mbps) Low-speed WAN / Internet VPN
- Data Compression Uncompressed (saves DC CPU cycles) Compressed (compresses data to ~10-15% of raw size)
Notification Mechanism Change Notification (Push-based, near real-time) Scheduled Polling (Pull-based, periodic interval)
Notification Latency 15-second initial delay; 3-second delay per partner Governed by replication interval (default 180 min, min 15 min)
Topology Structure Dual-hop bidirectional ring topology Spanning tree generated by ISTG across bridgehead servers
Urgent Replication Triggers
Certain high-security directory modifications bypass all standard intra-site notification delays and inter-site polling schedules, triggering Urgent Replication immediately:
Account lockouts (to immediately block compromised accounts enterprise-wide).
Local Security Authority (LSA) secret changes.
RID Master pool allocation changes.
Changes to the Domain Password Policy.
Tip
Enabling Inter-Site Change Notification: By default, inter-site replication waits for the scheduled replication frequency (e.g., every 15 or 180 minutes). For high-speed fiber WAN links or Azure ExpressRoute connections, administrators can enable near-real-time Change Notification on inter-site links by editing the options attribute on the Site Link object in ADSI Edit or PowerShell, setting bit flag 1 (binary bitmask 0x1 ).
2. KCC, ISTG & Bridgehead Server Generation Mechanics
Replication connection objects are generated dynamically by background directory algorithms to ensure high availability and eliminate single-point-of-failure routing. +-----------------------------------------------------------------------------+
- | TOPOLOGY GENERATION ENGINES |
- | |
- | [KNOWLEDGE CONSISTENCY CHECKER (KCC)] |
- | - Runs on EVERY domain controller every 15 minutes |
- | - Builds intra-site ring topology (guarantees <= 3 hops between any DCs) |
- | - Creates dynamic <nTDSSettings> connection objects |
- | |
- | [INTER-SITE TOPOLOGY GENERATOR (ISTG)] |
- | - Exactly ONE domain controller elected per site |
- | - Evaluates inter-site links, cost matrices, and site schedules |
- | - Automatically elects BRIDGEHEAD SERVERS to replicate WAN traffic |
- +-----------------------------------------------------------------------------+
Knowledge Consistency Checker (KCC): A built-in process running on all DCs every 15 minutes . It evaluates the availability of replication partners and creates unidirectional inbound connection objects ( fromServer references). If a DC fails, the KCC automatically recalculates the topology to route around the dead DC.
Inter-Site Topology Generator (ISTG): In each site, one DC is elected as the ISTG. The ISTG generates the inter-site replication connection objects connecting bridgehead servers across site links.
Bridgehead Servers: The primary contact DCs that send and receive replicated data across site links. By default, the ISTG automatically elects bridgeheads dynamically. While administrators can manually designate preferred bridgeheads in Active Directory Sites and Services, doing so creates a single point of failure if the designated bridgehead goes offline.
3. Replication Diagnostics and Health Auditing with repadmin
The command-line utility repadmin.exe is the primary diagnostic tool for inspecting replication health, identifying replication latency, and resolving synchronization errors. +-----------------------------------------------------------------------------+
- | REPADMIN COMMAND CHEAT SHEET |
- | |
- | COMMAND DIAGNOSTIC PURPOSE |
- | ----------------------------+-------------------------------------------- |
- | repadmin /showrepl * /csv | Exports complete inbound replication status |
- | | and error codes for all DCs to CSV |
- | repadmin /replsum | Summarizes replication health, latency, and |
- | | largest replication delta across all DCs |
- | repadmin /syncall /AePd | Forces immediate synchronization across all |
- | | partitions, enterprise-wide, push/pull |
- | repadmin /kcc * | Forces immediate KCC topology calculation |
- | repadmin /showutdvec | Displays Up-to-Dateness Vector (high-water |
- | | USNs) to detect lingering objects |
- +-----------------------------------------------------------------------------+
- Essential Diagnostic Syntax Examples: :: 1. Check replication summary and identify failing DCs
- repadmin /replsum
- :: 2. Display detailed inbound replication partners and USN status for local DC
- repadmin /showrepl
- :: 3. Force full cross-partition synchronization using all topology paths
- repadmin /syncall /AdePq
- :: Switches: /A=All partitions, /d=Distinguished name, /e=Enterprise-wide (across sites), /P=Push, /q=Quiet
- :: 4. Force KCC recalculation on all DCs in the current site
- repadmin /kcc *
- 4. Convergence Mechanics: USNs, Watermarks and Dampening
Replication is driven by counters, not timestamps. Each domain controller keeps a local Update Sequence Number (USN) that increments on every originating write. Two vectors control what actually crosses the wire:
The high-watermark vector (up-to-dateness by partner) records the highest USN a domain controller has received from a specific partner , so each replication cycle asks only for "everything after N".
The up-to-dateness vector (UTDV) records the highest originating USN this domain controller has seen from every domain controller in the forest, identified by invocation ID.
Together these produce propagation dampening : in a ring topology a change that arrives at a domain controller from two directions is applied once and the duplicate copy is suppressed, because the UTDV already shows that originating write as seen.
When two administrators change the same attribute on different domain controllers inside the same replication window, Active Directory resolves the collision deterministically in this order:
Higher version number wins — the attribute's version increments on each originating write.
If versions tie, the later originating timestamp wins.
If timestamps also tie, the higher originating domain controller GUID wins.
That third tiebreaker is why one of two simultaneous edits can vanish with no error logged anywhere: last-writer-wins is by design, not a fault.
5. Tombstones, Lingering Objects and Strict Replication Consistency
Deletions do not remove an object immediately. The object becomes a tombstone — stripped of most attributes, flagged isDeleted , and retained for the forest's tombstone lifetime , which is 180 days in any forest created at Windows Server 2003 SP1 functional level or later. Replication of the deletion is what removes it everywhere.
A domain controller that is offline longer than the tombstone lifetime and is then reconnected never receives those deletions and still holds objects that no longer exist elsewhere. Those are lingering objects , and they cause the classic symptom of a user or group that appears in one site's directory searches and nowhere else.
Control Behaviour
Strict replication consistency (default: enabled for forests built at Windows Server 2003 or later) The destination domain controller halts inbound replication of that partition and logs Event ID 1988 rather than reanimating an unknown object.
Loose replication consistency The unknown object is reintroduced across the forest — this is how a lingering object spreads.
Remediation repadmin /removelingeringobjects <DestDC> <SourceDC-GUID> <NamingContext> /advisory_mode first to log what would be deleted, then rerun without /advisory_mode .
Warning
The correct response to a domain controller that has been offline longer than the tombstone lifetime is to forcibly demote it and perform metadata cleanup , then repromote. Simply restoring the network connection is what injects lingering objects into a healthy forest.
6. SYSVOL Replication and Whole-Health Diagnostics
The directory database and SYSVOL replicate through different engines. SYSVOL uses DFS Replication (DFS-R) on any modern domain; the legacy File Replication Service (FRS) was deprecated and removed, and a domain still on FRS must complete the dfsrmig migration to the Eliminated state before a Windows Server 2016 or later domain controller can be promoted into it. A domain that replicates the directory correctly but not SYSVOL produces the distinctive symptom of Group Policy changes that never reach some clients while user and group changes do. :: SYSVOL replication state (0=Start, 1=Prepared, 2=Redirected, 3=Eliminated)
- dfsrmig /getglobalstate
- dfsrmig /getmigrationstate
- :: Whole-domain-controller health, including replication, DNS and SYSVOL checks
- dcdiag /v /c /e /test:Replications /test:SysVolCheck /test:NetLogons
- :: Attribute-level forensics: who last wrote this attribute, from which DC, and when
- repadmin /showobjmeta DC-SEA-01 "CN=Jane Doe,OU=Finance,DC=corp,DC=contoso,DC=com"