DFS-R: Configuration Consistency Monitor

  • ID:  Microsoft.Windows.FileServer.DFSR.UnrecognizedPartnerMonitor
  • Description:  This object monitors whether the configuration information for a connection or replication group in the local DFS Replication database matches the information received from Active Directory Domain Services (AD DS). This monitor creates a Warning alert if the connection or replication group configuration is not identical in the local database and AD DS.
  • Target:  Replication Group Member
  • Enabled:  Yes

Operational States

Name State Description
FirstEventRaised Warning  
SecondEventRaised Success  

Alert Details

Monitor State Message Priority Severity Auto Resolution
FirstEventRaised (Warning) DFS-R: Connection or Replication Group Configuration Doesn’t Match with AD DS Medium Warning Yes

Run As Profiles

Name
Default

Monitor Knowledgebase

Summary

This object monitors whether the configuration information for a connection or replication group in the local DFS Replication database matches the information received from Active Directory Domain Services (AD DS). This monitor creates a Warning alert if the connection or replication group configuration is not identical in the local database and AD DS. It does so by looking for the presence of DFS Replication Event 5012.

Causes

An unhealthy state of this monitor indicates that DFS Replication could not establish a connection with the member. This error can occur for the following reasons:

  • An administrator recently made a configuration change or created a new replication group. If two replication group members obtain their configuration data from different domain controllers, they may have mismatched configuration data due to AD DS replication latencies.

  • An administrator altered AD DS permissions.

Resolutions

Wait for configuration changes to replicate with AD DS

DFS Replication will retry this operation, which usually resolves 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 this problem persists, verify that AD DS replication is working and that the service is able to reach a domain controller.

Test AD DS connectivity

To test DFS Replication’s ability to communicate with AD DS, open a command prompt window and then type the following command: Dfsrdiag pollad /verbose. The command should report Operation Succeeded. If not, there is a problem communicating with AD DS.

If the problem persists for 8 hours, the DFS Replication service will disable the connection and log DFS Replication Event 5016.

Verification

This monitor automatically resets to a healthy state after the problem is resolved (usually indicated by DFS Replication Event 5004) or the DFS Replication service is restarted.

To manually verify the replication topology, see Repair a Disconnected Topology (http://go.microsoft.com/fwlink/?LinkId=187103).

External References
This monitor does not contain any external references.

See Also for Windows Server File & iSCSI Services Management Pack


Downloads for Windows Server File & iSCSI Services Management Pack

AZURE OPTIMIZATION ASSESSMENT GET STARTED
MIGRATION TO AZURE GET STARTED
SYSTEM CENTER MIGRATION TO AZURE GET STARTED
MIGRATION TO AZURE FOR SQL AND WINDOWS 2008 GET STARTED