SSH Tectia

Installing on Windows

The Windows installation packages are provided in the MSI (Microsoft Installer) format. The package is also compatible with Microsoft Windows Server 2003 x64 Edition.

SSH Tectia Server includes support for Entrust certificates on Windows 2000 and Windows XP. The necessary libraries are automatically included in the installation.

The installation is carried out by a standard installation wizard. The wizard will prompt you for information and will copy the program files, install the services, and generate the host key pair for the server.

On the CD-ROM, the installation package for Windows is located in the /install/windows/ directory.


SSH Tectia Server cannot be installed on file systems that do not support permissions (for example, FAT16 or FAT32). The hard disk partition where SSH Tectia Server is installed should use the NTFS file system.

You must have administrator rights to install SSH Tectia Server on Windows.

To install SSH Tectia Server on Windows, follow the instructions below:

  1. Locate the installation file ssh-tectia-server-<ver>.msi (where <ver> corresponds to the version and build number, for example Double-click the installation file, and the installation wizard will start.

    If you are running the .msi installer directly from the online .zip package, you have to import the license file (sts52.dat) after completing the installation. If you have extracted the contents of the online .zip package before running the .msi installer or if you are installing from a CD-ROM, the license file is imported automatically.

  2. Follow the wizard through the installation steps and fill in information as requested.

    The server host key is generated during the installation. Key generation may take several minutes on slow machines.

  3. When the installation has finished, click Finish to exit the wizard.

  4. The installation should (re)start the server automatically.

    If the server does not start (because of a missing license, for example), you can start it after correcting the problem from the Windows Services console. See Starting and Stopping on Windows