This object monitors Server for NFS and generates an alert if the service failed or has been stopped, if the alert is enabled for this monitor.
This monitor can enter a Warning or Critical health state if Server for NFS has been stopped by administrative action or the Server for NFS service failed. To determine the underlying cause, inspect the Windows System event log for messages from Source Microsoft-Windows-ServicesForNFS-Server with one of the following event IDs:
Event 1001 - The Network File System (NFS) driver has suspended operations.
Event 1003 - The Network File System (NFS) driver successfully unloaded. This may have been the result of administrative action.
If the health state is unknown, it means that monitoring has not yet begun for this object.
Restart Server for NFS
To restart Server for NFS, use the following procedure:
1. At an elevated command prompt on the affected server, type nfsadmin server stop.
2. Type nfsadmin server start.
To verify the startup status of the Server for NFS driver:
1. At an elevated command prompt on the affected server, type devmgmt.msc.
2. On the View menu, click Show hidden devices.
3. Expand the Non-Plug and Play Drivers node.
4. Right-click Server for NFS Driver, click Properties, click the Driver tab and check Status.
To verify the state of Server for NFS, use the following procedure:
1. At a command prompt, type sc query >Microsoft-Windows-ServicesForNFS-Server.
2. Verify that the STATE is RUNNING.
This monitor automatically resets to a Healthy state after Server for NFS is restarted.