This article was previously published under Q324055
You may find it easier to migrate files from an existing UNIX server to a Windows-based server if you use NFS instead of File Transfer Protocol (FTP) to move the files. Additionally, if you use Client for NFS, ongoing access to the UNIX host is available. This functionality makes it easier to stage the migration over time.
Note You cannot install Client for NFS and Gateway for NFS on the same computer; however, Gateway for NFS enables the computer to act as an NFS client while it provides access to NFS resources for downstream Windows-based clients.
Installing Client for NFS from the command line
Windows Services for UNIX version 3.0 uses Microsoft Installer for installation. As a result, you can install individual modules of the product from the command line. If previous components of Windows Services for UNIX have been installed, you must include these components in the addlocal parameter of the installation command line, separated by a comma (,). If you do not do so, these products are removed during the installation of Client for NFS.
To install Client for NFS from the command line:
Log on to the Windows computer by using an administrative level account.
Click Start, click Run, type cmd, and then click OK.
Insert the Windows Services for UNIX version 3.0 CD in the CD drive (this example uses drive D).
From the command prompt, run the following command to install Client for NFS:
To include the product key in the command line, add PidKey=key, where key is the 25 character product key.
If you are using either Windows 2000 and Windows XP, you do not have to restart the computer.
If you are installing from a telnet prompt (where the graphical user interface [GUI] is not available) or by using a script, use the following command line to perform an installation which does not require user interaction:
Install Windows Services for UNIX in a folder that does not have any spaces in the folder path to prevent problems with some components of Windows Services for UNIX. The default installation point is \SFU.
The addlocal parameter to the msiexec command that is described earlier is case-sensitive and space-sensitive. The installation is not successful if you do not use the command exactly as it is written in this article.
If your UNIX server is not running PCNFSD and you are not using NIS for authentication, you must install Windows Services for UNIX PCNFS Server. For more information about how to install the Services for UNIX PCNFS Server, click the following article number to view the article in the Microsoft Knowledge Base:
324084 How to install Server for PCNFS to support Windows clients on a UNIX network
Microsoft recommends that you install at least one User Name Mapping service on your network to map UNIX and Windows user names to each other.For more information about how to install and configure the User Name Mapping service, click the following article number to view the article in the Microsoft Knowledge Base:
324073 How to configure the User Name Mapping service
When you install Microsoft Windows Services for UNIX 3.5 on a Microsoft Windows Server 2003 Service Pack 1 (SP1)-based or Microsoft Windows XP-based computer, you cannot specify an alternate installation path, such as D:\programs\SFU, by using the [targetdir="install path"] command. By default, Windows Services for UNIX 3.5 is installed to the %systemdrive%\SFU folder. To install Windows Services for UNIX 3.5 to a different location, you must use the [sfudir="install path"] command. For more information about how to use a script to install the Windows Services for UNIX 3.5 password synchronization component on a domain controller, click the following article number to view the article in the Microsoft Knowledge Base:
891768 How to configure the User Name Mapping service
For more information about preparing to migrate data in a UNIX-to-Windows migration, click the following article number to view the article in the Microsoft Knowledge Base:
324538 How to migrate Web site data in a UNIX-to-Windows migration