This object monitors the DFS Replication configuration objects in Active Directory Domain Services (AD DS), and creates a Critical alert if it detects inconsistency. It does so by looking for the presence of DFS Replication Event 6006.
An unhealthy state of this monitor indicates that a DFS Replication object referenced in Active Directory Domain Services (AD DS) doesn’t exist. This can occur for the following reasons:
AD DS replication latencies may cause configuration updates to be slow to replicate to the specified domain controller.
The specified object does not exist or the referenced object's data may not be valid.
Wait for configuration changes to replicate with AD DS
DFS Replication will retry this operation, which might resolve automatically after configuration changes replicate through AD DS.
To poll immediately for configuration changes, open a command prompt window and then type the following command once for each member of the replication group, where <DOMAIN> is the domain the server is located in and <Server> is the server name:
Dfsrdiag PollAD /Member:<DOMAIN>\<Server>
If the inconsistency is still not resolved, recreate the server’s membership in the replication group.
Recreate the server’s membership in the replication group
Use DFS Management or the Dfsradmin command to remove the server’s membership in the replication group and then add the server back to the replication group.
Note: To administer a replication group, you must be a member of the Domain Admins group in the domain in which the replication group is configured, the creator of the replication group, or have been delegated permissions.
This monitor automatically resets to a healthy state when the issue is resolved.