Your browser does not allow this site to store cookies and other data. Some functionality on this site may not work without them. See Privacy Policy for details on how we would use cookies.

SSH Tectia

SSH Tectia Installation and Upgrade

When the managed hosts have opened management connections to the Management Server, the administrators can view the hosts in the administration interface. Now the hosts are ready for centralized management.

The first task is to deploy SSH Tectia software to the hosts and to upgrade those hosts that are running an outdated or a third-party version of Secure Shell. This can be performed as a single management task, by selecting a target host group and by specifying the required SSH Tectia software version for deployment. See Figure 5.2.

Deploying SSH Tectia Client via the administration interface

Figure 5.2. Deploying SSH Tectia Client via the administration interface

SSH Tectia Manager verifies the operating system running on each host that is queued for installation, and selects the appropriate installation package. The administrator can select which optional features are to be installed on each host type. SSH Tectia Manager then pushes the installation packages to the hosts over the management connection (see Figure 5.3), and performs the installation without requiring any further administrator interaction.

SSH Tectia deployment

Figure 5.3. SSH Tectia deployment

The Management Agent notifies the Management Server on the success or failure of the installation jobs.

If an existing SSH Secure Shell server on Unix is upgraded to SSH Tectia Server, the open Secure Shell sessions will continue running (using the old server version), while all subsequent new sessions are opened with the new SSH Tectia version.

If an existing SSH Secure Shell client on a Windows workstation is upgraded to SSH Tectia Client while the user has the client application open, the user can be notified and given a grace period, after which the application is shut down and upgraded.

If a host is offline at the time of deployment, the installation job will remain pending until the host is online the next time, and its Management Agent connects to the Management Server. The pending installation job is then performed automatically.