Linux

FlexxAgent for Linux allows for the inclusion of devices running this operating system into the Flexxible service consoles, enabling their centralized management and monitoring. The agent is designed to operate in various types of environments, including physical devices, machines, and virtual desktops, making it a solution adaptable to diverse infrastructures.

The following types of devices are supported:

• Physical Linux devices
• Virtual devices on VMware as hypervisor
• VDIs published using Citrix as broker

Supported distributions and versions

FlexxAgent is compatible with the following Linux distributions:

• Fedora 37 or later
• Debian/GNU Linux 11 (Bullseye) or later
• Ubuntu 22.04, 24.04

To request the inclusion of a new distribution, contact the Flexxible team.

Requirements

Before installing the agent, updating all operating system packages is recommended. During the installation process, the necessary components will be automatically added based on the detected distribution.

Required package dependencies in Fedora and Debian:

• dmidecode
• imvirt
• systemd

Limitations

Some functionalities are not available on Linux systems, including:

• Flexxible Remote Assistance
• User microservices
• Flow execution
• Data collection from plug and play peripherals

The execution of microservices on demand from the Workspaces module supports Bash as the scripting language.

Download and installation

The installation of FlexxAgent on Linux is carried out using an installation script and a deb or rpm file, with the latter used for offline installation (without automatic download of the installation package).

To perform the installation, click on the Download FlexxAgent button located in the Portal's sidebar.

Next:

1. Select a report group from the respective dropdown menu.

2. Download the license/configuration file (.conf) and the Linux installer.

   

Available installer types

Advanced options allow you to select the type of installer according to the distribution:

• Debian

  • sh (recommended option): standard installation or offline installation.
  • deb: offline installation.

• Fedora

  • sh (recommended option): standard installation or offline installation.
  • rpm: offline installation.

  

Installation script parameters

Parameter	Caption
-v,--version <VERSION>	Use a specific version, by default latest.
-d,--distro <DISTRO>	The script automatically detects the distribution of the system it is running on. This parameter allows you to force the installation of the FlexxAgent version for a specific distribution when working with derived or similar distributions.
--verbose,-Verbose	Displays diagnostic information.
-c,--config <CONFFILE>	Applies the configuration from a configuration file by default settings.conf.
-o, --offline	Installs FlexxAgent from a given package file, instead of downloading it.
-?,--?,-h,--help,-Help	Shows help.

Examples

• Install FlexxAgent with the configuration file:

flexxagent-install.sh [-c|--config <path/file.conf>]

• Install a specific version of FlexxAgent:

flexxagent-install.sh [-v|--version <VERSION>]

• Force the FlexxAgent installation for a specific distribution:

flexxagent-install.sh [-d|--distro <DISTRO>]

• Access the help:

flexxagent-install.sh -h|-?|--help

Offline installation

FlexxAgent can be installed in environments with network restrictions or no internet access.

Steps for installation:

1. Place the FlexxAgent package file, the configuration file, and the installation script in the same folder.

2. Grant permissions to the script:

sudo chmod +x ./flexxagent-install.sh

1. Run the script with the -o or --offline parameter and indicating the name of the package file to install:

sudo ./flexxagent-install.sh -c [archivo de configuración] -o [paquete de Flexxagent]

4. Delete the files used if they are no longer needed.

Uninstall

The uninstall script can be downloaded from the following URL:

https://update.workspaces.flexxible.com/agents/Linux/FlexxAgent/latest/flexxagent-uninstall.sh

Steps for uninstallation

1. Download the uninstaller from the URL.
2. Grant permissions to the script.

   sudo chmod +x ./flexxagent-uninstall.sh

3. Run the script.

   sudo ./flexxagent-uninstall.sh

4. Clean the files used.

Uninstallation script parameters

Parameter	Caption
-d,--distro <DISTRO>	The script automatically detects the distribution of the system it is running on. This parameter helps to force the uninstallation of the FlexxAgent version for a specific distribution when working with derived or similar distributions.
-c,--cleanup <VERSION>	Cleans configurations and logs; default is false.
-?,--?,-h,--help,-Help	Shows help.

Examples

Uninstall and clean configurations and logs:

flexxagent-uninstall.sh [-c|--cleanup]

Force the uninstallation for a specific distribution:

