HP StorageWorks All-in-One Storage System user guide (440583-005, February 2008)

1. Go to Add/Remove Programs.
2. Select Add/Remove Windows Components > Other Network File and Print Services > Microsoft
Services for NFS > Details.
3. Install Client for NFS.
Administering MSNFS
To access Microsoft Services for Network File System from the Start menu:
1. Select Start > Programs > Administrative Tools.
2. Click Microsoft Services for Network File System.
To access Microsoft Services for Network File System from the HP All-in-One Management Console:
1. Access the HP All-in-One Management Console by clicking on the shortcut icon on the desktop.
2. In the left pane of the console, select the Share Folder Management listing.
3. In the center pane, under Share Utilities, select Microsoft Services for NFS .
Server for NFS
With Server for NFS, a computer running the Microsoft Windows Server 2003 R2 operating system
can act as a Network File System (NFS) server. Users can then share files in a mixed environment of
computers, operating systems, and networks. Users on computers running NFS client software can
gain access to directories (called shares) on the NFS server by connecting (mounting) those directories
to their computers. From the viewpoint of the user on a client computer, the mounted files are
indistinguishable from local files.
UNIX computers follow advisory locking for all lock requests. This means that the operating system
does not enforce lock semantics on a file, and applications that check for the existence of locks can
use these locks effectively. However, Server for NFS implements mandatory locks even for those
locking requests that are received through NFS. This ensures that locks acquired through NFS are
visible through the server message block (SMB) protocol and to applications accessing the files locally.
Mandatory locks are enforced by the operating system.
Server for NFS Authentication DLL vs. Service for User for Active Directory domain controllers
On a Windows Storage Server 2003 R2 storage system, Server for NFS depends on a domain
controller feature called Service for User (S4U) to authenticate UNIX users as their corresponding
Windows users. Windows Server operating systems prior to Windows Server 2003 and Windows
Storage Server 2003 do not support S4U. Also, in mixed domain environments, legacy Services for
UNIX (SFU), Services for NFS and Windows Storage Server 2003 NFS deployments do not use the
S4U feature and still depend on the Server for NFS Authentication DLL being installed on domain
controllers.
Therefore, the administrator needs to install the Server for NFS Authentication DLL on Windows 2000
domain controllers when:
• The NFS file serving environment uses previous NFS releases (NAS, SFU, and so on).
• The Windows domain environment uses pre-2003 domain controllers.
All-in-One Storage System 163