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

SSH Tectia

Installing Remotely

The remote installation can be started from the Management Agent Initial Deployment page. To access the page, click Software → Initial Deployment on the menu. The remote installation via SSH Tectia Manager is available only to Unix hosts, but the remote upgrade is available to all supported hosts. See Upgrading Management Agents Remotely. To deploy the agents remotely to Unix hosts, follow the instructions below:

  1. Click Software → Initial Deployment on the menu.

  2. On the Management Agent Initial Deployment page, click New job.

  3. The Adding new Unix/Linux hosts under management page opens. See Figure A.2.

    • Select the Management Agent version to be installed.

    • Select the ICB file to use.

    • Select the installation method.

    • Enter the necessary credentials to log in to the target host(s).

    • Give one or more hostnames (separated by spaces and/or commas) of the target hosts, or browse to the location of a host list file.

    Deploying the Management Agent to Unix hosts

    Figure A.2. Deploying the Management Agent to Unix hosts

    The host list file is an ASCII file with one line for each target host. Each line should contain the hostname, username, password, su-username, and su-password separated by a TAB character. All except the hostname field can be left empty, in which case the values provided on the installation page will be used as default values.

    After you have made the necessary settings, click Start install.

  4. A summary of the host list is shown. After confirming that it is correct, click Yes to start the installations.

The progress of the installation can be viewed on the Management Agent initial deployment page. Click the Running tab to view the installation jobs in progress. Click the Finished tab to view the completed jobs.

For each target host, the following steps are completed by the Management Server to automatically install the Management Agent:

  • Connection to the target host is made using the protocol specified in the installation method field (see above), and the given user is logged in from the login prompt. If specified, su is used to gain additional privileges required for the installation.

  • File transfer is done over the terminal connection (rlogin/telnet) or by scp secure file copy application (ssh2). In case you encounter problems with the remote agent deployment, try using the selected connection method manually from the Management Server to the managed host with the sshmgmt user account.

  • A directory /tmp/<xxxxxxxxxx> is created for storing temporary files. The name of the directory is a random sequence of 10 characters.

  • A script is uploaded and run to determine the processor, architecture, operating system, and OS version of the host.

  • The installation package suitable for the host is uploaded. If there is no suitable installation package for the host, the installation is aborted.

  • The specified ICB file is copied to /var/opt/ssh-mgmt/agent/icb.dat.

  • The package is installed, temporary files are removed, and the user is logged out. The Management Agent starts and connects to the Management Server automatically.

The installation will run simultaneously for a limited number of hosts (default 5). This number can be changed on the Settings → System Settings page. Note that a limit that is too high can slow down the Management Server administration interface, in addition to causing a high network load.


Highlights from the SSH.COM blog:

  • Cryptomining with the SSH protocol: what big enterprises need to know about it

    Cryptomining malware is primarily thought of as targeting desktops and laptops and is used to hijack system resources to mine cryptocurrency.
    Read more
  • SLAM the door shut on traditional privileged access management

    Did you know that something as trivial-sounding as granting access for your developers or third parties to a product development environment can throw a gorilla-sized monkey wrench into your operations and productivity?
    Read more
  • We broke the IT security perimeter

    Everyone understands the concept of a security perimeter. You only gain access if you are identified and authorized to do so.
    Read more