This object monitors Windows Management Instrumentation (WMI) registration and creates a Critical alert if it detects that DFS Replication couldn’t register itself with WMI. It does so by looking for the presence of DFS Replication Event 6104.
An unhealthy state of this monitor indicates that replication is stopped because DFS Replication failed to register itself with WMI. This can occur if the Windows Management Instrumentation service is stopped.
Restart the Windows Management Instrumentation service
To restart the service remotely by using the sc command, open a command prompt window and then do the following:
1.To stop the service, type the following command, where <servername> is the Universal Naming Convention (UNC) path to the remote server:
sc <servername> stop winmgmt
2.To confirm that the service is in the STOPPED state, type the following command:
sc <servername> query winmgmt
3.To restart the service, type the following command:
sc <servername> start winmgmt
Note: To restart a service, you must be a member of the local Administrators group on the affected server. You can also restart services using the Services snap-in, the Windows PowerShell Start-Service and Stop-Service cmdlets, or command-line tools such as net stop and net start.
Reregister the DFS Replication WMI Provider
To do so, follow this procedure:
1. Log on to the affected server and then open an elevated command prompt window.
2. Type the following command: Mofcomp.exe %systemroot%\system32\wbem\dfsrprovs.mof.
3. Type the following command: net stop dfsr.
4. Type the following command: net start dfsr.
This monitor automatically resets to a healthy state when the issue is resolved.
To confirm that the service is in the STOPPED state, type the following command: