- Notes, cautions, and warnings
- Overview
- Configuring your NAS system
- Initial configuration of your NAS system
- Server Manager roles, role services, and features
- Installing or uninstalling Server Manager roles, role services, and features
- Accessing administrative tools for your NAS systems
- Accessing computer management
- Work folders
- Creating a new DFS namespace
- Creating new DFS replication group
- Adding DFS namespaces to display
- Adding replication groups to display
- File Server Resource Manager
- Multipath I/O
- Managing your NAS system
- Using your NAS system
- Creating server message block share
- Modifying message block shares
- NFS share
- Windows domain controller as identity mapping source
- User name mapping server as identity mapping source
- AD LDS as identity mapping source
- Configuring AD LDS for services for NFS
- Installing AD LDS server role
- Creating a new AD LDS instance
- Extending the AD LDS schema to support NFS user mapping
- Setting a default instance name for AD LDS instances
- Updating active directory schema
- Adding user and group account maps from a UNIX-based system to a Windows-based system
- Authorizing access to the ADS LDS namespace object
- Configuring the mapping source
- Debug notes for NFS account mapping problems
- Restarting the server for NFS
- Creating the NFS share
- Creating quotas using File Server Resource Manager
- Creating file screens using file Server Resource Manager
- Creating a new volume
- Managing a volume
- Extending a volume
- Shrinking a volume
- Deleting a volume
- Data deduplication
- Enabling and configuring shadow copies of shared folders
- Performing backup of your server
- NIC teaming
- Getting help
PowerVault NX Series Network Attached Storage Systems Windows Storage Server 2016 Administrator's Guide
NFS share
Network File System (NFS) protocol provides access control (for UNIX-based file systems) and is implemented by granting permissions to specific client systems and groups, by using network names.
Before creating NFS shares, the administrator must configure Identity Mapping. The identity mapping source can be any one of the following:
- Microsoft Active Directory domain name server (Microsoft Windows Server 2003 domain controller, Microsoft Windows Server 2008 domain controller, or Microsoft Windows Server 2012 domain controller and Microsoft Windows Server 2016 domain controller)
- User Name Mapping (UNM) server
- Active Directory Lightweight Directory Services (AD LDS)
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\