Your browser does not allow storing cookies. We recommend enabling them.

SSH Tectia

Upgrading Previously Installed SSH Tectia Server Software


Before starting the upgrade, make backups of all configuration files where you have made modifications.

When upgrading a maintenance release of SSH Tectia Server on Windows, usually no rebooting of the computer is needed. Check the release notes to see if the current Server release can be upgraded without reboot. On Unix, upgrading does not require a reboot.

If you are running both SSH Tectia client-side tools and SSH Tectia Server on the same machine, install the same release of each SSH Tectia product, because there are dependencies between the common components.

Check if you have some Secure Shell software, for example earlier versions of SSH Tectia products or OpenSSH server or client, running on the machine where you are planning to install the new SSH Tectia versions.

Before installing SSH Tectia Server on Unix platforms, stop any OpenSSH servers running on port 22, or change their listener port. You do not need to uninstall the OpenSSH software.

The following table shows you which SSH Tectia versions you need to uninstall before you can upgrade to SSH Tectia Server 6.1. When upgrading versions marked upgrade on top, the earlier version is automatically removed during the upgrade procedure. Also, when installing via SSH Tectia Manager, the earlier versions are removed automatically.

Table 2.2. Upgrade lines

SSH Tectia versionAIXHP-UXLinuxSolarisWindows
SSH Secure Shell 2.x-3.xremoveremoveremoveremoveremove
SSH Tectia 4.0removeremoveremoveremoveremove
SSH Tectia 4.1-4.xremoveremoveremoveremoveupgrade on top
SSH Tectia 5.x-6.xupgrade on topupgrade on topupgrade on topremoveupgrade on top

The configuration file format and file locations have been changed in SSH Tectia Server 5.0. Because of that, the configuration files behave differently when upgrading from 4.x and from 5.x-6.x:

  • The 4.x configuration files are not migrated to 6.1, but the default 6.1 configuration is used. However, the connection profiles are migrated from 4.x to 6.1 on Windows platforms.

  • The 5.x-6.x configuration files are migrated to 6.1 as such and automatically taken into use there.

When necessary, you can modify the configuration files by using the SSH Tectia Configuration GUI or by editing the XML configuration files manually with an ASCII text editor or an XML editor.

A separate document, SSH Tectia Client/Server Migration Guide, gives detailed instructions on upgrading from the SSH Tectia client/server solution 4.x to 6.x, including information on migrating the configuration files.

Want to see how PrivX can help your organisation?

Are you a DEVELOPER accessing cloud hosts, are you a IT ADMIN managing access & credentials in your corporation, are you BUSINESS MANAGER and want to save money or are you responsible of IT SECURITY in DevOps