HP ProLiant ML310 G3 Storage Server - Manual (Page 79)

6. Click Custom Installation, and then click Next.
7. In the Components pane, click the down arrow next to Windows Services for UNIX, and then
click Entire component will not be available.
8. Click the plus sign (+) next to Authentication Tools.
9. In the Components pane, click the plus sign (+) next to Authentication Tools.
10. Click Server for NFS Authentication, click Will be installed on local hard drive, and then click Next.
11. Follow the remaining instructions in the Wizard.
NOTE:
NFS users can be authenticated using either Windows domain accounts or local accounts on the
Windows server. Server for NFS Authentication must be installed on all domain controllers in the domain
if NFS users will be authenticated using domain accounts. Server for NFS Authentication is always
installed on the computer running Server for NFS.
Elevate S4U2 functionality on Windows Server 2003 domain controllers
NOTE:
The S4U2 functionality does not work until the domain functional level is elevated to Windows Server
2003.
To elevate the functional level to Windows Server 2003:
1. On the Windows 2003 domain controller, open Active Directory Domains and Trusts.
2. In the console tree, right-click the domain for which you want to raise functionality, and then click
Raise Domain Functional Level.
3. In Select an available domain functional level, click Windows Server 2003.
4. Click Raise.
Server for NFS administration
The Server for NFS administration online help contains information for the following topics:
• Understanding the Server for NFS component
• Starting and stopping Server for NFS
• Configuring Server for NFS
• Securing Server for NFS
• Optimizing Server for NFS performance
• Using file systems with NFS
• Managing NFS shares
• Managing NFS client groups
• Using Microsoft Services for NFS with server clusters
• Server for NFS Authentication
Accessing NFS resources for Windows users and groups
Server for NFS allows Windows clients to access NFS resources on the storage server without separately
logging on to Server for NFS. The first time users attempt to access an NFS resource, the Server for NFS
looks up the user’s UNIX UID and GID information in either Windows Active Directory or the User
Name Mapping function on the storage server. If the UNIX UID and GID information is mapped to a
Windows user and group accounts, the Windows names are returned to Server for NFS, which then uses
HP ProLiant ML310 Storage Server 79