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

SSH Tectia

Upgrading SSH Tectia Manager

To upgrade an old version of Management Server, follow the steps described below. Removing and upgrading the Management Server leaves the existing configurations intact. The database contents and tables are updated automatically.

For detailed instructions for upgrades when using Sybase and Oracle databases, see the following sections.

The upgrade process consists of

  • upgrading the Management Database and drivers

  • upgrading the Management Server

  • upgrading the Management Agents remotely

  • following that all the hosts are correctly upgraded to the new version.

Old Management Agents are backwards compatible for the upgradability of the Management Agent. Using other management functionalities with an old Management Agent may cause various problems and is not guaranteed to work. Therefore, upgrading the Management Agent to the latest version as soon as possible is highly recommended. Using a new Management Agent with an old Management Server is not recommended.


The configuration user interface for SSH Tectia Client G3 has been simplified in SSH Tectia Manager release 6.0. After the upgrade, you should gradually migrate SSH Tectia Client 5.x configurations generated with SSH Tectia Manager 2.x to the new configuration format. For smooth transition, the Legacy configs tab is provided for compatibility with SSH Tectia Client 5.x configurations created using SSH Tectia Manager 2.x. For more information, see Legacy Configurations (SSH Tectia Client 5.x).

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