Install Windows Services for UNIX

Insert the Windows Services for UNIX compact disc into the CD-ROM drive.
In the Windows Services for UNIX Setup Wizard dialog box, click Next.
In the User name box, type your name. If the name of your organization does not appear in the Organization box, type the name of your organization there.
In the CD Key boxes, type the product key found on the back of the CD-ROM case, and then click Next.
Read the End User License Agreement carefully. If you accept the terms of the agreement, click I accept the terms in the License Agreement, and then click Next to continue installation. If you click I do not accept the License Agreement (Exit Setup), the installation procedure terminates.
To complete installation of default Windows Services for UNIX components in the default directory, click Standard installation (for information about standard installation components, see Installation options in Related Topics). If you want to specify a different set of components or a different installation location, click Custom installation.

Standard installation

In the Security Settings box, read the instructions carefully, select the options you want, and then click Next.
In the User Name Mapping box, type the name of your organization's User Name Mapping server, and then click Next to complete the installation. If you do not know the name of the User Name Mapping server, click Next without typing a name; you can specify the name of the server later using Services for UNIX Administration.
Important
- These components will not work properly until you specify the name of the User Name Mapping server.
Before restarting the computer, for each service you want to run that was disabled by Windows Services for UNIX Setup, use Services in the Administrative Tools group in Control Panel to change the startup type of the service to automatic. To enable an Interix service (daemon), edit the /etc/inted.conf file.

Custom installation

Click the icon next to each component that you want to install and click the appropriate option. If you do not want to install a component, click the icon next to the component and click Entire feature will not be available. When you are finished specifying the components to install, click Next.
If you are installing the GNU Software Development Kit (SDK), read the information about the GNU Library General Public License carefully. If you want to install the GNU SDK, click Next to continue installation. If you click Back, you will be given another opportunity to select the components to install. See Files covered by the GNU Public License (GPL) for a complete listing.
In the Security Settings box, read the instructions carefully, select the options you want, and then click Next.
If you are installing ActiveState Perl, read the ActiveState Perl End User License Agreement carefully. If you accept the terms of the agreement, click I accept the agreement, and then click Next. If you click I do not accept the agreement (Reselect components to be installed) and then click Next, you will be given another opportunity to select the components to install.
If you are installing base utilities, the Windows-based Remote Shell service, Client for NFS, Gateway for NFS, or Server for NFS, you will be prompted for the name of your organization's User Name Mapping server. If you do not know the name of the User Name Mapping server, click Next without entering a name; you can specify the name of the server later using Services for UNIX Administration.
Important
- These components will not work properly until you specify the name of the User Name Mapping server.
If you are also installing User Name Mapping, type the name of the server on which you are installing Windows Services for UNIX.
In the Installation location box, type the fully qualified path of the directory where you want to install Windows Services for UNIX, and then click Next to complete installation. The path you specify must contain only alphanumeric characters and the underscore (_) character.
Before restarting the computer (if required), for each service you want to run that was disabled by Windows Services for UNIX Setup, use Services in the Administrative Tools group in Control Panel to change the startup type of the service to automatic and then start the service if Setup does not require you to restart the computer. To enable an Interix service (daemon), edit the /etc/inted.conf file before restarting the computer.

Notes

If you are installing Windows Services for UNIX version 3.0 as an upgrade to Windows Services for UNIX 2.0 or as an upgrade to Microsoft Interix version 2.2, after you accept the End User License Agreement, an upgrade summary will be displayed showing the components you currently have installed. When you click Next, you will be offered a choice between Express Upgrade, which will upgrade the currently installed components, or Custom Upgrade, which allows you to install additional components. The steps for completing the installation with these options are the same as for the Standard installation and the Custom installation, respectively. You cannot use the Custom upgrade to uninstall Windows Services for UNIX 2.0 or Interix 2.2 features.
If you are installing Windows Services for UNIX version 3.0 as an upgrade to Microsoft Interix version 2.2, the following files are preserved in the upgrade:
- motd
- igetty.conf
- csh.lcl
- profile.lcl
- inetd.conf
- syslog.conf
Depending on your system's configuration, you can install any or all of the following components:
- Utilities
  - Base utilities, including common Windows utilities; UNIX utilities; X-Windows utilities, X11R5 window managers, terminal emulators, and graphic programs; Cron service; and Telnet Client. Installing this component also installs the Interix subsystem For more information, see Interix overview.
  - UNIX perl. Installing this component also installs the base utilities.
