- 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
AD LDS as identity mapping source
Active Directory Lightweight Directory Services (AD LDS) is used for identity mapping on systems that run Windows Storage Server in an environment where no Active Directory exists to support user mapping.
Before you start AD LDS mapping:
- Determine the users and groups on the UNIX-based system that must be mapped to users and groups on the Windows-based system.
- Determine the UID and GID for each UNIX user, and the GID for each UNIX group.
- Create a user or group on the Windows-based computer for each UNIX user or group to be mapped.
NOTE: Each UID
and GID requires a unique mapping. You cannot use one-to-many or many-to-one
mappings.
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: <>()\