Administrator Guide
Table Of Contents
- Contents
- Notes, Cautions, and Warnings
- _
- Overview
- Applications To Manage Your NAS System
- Using Your NAS System
- Creating A Server Message Block Share
- Modifying Message Block Shares
- NFS Share
- Windows 2003 Domain Controller As Identity Mapping Source
- Windows 2008 Domain Controller As Identity Mapping Source
- User Name Mapping Server As Identity Mapping Source
- Active Directory Lightweight Directory Services As Identity Mapping Source
- Configuring AD LDS For Services For NFS
- Installing The 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 The Active Directory Schema
- Adding User And Group Account Maps From A UNIX-Based Computer To A Windows-Based Computer
- Connecting To The Distinguished Name Or Naming Context
- Adding User Account Maps
- Adding Group Account Maps
- Authorizing Appropriate 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 And File Screens Using Share And Storage Management Wizard
- Creating Quotas And File Screens Using File Server Resource Manager
- Creating A New Volume
- Managing A Volume
- Extending A Volume
- Shrinking A Volume
- Deleting A Volume
- Enabling Or Disabling SIS On A Volume
- Enabling And Configuring Shadow Copies Of Shared Folders
- Performing Backup Of Your Server Using Microsoft Windows Server Snap-In
- Choosing Volumes To Backup
- Choosing A Storage Location
Authorizing Appropriate Access To The ADS LDS Namespace Object
To connect to the Configuration partition:
1. Click Start, right-click Command Prompt, and click Run as administrator to open an elevated command prompt.
2. Navigate to the C:\WINDOWS\ADAM directory, and run the dsacls command to grant the Everyone group read
access to the mapping data store as follows:
dsacls "\\server1:389\CN=nfsadldsinstance,dc=server1" /G everyone:GR /I:T
3. Optionally, if you are setting up a shared AD LDS store to allow multiple NFS servers to query the account mapping
database, add the mapping data store to the ACL to allow Read permissions for the Anonymous Logon account as
follows:
dsacls "\\server1:389\CN=nfsadldsinstance,dc=server1" /G "anonymous
logon":GR /I:T
NOTE: You can skip this step if there is no shared access between computers to the mapping data store.
Configuring The Mapping Source
To configure the mapping source:
1. Click Start, right-click Command Prompt, and click Run as administrator to open an elevated command prompt.
2. Run the following command, where
<Computer>
is the name of the computer where the AD LDS instance was
created, and where
<Port>
is the port that the AD LDS instance uses:
nfsadmin mapping config adlookup=yes addomain=<Computer>:<Port>
NOTE: For this example, use the following:
nfsadmin mapping config adlookup=yes addomain=server1:389
3. Test the setup by accessing the NFS resources and verifying that the user and group account mappings work as
expected.
Debug Notes For NFS Account Mapping Problems
Server for NFS can be made to log account mapping failures to the Windows Event Log service by setting the following
registry key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\nfsserver\Parameters
\VerboseMappingFailureLogging INVALID USE OF SYMBOLS REG_DWORD = 1
After you create the key, you must restart the Server for NFS.
Restarting The Server For NFS
To restart the server for NFS:
1. Click Start, right-click Command Prompt, and click Run as administrator to open an elevated command prompt.
2. Run the following command:
nfsadmin server stop && nfsadmin server start
22