Introduction

Microsoft Windows Services for UNIX is a Microsoft product used to extend the functionality of the Windows operating environment. It provides a complete replacement for the standard Windows POSIX environment as well as providing a large number of UNIX based utilities. In particular the perl scripting language and a POSIX compliant shell (Korn Shell) are provided. Services also exist which allow for password synchronisation between UNIX and Windows based servers. Microsoft Windows Services for UNIX is a fully supported Microsoft product.

Requirements

• Microsoft Windows 2000 (Professional or Server), Service Pack 2 or greater
  Microsoft Windows XP (Professional)
  Microsoft Windows 2003 Server
• Microsoft Windows Services for UNIX, version 3.5

Installation Notes SFU

1. Log in as the local domain Administrator.
2. Insert the Microsoft Windows Services for UNIX CD into the CD drive. The Windows Installer will start automatically and the Microsoft Windows Services for UNIX Setup Wizard will appear.
     -OR-
   Run the self extract archive and extract the files a temporary folder. Once all files are extracted run the setup.exe in the temporary folder.
3. On the Welcome screen click Next>.
4. Enter your User name and Organisation then click Next>.
5. The End-User Licence Agreement will be displayed. After reading the licence click I accept the agreement. Click Next >.
6. Select Custom Installation and click Next>.
7. Select the components to be installed.
   The following should be the only facilities enabled:
   • Utilities
     • Base Utilities
     • UNIX Perl
   • Interix GNU Components
     • Interix GNU Utilities
   Disable all other facilities by selecting the Entire feature will not be available option.
   Click Next> once the required components are selected.
8. Turn on:
   Enable setuid behaviour for Interix programs option. Vitalware will not function without this option enabled.
   Change the default behaviour to case sensitive (option will appear on Windows XP/2003 only). Turn this option on. 
   Then click Next>.
9. On the User Name Mapping (Configure the User Name Mapping Server) screen select Remote User Name Mapping Server and leave the name box empty. Click Next>.
10. On the User Name Mapping (Remote User Name Mapping) screen click Next>.
11. In the Installation location: screen enter the full path where Microsoft Windows Services for UNIX will be installed. The path you enter can only contain alpha, numeric or underscore characters. The default  path of C:\SFU\ is strongly recommended. Click Next>.
12. Microsoft Windows Services for UNIX will commence installing. Once the installation is complete click Finish.
13. You will be prompted to restart the server. Click Yes.

Create perl link

The perl executable is installed in the /usr/local/bin directory. All Vitalware scripts expect to find perl in /usr/bin. Hence a link is required so that /usr/bin/perl > /usr/local/bin/perl.

1. Log in as Administrator.
2. Start a Korn Shell with Start>Programs>Windows Services for UNIX>Korn Shell.
3. Enter  ln  -s  /usr/local/bin/perl /usr/bin/perl
4. Enter exit to terminate the Korn shell.

Install updated cpio program

An update is required to the cpio program provided in the base Windows Services for Unix 3.5 package.

1. Log in as Administrator.
2. Download the files pkg-2.4.3-bin35.sh (package install archive file) and cpio-2.5.1-bin.tgz (cpio package archive) into a temporary folder (use C:\SFU\tmp) on the host on which you are installing Services for Unix. 
3. Start a Korn Shell with Start>Programs>Windows Services for UNIX>Korn Shell.
4. Enter cd  /tmp
5. Enter sh  pkg-2.4.3-bin35.sh
6. Enter pkg_add  cpio-2.5.1-bin.tgz
7. Enter rm  pkg-2.4.3-bin35.sh  cpio-2.5.1-bin.tgz
8. Enter exit to terminate the Korn shell.

Setup Telnet

It is not necessary to have telnet enabled on your server for Vitalware to operate. However in order to provide remote support KE Software recommends that the service be available. If telnet is not enabled some other remote administration tool (e.g. NetMeeting) may be used.

Disable Windows telnet daemon

1. Log in as Administrator.
2. Windows XP/2003: Open the Control Panel with Start>Control Panel>Administrative Tools
   -OR-
   Windows 2000: Open the Control Panel with Start>Settings>Control Panel>Administrative Tools
3. Open the Services Icon. The Services window will open.
4. Double click on the Telnet service from the services list.  The Telnet Properties dialog box will open.
5. Check the Startup type. Change to Disabled if not already set for that option.
6. Check the Service Status. If the status is not Stopped click Stop.
7. Click OK to close the Telnet Properties dialog box.
8. Close the Services window.

Enable SFU telnet daemon

1. Log in as Administrator.
2. Start a Korn Shell with Start>Programs>Windows Services for UNIX>Korn Shell.
3. Enter vi  /etc/inetd.conf
4. Locate the telnet daemon line:
   
   #telnet stream tcp nowait NULL /usr/sbin/in.telnetd in.telnetd -i
   
   and remove the leading #.
5. Save the file.
6. Enter ps  -e  |  grep  inetd
   and note the process id (pid) of the inetd process (it is the first number listed).
7. Enter kill  -HUP  pid
   where pid is the number noted in the previous step.
8. Enter exit to terminate the Korn shell.

Windows 2003 Server and Service Pack 1

If you have installed Windows Services for UNIX version 3.5 on a Windows 2003 Server which has subsequently been upgraded to Service Pack 1, you may encounter problems with the POSIX subsystem. In particular simple scripts will crash as will many other POSIX based applications. The issue is outlined in Windows Knowledge Base article Q899522.

The hot fix required to resolve this issue is not available for download and must be sourced from Microsoft directly.

Windows 2003 Server (SP 1) and Windows XP (SP 2)

A second problem that may occur on Windows XP or Windows Server 2003 is that Data Execution Prevention (DEP) may be enabled for all programs. DEP stops executable code from running in either the data or stack segments. The Windows POSIX subsystem requires code to be run in these segments, so DEP must be configured accordingly. A complete description of DEP can be found here. In order for the POSIX subsystem to execute DEP must be set in either OptIn or AlwaysOff mode. The mode is set via the /noexecute option found in boot.ini. A setting of OptOut or AlwaysOn will cause the POSIX subsystem to malfunction.