- Interix GNU components. For more information, see Files covered by the GNU Public License (GPL).
  - Interix GNU utilities. Interix utilities distributed under the terms of the GNU General Public License (GPL) that supplement the base utilities. Installing this component also installs the base utilities.
  - Interix GNU SDK. Interix SDK tools distributed under the terms of the GNU General Public License (GPL) that supplement the Interix SDK. Installing this component also installs the GNU utilities and the Interix SDK.
- Network file system (NFS)
  - Client for NFS. You cannot install Client for NFS and Gateway for NFS on the same computer.
  - Server for NFS. You must also install Server for NFS Authentication.
  - Gateway for NFS. Gateway for NFS is not available to be installed on a computer running Windows NT Workstation, Windows 2000 Professional, or Windows XP Professional. You cannot install Client for NFS and Gateway for NFS on the same computer.
- Server for NIS. This component is available only if you are installing Windows Services for UNIX on a Windows Active Directory domain controller.
- Password Synchronization
- Remote connectivity
  - Telnet Server
  - Remote Shell service
- Authentication tools
  - Server for PCNFS
  - Server for NFS Authentication. For more information, see Understanding Server for NFS security.
  - User Name Mapping
- The Interix Software Development Kit. See Porting applications to the Interix subsystem. Installing this component also installs base utilities.
- ActiveState ActivePerl 5.6.
If you are installing the base utilities, you will be required to choose whether you want to enable setuid behavior for Interix programs. The choice you make will affect both system security and how certain Interix programs behave.
According to the POSIX standard, a file has permissions that include bits to set a UID (setuid) and set a GID (setgid) when the file is executed. If either or both bits are set on a file, and a process executes that file, the process gains the UID or GID of the file. When used carefully, this mechanism allows a nonprivileged user to execute programs that run with the higher privileges of the file's owner or group. When used incorrectly, however, this can present security risks by allowing nonprivileged users to perform actions that should only be performed by an administrator. For this reason, Windows Services for UNIX Setup does not enable support for this mechanism by default.

You should enable support for setuid behavior only if you are sure you will be running programs that require support for this behavior. Even if you do not enable support for setuid behavior when installing Windows Services for UNIX, you can enable it later. For more information, see The superuser account and appropriate privileges.
If you connect to a remote computer using Terminal Services to install Windows Services for UNIX on the computer, you cannot use a network share directory mapped to a drive letter to access the installation files for Windows Services for UNIX. You must access the installation files using a universal naming convention (UNC) path, such as \\server\share.
After you have installed Windows Services for UNIX, you still have the option to install additional components or remove installed components when you so choose.
If the installation program does not start when you insert the Windows Services for UNIX compact disc into the CD-ROM drive, open the CD-ROM drive in Windows Explorer, and then double-click the program Setup.exe.
Windows Services for UNIX components cannot be run from a network server. All files must be installed on the local computer.

At a command prompt, type:
msiexec /i [path\]sfusetup.msi [ADDLOCAL="component[,component...]"] PIDKEY="key" SFUDIR="location" {/qb|/q}

The following describes the arguments and options for this command.

