This object monitors the User Name Mapping LDAP service connection and generates an alert if Server for NFS cannot connect to the LDAP server, if the alert is enabled for this monitor.
User Name Mapping associates user accounts between Windows and UNIX domains so that users logged on to a UNIX domain can access shared resources on Windows without logging on separately to the Windows domain.
This monitor can enter a Critical health state if Server for NFS is not configured to use either Active Directory Domain Services (AD DS) or User Name Mapping as a Windows-UNIX identity mapping source.
If the health state is unknown, it means that monitoring has not yet begun for this object.
Configure Server for NFS to use an Active Directory Domain Services identity mapping source
To configure Server for NFS to retrieve identity mapping data from the LDAP service, use the following procedure:
1. Identify the domain that the LDAP service is running on as follows:
At an elevated command prompt on the affected server, type nfsadmin mapping to display identity mapping settings.
2. To enable Server for NFS to retrieve identity mapping data, type nfsadmin mapping config adlookup=yes addomain=<domain>
Note that addomain is not required if the computer is in the same domain as the Active Directory domain.
To verify that Server for NFS is properly configured for User Name Mapping, use the following procedure:
1. At an elevated command prompt, type nfsadmin mapping.
2. Verify that the AD Lookup field in the list is set to Enabled and that AD Domain is either blank or set to the name of the domain being used.
Note The Server for NFS service will default to the parent Active Directory domain for the computer, but this can be overridden by setting the AD Domain field in the mapping settings.
This monitor automatically resets to a Healthy state after Server for NFS is restarted.