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


Preparing for Installation

Check and execute the following steps before starting the installation:

  1. Make sure that you have enough space on the host and file system you are installing the Management Server on. Up to 100 MB is needed during the installation. You may remove the installation packages and extracted installation files after a successful installation.

    Normal operations require disk space for log storage and imported managed software versions. The Management Server stores all collected log data in the Management Database, and large deployments of over 100 hosts may produce considerable amounts of data over time. Reserve enough space for the log data and follow the growth of the database. If the size of the database is to exceed 2GB, use an external database instead of the built-in Management Database. Setting up an Oracle database with Tectia Manager is described in Using an Oracle Database.

    For instructions on managing and deleting logs, see Managing Logs

  2. Make sure that there are no other web servers running on ports 80 or 443 on the Tectia Manager host. If another service reserves these ports, the ssh-mgmt-server startup will fail. If this happens:

    1. Check the service reserving the port, for example, with the netstat utility.

    2. Stop the service reserving the port in question.

    3. Restart ssh-mgmt-server.

  3. Check that the web browser allows the use of cookies. The session control of Tectia Manager uses cookies, and if the browser does not support or accept them properly, the user gets returned to the login page after a login attempt.

  4. Check that the file descriptor ulimit defined in the operating system settings is big enough (for example, on Linux the limit is by default 1024). The Management Server uses 1 file descriptor per Management Agent or Distribution Server connecting directly to it. Increase the ulimit to exceed the number of Agents and Distribution Servers connecting to the Management Server.

    In case you want to keep the ulimit under a certain level also in large environments, use more Distribution Servers in the environment.

  5. Check that the installation CD is located and accessible on the target server CD-ROM drive or the installation CD has been copied to the hard disk of the server. The installation commands described in this document assume that you are in the installation root directory (referred to as /cdrom/ later in the text).

  6. Create a dedicated user account for the Management Server. This can also be done automatically during the initial configuration (see Initial Configuration for Management Server).

    The default is sshmgmt and <path>/sshmgmt is the home directory for the user. Use passwd -l sshmgmt to prevent logon using the sshmgmt account:

    $ su - root 
    # useradd -m -d <path>/sshmgmt sshmgmt 
    # passwd -l sshmgmt

    In the previous command, <path>/sshmgmt is the home directory for the user sshmgmt and should exist for storing Secure Shell host keys used in the initial deployment through Secure Shell. The user sshmgmt is used for running the Management Server processes and for opening the Management Agent initial deployment Secure Shell connections. It is typically not used for accessing the Management Server host from outside the host.




What to read next:

  • Reduce Secure Shell risk. Get to know the NIST 7966.

    The NISTIR 7966 guideline from the Computer Security Division of NIST is a direct call to action for organizations regardless of industry and is a mandate for the US Federal government.
    Download now
  • ISACA Practitioner Guide for SSH

    With contributions from practitioners, specialists and SSH.COM experts, the ISACA “SSH: Practitioner Considerations” guide is vital best practice from the compliance and audit community.
    Download now