Argument/Option	Description
path	The fully qualified path of the Windows Services for UNIX Sfusetup.msi file. If you omit the path, the Sfusetup.msi file must be in the current directory.
component	Specifies the feature you want to install. If you are installing Windows Services for UNIX for the first time and do not specify the ADDLOCAL keyword with at least one component name, a standard installation is performed (see Installation options). If you do not specify the ADDLOCAL keyword with at least one component name, and you are upgrading a previous installation of Windows Services for UNIX or Microsoft Interix, only currently installed components will be upgraded; no other components will be installed. Important If you are upgrading an existing installation of Windows Services for UNIX or Microsoft Interix and specify ADDLOCAL with at least one component name, you must specify all existing components as well as any new components you want to install; failure to do so will cause the upgrade to fail. Component names are case sensitive, so you must type them exactly as shown. Multiple component names must be separated by commas only; spaces are not allowed. The following components can be installed: BaseUtils Installs base utilities, including Interix utilities, Windows-based Cron service and Telnet Client, and Windows-based administrator utilities. Installing BaseUtils also installs the Interix subsystem. UNIXPerl Installs UNIX-based perl. Installing UNIXPerl also installs the Interix subsystem and base utilities. GNUUtils Installs Interix GNU utilities. Installing GNUUtils also installs the base utilities. See Files covered by the GNU Public License (GPL) for a complete listing. InterixSDK Installs the Interix Software Development Kit (SDK). Installing InterixSDK also installs the Interix subsystem and base utilities. GNUSDK Installs the Interix GNU SDK. Installing GNUSDK also installs the Interix SDK. See Files covered by the GNU Public License (GPL) for a complete listing. NFSClient Installs Client for NFS. NFSClient and NFSGateway cannot be installed on the same computer. NFSGateway Installs Gateway for NFS. You cannot install NFSGateway on a computer running Windows NT Workstation, Windows 2000 Professional, or Windows XP Professional. NFSClient and NFSGateway cannot be installed on the same computer. NFSServer Installs Server for NFS. If NFSServer is being installed on a computer that is not a domain controller, NFSServerAuth must also be installed. NIS Installs Server for NIS. NIS can only be installed on a Windows Active Directory domain controller. PasswdSync Installs Password Synchronization. RshSvc Installs the Windows-based Remote Shell service. TelnetServer Installs Telnet Server. Mapsvc Installs User Name Mapping. NFSServerAuth Installs Server for NFS Authentication. Pcnfsd Installs Server for PCNFS. Perl Installs Windows-based ActiveState Perl.
key	The 25-character product identification code. Do not type hyphens or spaces in the key.
location	The fully qualified path of the directory where Windows Services for UNIX is to be installed. The path you specify must contain only alphanumeric characters and the underscore (_) character.
/qb	Installs Windows Services for UNIX with a basic user interface. You must specify either the /q or /qb option; otherwise, the results will be unpredictable.
/q	Installs Windows Services for UNIX with no user interface or display. This option allows you to perform an unattended installation. You must specify either the /q or /qb option; otherwise, the results will be unpredictable.

Notes

For security purposes, some Windows services that you install are disabled until you change their startup type to automatic and then either start the services or restart the computer. Also, all Interix services (daemons) are disabled by default. To manage Windows services, use Services in the Administrative Tools group in Control Panel. To manage Interix services, edit the inetd.conf(5) file.
If you install the base utilities using the command line, setuid behavior for Interix programs will be disabled by default. This will affect how certain Interix programs behave.
According to the POSIX standard, a file has permissions that include bits to set a UID (setuid) and set a GID (setgid) when the file is executed. If either or both bits are set on a file, and a process executes that file, the process gains the UID or GID of the file. When used carefully, this mechanism allows a nonprivileged user to execute programs that run with the higher privileges of the file's owner or group. When used incorrectly, however, this can present security risks by allowing nonprivileged users to perform actions that should only be performed by an administrator. For this reason, Windows Services for UNIX Setup does not enable support for this mechanism by default.

You should enable support for setuid behavior only if you are sure you will be running programs that require support for this behavior. Even if you do not enable support for setuid behavior when installing Windows Services for UNIX, you can enable it later. For more information, see The superuser account and appropriate privileges.
If you connect to a remote computer using Terminal Services to install Windows Services for UNIX on the computer, you cannot use a network share directory mapped to a drive letter to access the installation files for Windows Services for UNIX. You must access the installation files using a universal naming convention (UNC) path, such as \\server\share.
After you have installed Windows Services for UNIX, you can subsequently install additional components or remove installed components when you so choose.
If you are installing Windows Services for UNIX for the first time on a computer running Windows NT, you must install using the Windows interface. This is required to upgrade the Windows Installer, which will then enable you to use the command line to add or remove components.
If you are installing Windows Services for UNIX version 3.0 as an upgrade to Microsoft Interix version 2.2, the following files are preserved in the upgrade:
- motd
- igetty.conf
- csh.lcl
- profile.lcl
- inetd.conf
- syslog.conf