Checks the health of inbound replication for the domain controller.
Knowledge Base article:
Summary
This monitor verifies that the domain controller is successfully replicating with all of its inbound replication partners.
If it fails replication for any of its inbound partners AD data could become inconsistent between domain controllers.
Configuration
Interval (sec)
default: 300 sec (5 min)
Max Replication Latency (min)
All Naming Contexts should replicate within an hour unless specifically configured otherwise in AD. The default is 65 min to allow for minor delays. Depending on your Active Directory topology, this threshold may need to be tuned appropriately.
Max Replication Latency RootDSE (min)
The RootDSE should replicate within a few minutes as this is the NC that changes the most. Since the RootDSE replicates so often this control was added to allow for tighter replication thresholds for the RootDSE. By default the replication threshold is set to 15 minutes.
Causes
Alerts raised indicate that this domain controller has had an issue replicating with one or more of its replication partners.
If the domain controller fails replication for one or more naming contexts in AD, its data (i.e. User/computer accounts and passwords, etc) may become stale and out of date.
This alert could fire while one of the other Domain Controllers in the forest is being rebooted or having maintenance performed on it. This is mitigated by verifying that the DC responds to ping or not but we expect a few false negatives to fire from this monitor.
Resolutions
Log on to the Domain Controller experiencing issues and run diagnostics to help determine why replication failed. The following diagnostic commands are helpful in diagnosing replication failures:
Home
ENU