Map Windows user and group IDs for Xsan volumes
You can use the Windows ID Mapping setting for a volume to specify how Windows clients map user and group information to Xsan-compatible user IDs (UIDs) and group IDs (GIDs), which they need to access Xsan volumes.
Windows clients can use these methods to provide UIDs and GIDs:
Generate IDs from GUID: Windows clients dynamically generate UIDs and GIDs based on globally unique identifier (GUID) information in an Active Directory domain. Choose this method if Mac computers on the SAN are connected (bound) to Active Directory with the default binding options, which automatically generate IDs.
Use IDs from LDAP (RFC 2307): Windows clients get UID and GID values from the uidNumber and gidNumber attributes in Active Directory records. Choose this method if Mac computers on the SAN are connected to Active Directory with binding options set to map IDs to uidNumber and gidNumber.
Important: To avoid ID conflicts, be sure all computers on the SAN use the same Active Directory domain and the same method of ID mapping.
In the Server app sidebar, select Xsan from the list of advanced services.
Select the volume you want to edit.
Click , then choose Edit Volume.
Choose a mapping method from the Windows ID Mapping pop-up menu.
If you choose “Use IDs from LDAP (RFC 2307),” you can change the ID numbers used when a directory record doesn’t include a uidNumber or gidNumber attribute.
Server unmounts the volume from clients and controllers and stops the volume before changing the Windows ID mapping method, then starts the volume and mounts it on each computer on which it was mounted.