NFS: Server for NFS should be configured to use Netgroups
Updated: February 2, 2011
Applies To: Windows Server 2008 R2
This topic is intended to address a specific issue identified by a Best Practices Analyzer scan. You should apply the information in this topic only to computers that have had the File Services Best Practices Analyzer run against them and are experiencing the issue addressed by this topic. For more information about best practices and scans, see Best Practices Analyzer.
Operating System |
Windows Server 2008 R2 |
Product/Feature |
File Services |
Severity |
Warning |
Category |
Configuration |
Issue
Server for Network File System (NFS) is configured to use ClientGroups instead of Netgroups.
Impact
Client-based fencing (access control) for clients is performed by using a deprecated, proprietary technology instead of an industry standard that provides centralized client-based fencing for Server for NFS.
Resolution
Use the appropriate centralized configuration, such as Active Directory Domain Services (AD DS) or Network Information Service (NIS), to enable Netgroups.
Membership in the local Administrators group, or equivalent, on the server that you plan to configure, is the minimum required to complete this procedure.
To configure Server for NFS to use netgroups
In Administrative Tools, click Share and Storage Management.
In the Actions pane, click Edit NFS Configuration.
In Services for NFS Configuration Guide, in the left pane click Configure a Netgroup Source, and then click Netgroup Source Wizard.
In Netgroup Source Type, click Use a netgroup source, and then proceed through the wizard.
Additional references
Specify How Server for NFS Obtains Windows User and Group Information (https://technet.microsoft.com/en-us/library/cc754514.aspx)