flexxagent-uninstall.sh [-d|--distro <DISTRO>]

Access the help:

sudo ./flexxagent-uninstall.sh --help

Proxy Configuration

Proxy configuration must be done before installation by modifying the configuration file downloaded from Portal.

Unauthenticated proxy

• proxy = http://proxy_uri:port
• Example: proxy = http://192.168.0.100:443

Authenticated proxy

• proxy = http://user:password@proxy_uri:port
• Example: proxy = http://proxy_user:xxxxxxxx@192.168.0.100:443

Update

FlexxAgent can be updated to the latest version in two ways:

• From Workspaces, select the device and perform: Operations -> FlexxAgent -> Update to the latest version.
• Re-run the installation script to download and install the latest version.

Information obtained from the device

FlexxAgent collects data locally from the device and sends it to the service consoles.

General information

• Name. Device Name.
• Device Status. Power status of the device, can be On, Off, or Not reporting.
• FlexxAgent Version. Version number of FlexxAgent installed on the device.
• FlexxAgent Status. Running or Stopped.
• Last FlexxAgent report. Date and time of the last FlexxAgent report on the device. This date might not be recent if the FlexxAgent service is stopped or the device is off.
• Connection Type. Indicates if the device is connected via Wireless LAN, Mobile Network, Ethernet, or Unknown.
• Network. Network addressing of the device and public IP for internet access. These networks are created automatically when more than four devices are connected to the same network.
• Network Signal. Network reception percentage.
• Subnet. Device's network addressing.
• MAC Address. Unique identifier of the device's network card.
• Wireless Network. Name of the network.
• Connection signal. Percentage of signal reception when the device connects using a wireless method.
• Network Changed. Date and time of the last network change.
• Sessions. Number of user sessions on the device.
• Last User. Last user logged into the device in domain\account format.
• Connected From. When the selected device is a VDI or similar, shows the device name from which the virtual device is accessed.
• Connection Time. Date and time when the session started.
• Code. Lets identify the device with a personal code. This code must be manually filled in individually using the Edit option in the Operations menu of the workspace details.
• Description. Allows the user to identify the device with a personal description. This field must be assigned manually and individually using the Edit option in the Operations menu of the device details.

Extended Info

• RAM. Total capacity of available RAM.
• Cores. Number of processor cores.
• IP Address. Device's IP address on the local network.
• OS. Type of operating system.
• Operating System. OS version.
• Region. Obtained using the public IP. It might not be accurate if connected to a corporate network or using a VPN.
• Broker type. If detected, shows the session broker used.
• Delivery group. For VDIs, shows the delivery group to which the device belongs.
• Subscription. If detected, subscription in use for Citrix Cloud, Azure services, etc.
• Hypervisor. If virtualization is detected, shows the hypervisor used.
• Session Analyzer. Indicates whether or not it's configured to launch session Analyzer in all user sessions.
• Session Analyzer version. Session Analyzer version number.
• Report Group. Reporting group to which the device belongs.

Information in tabs

FlexxAgent groups information about the following aspects of the device:

Sessions

Displays a table with the log of user sessions established on the device and timely information about the session type, connection status, or start date.

Performance

Displays graphs of the device's main performance counters, based on data collected over the last two hours. The following are included:

• CPU. Processor usage percentage.
• Memory. Amount of memory used and available.
• Bandwidth Usage. Amount of incoming and outgoing traffic.

At the top, a link grants access to the Analyzer module.

Jobs

All actions performed from the Workspaces module on one or more devices are audited in the Jobs queue. This tab allows you to check the work done for the active device.

Alert

Presents a table with the list of all active alerts on the device. When an alert is logged, a notice is displayed at the top of the page.

Connection Log

Presents a list of the connections established with the device, including each instance where a user logs in or reconnects a previously disconnected session.

The session end date is recorded only for sessions that have been disconnected or closed. While the session remains active, this field will remain empty.

Disks

Displays a list of all partitions present on the disks identified in the system, as well as statistics of their capacity and occupancy levels.

Notifications

Allows you to see if the device has any active notification. When there is one, a message is displayed at the top of the page.

Reporting groups history

Allows you to see which reporting groups the device belongs to, the date of incorporation, and if it has been assigned to the group manually or automatically.