Skip to main content

​
One installation script, three flavors of monitoring parameters

The Syteca Linux Client is installed locally from the command line on each Linux endpoint. Linux Clients do not support remote installation via the Management Tool the way Windows Clients do; every Linux endpoint is installed from its own Terminal. The same SytecaLinuxClient.tar.gz archive is used across all variants. What differs is how monitoring parameters are supplied to the install.sh script:
On Solaris and AIX distributions, GNU Bash 3.2.25(1) or higher must be installed before running install.sh. On Solaris specifically, update the bash before proceeding.
In SaaS deployments, the Application Server is reached through the load balancer on the Syteca proxy server. Use the load balancer hostname (or IP address) as the server argument, and use port 443 instead of 9447. This applies to all three variants below.

​
Prerequisites

Before starting a Linux Client installation:
  1. Verify the target endpoint meets Linux Client system requirements.
  2. Download the appropriate installation package from the Management Tool. Options include:
    • SytecaLinuxClient.tar.gz (default monitoring parameters, x64 or x86 variant).
    • SytecaLinuxClient.tar.gz containing an .ini file (custom monitoring parameters, generated in the Management Tool).
    • .rpm package (for use with RPM Manager on Red Hat, CentOS, and derivatives).
    • Linux powerpc64le package (for IBM Power architecture endpoints).
  3. Have sudo access on the target endpoint.

​
Install with default monitoring parameters

The default installation variant reads the Application Server name and port from command-line arguments to install.sh. It is the simplest procedure and appropriate for one-off installs.
1

Copy the installation package to the target endpoint

Transfer SytecaLinuxClient.tar.gz to any folder on the target Linux endpoint. Verify the correct architecture variant (x64 vs. x86) matches the endpoint.
2

Open a Terminal and navigate to the folder

Run the Terminal, then change to the folder containing the installation package:
3

Unpack the installation package

Extract the archive:
4

Navigate to the EkranClient folder

The folder contains the install.sh script used to install the Client.
5

Run the installation script

Specify the Application Server name (or IP) and the port used for connection (port 9447 is recommended):
For Multi-Tenant deployments installing to a specific tenant, add the -tenantKey parameter:
In Multi-Tenant mode, the Tenant Key can be copied from the Management Tool (on the Tenants page) by the administrator of the built-in default tenant. If no Tenant Key is specified, the Client is installed on the built-in default tenant.
For SaaS deployments, use the load balancer hostname and port 443:
6

(Optional) Enable X11 GUI session monitoring

To monitor GUI sessions on X Window System (X11) endpoints, add the -withX11 flag:
The Client connects to the Application Server at IP 10.100.4.182 through port 9447, with X11 GUI session monitoring enabled.Combined with -tenantKey for Multi-Tenant:
After installation, the Client appears in the list on the Clients page of the Management Tool. Monitoring starts on the next user login on the endpoint.

​
Install with custom monitoring parameters (INI file)

Use this variant when the SytecaLinuxClient.tar.gz archive contains a bundled .ini file with custom monitoring parameters generated in the Management Tool. The INI file contains parameters like Offline cache size and Command output skipping that are not accessible from the install.sh command line.
NOT AVAILABLE IN SAAS. Custom monitoring parameters via INI file are not available in Syteca SaaS deployments.
1

Copy, unpack, and navigate to EkranClient

Same first four steps as the default installation above: copy the package to a folder, navigate there, unpack with tar xvfz, and change directory to EkranClient.
2

Run install.sh with no server argument

The Application Server name and port come from the bundled INI file, so no server argument is needed on the command line:
The default Server port for the INI-file variant is 9447.
For Multi-Tenant deployments:
3

(Optional) Enable X11 GUI session monitoring

Add -withX11 to enable X Window System GUI session recording. Example combining X11 and Multi-Tenant:
The Client connects to the Application Server named in the .ini file, on port 9447, with X11 GUI session monitoring enabled and joined to the tenant with the specified key.
After installation, the Client appears on the Clients page of the Management Tool.

​
Install on SELinux endpoints

SELinux-enabled Linux endpoints need a SELinux-compatible variant of the Client. The installer picks this variant automatically when running on an SELinux endpoint, so the installation procedure is identical to the standard Linux Client procedure.
SELinux must be enabled and operating in Enforcing mode on the target endpoint before starting the installation. Verify this with sestatus before beginning.

​
Supported installation packages for SELinux

Any of the standard Linux installation packages downloaded from the Management Tool works for SELinux:
  • Linux x64 Client Installation (.tar.gz) with default monitoring parameters.
  • Linux x64 Client Installation Package (.tar.gz + .ini) with custom monitoring parameters.
  • Linux x64 Client Installation (.rpm) for use with RPM Manager.

​
Automatic variant selection and override flags

The installer detects the SELinux environment and automatically selects the SELinux-compatible variant included in the package. Override with these flags if the automatic selection does not match your needs:

​
Installation command

Same as the default Linux Client install:
For SaaS deployments:
After installation, the SELinux-compatible Client appears on the Clients page of the Management Tool. Monitoring starts on the next user login on the endpoint.

Linux Clients

How the Linux Client behaves in remote SSH, local terminal, and GUI (X11) sessions, plus how to read Client status from the Management Tool and the CLI.

System requirements

Supported Linux distributions, glibc requirements, and hardware sizing.

Install Windows Clients

Windows Client installation methods for comparison, including remote installation.

Install macOS Clients

macOS Client installation from the command line.