Windows

FlexxAgent supports 64-bit Windows operating systems; it cannot be installed on 32-bit systems. The installation binary is available with and without a graphical interface, making it fully compatible with unattended deployment mechanisms and the installation wizard.

FlexxAgent consists of a Windows service called FlexxAgent Service, which manages two processes: FlexxAgent (process), which runs at the system level, and FlexxAgent Analyzer (process), which starts for each user session.

This structure enables FlexxAgent to address multiple session devices, such as terminal servers, Citrix, or AVD, and acquire detailed metrics to enhance diagnostic capabilities.

For example, if a person is working on their laptop, the FlexxAgent process would run at the system level, and the FlexxAgent Analyzer would run from the user's identity. If the device hosts multiple user sessions, in addition to FlexxAgent at the system level, FlexxAgent Analyzer will run for each user session on that device.

Regarding resource requirements, FlexxAgent has very optimized consumption, hovering around the following values:

• Disk space used: < 200 MB
• CPU: < 0.5%
• RAM: 100-200 MB

FlexxAgent Service (system)

• For resource consumption information, including performance counters, hardware, sessions, profiles, disks, partitions, and Windows services, the default value is 60 seconds.
• Event log error events are sent every 10 minutes.
• User profile information is obtained every 15 minutes.

FlexxAgent Analyzer (user)

• Includes application usage analysis, diagnostic data, and user experience.
• Data is collected locally every 15 seconds.
• The report is sent to the service every 5 minutes.

These values can be adjusted in Settings on the different consoles, providing flexibility to meet specific needs.

Supported versions

The operating systems compatible with FlexxAgent are those still within the manufacturer's support cycle. Although installation is allowed on versions without such support, certain functionalities might not be available.

Microsoft operating systems with full support and compatibility are:

• Microsoft Windows 10 or later
• Microsoft Windows Server 2016 or later

FlexxAgent can also be installed on Windows 7 and 8.1 SP1, Windows Server 2008 R2 SP1, and Windows Server 2012, but it will be subject to some limitations.

Software Requirements

FlexxAgent also requires certain software components:

• .NET Framework 4.6.2 or later
• Windows PowerShell 4.0 or later (Windows PowerShell 5.1 recommended)

Limitations

When using FlexxAgent on older Windows operating systems that are out of support, it does not support the following Analyzer features:

• User surveys
• GPU consumption metric collection
• Flow execution
• User microservices execution

If FlexxAgent is installed on a Windows 7 or Windows Server 2008 R2 operating system, the following KBs must be installed:

• KB4474419: SHA-2 code signing support update for Windows Server 2008 R2, Windows 7, and Windows Server 2008: September 23, 2019.
• KB3140245: Update to enable TLS 1.1 and TLS 1.2 as default secure protocols in WinHTTP in Windows and follow the instructions in the section How to enable TLS 1.1 and TLS 1.2 as default secure protocols in WinHTTP in Windows on the Microsoft support page.

Download

The installation binary download is available without a graphical interface.

Installation binary download without graphical interface

To download FlexxAgent without a graphical interface, it is necessary to do so from Workspaces -> Level 2 -> Report groups. In the upper right part of the screen there is a button that allows the download with two options:

• Minimum installation package: During the installation, the binary will access the internet to check and download the most recent binaries.
• Standalone package: During the installation, the binary will not require internet access to check or download binaries.

Unattended deployment

The agent supports being launched through unattended deployment methods such as distribution by GPOs, Intune, SSCM, and many more tools.

Installation

Unattended installation is performed via PowerShell.

Start-Process "<path>\FlexxAgent-Installer.exe" -ArgumentList "<add parameter>" -WindowStyle Hidden -Wait

Example of unattended installation adding installation parameter:

Start-Process "<path>\FlexxAgent-Installer.exe" -ArgumentList "-repairAgent true" -WindowStyle Hidden -Wait

Uninstallation

To uninstall unattended: "C:\Program Files\Flexxible\FlexxAgent\VDIServiceUpdater.exe" /Uninstall "C:\Program Files\Flexxible\FlexxAgent\FlexxAgent.exe" /quiet

Supported parameters

Parameter	Type	Description
RepairAgent	[bool]	Forces the repair. Fails if the agent is not installed.
proxyAbsoluteUri	[string]	Proxy URI and port.
proxyUser	[string]	User for authenticated proxy.
proxyPass	[string]	Password for authenticated proxy.
proxyPersistConfig	[switch]	If specified, the configuration persists in the registry.
configFilePath	[string]	Alternative directory for the FlexxAgent-Configuration.conf file.
DebugMode	[switch]	When specified, it creates a text file in the same folder with the script execution log.

Proxy configuration

FlexxAgent supports transparently configured proxies at the system level without configuring. Proxies with and without authentication are also supported. Proxy configuration can be done via the command line or by modifying registry keys that control this configuration.

Proxy configuration via command line

Installation with parameters: FlexxAgent-Installer.exe -proxyAbsoluteUri ip.ad.dre.ss:port -proxyPersistConfig:$True

Where ip.ad.dre.ss:port is the proxy IP or DNS plus the port, or including credentials:

FlexxAgent-Installer.exe -proxyAbsoluteUri ip.ad.dre.ss:port -proxyUser ProxyUserName -proxyPass ProxyUserPassword -proxyPersistConfig:$True

Configuration through registry keys

The registry keys that store the proxy configuration for FlexxAgent are located at:

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Flexxible\FlexxAgent\Communications

Registry keys related to proxy configuration:

• Key Proxy_URL
• Key Proxy_User
• Key Proxy_Pwd

Proxy_URL Key

• Key path: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Flexxible\FlexxAgent\Communications
• Key name: Proxy_URL
• Key type: REG_SZ
• Allowed values: the URL and port; for example http://192.168.1.1:3128 or https://192.168.1.1:3128

Proxy_User Key

• Key path: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Flexxible\FlexxAgent\Communications
• Key name: Proxy_User
• Key type: REG_SZ
• Allowed values: the username to authenticate to the proxy; for example Administrator. It can be omitted for unauthenticated proxies.

Proxy_Pwd Key

• Key path: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Flexxible\FlexxAgent\Communications
• Key name: Proxy_Pwd
• Key type: REG_SZ
• Supported values: The password to authenticate with the proxy. It can be omitted for unauthenticated proxies. The Proxy_Pwd key value can be set in plain text (not recommended) or encoded in base64 and enclosed by «&&&». For example: &&&VGhpc0lzTjArQCQzY3VyZVBAJCR3MHJk&&& for the “Proxy_Pwd” value. In either case, FlexxAgent encrypts the value as soon as FlexxAgent starts or tries to transmit information. You can use a site like https://www.base64encode.org/ to create the base64 encoded password string.

Update

FlexxAgent can be updated automatically or manually from Workspaces.

Automatic Update

This functionality is controlled with settings that are usually enabled in Workspaces. The path to view or change the settings for this feature is Workspaces -> Level 3 -> Settings -> Auto update. Selecting True will allow a new version of FlexxAgent to be automatically sent to all active devices in the organization when detected. This action will leave a Job in Workspaces with all the operation details.

Manual Update

The path to manually update FlexxAgent: Level 1 -> Workspaces -> Operations -> FlexxAgent -> Update to latest version.

Different installed versions can be seen in the drop-down option My filters -> Predefined filters -> FlexxAgent version summary. This will generate a view of all devices grouped by the FlexxAgent version.

Once the update operation is executed, a Job with all the details of the operation will be generated in the corresponding section.

Logs

FlexxAgent can generate three types of logs:

• Installation and update logs
• FlexxAgent Analyzer logs
• FlexxAgent service logs

These logs allow you to consult information and diagnose problems from the installation of FlexxAgent.

Installation and update logs

Inside the folder C:\Windows\Temp\Flexxible a text log is left containing information about the installation or update process, including dependency information and process details.

FlexxAgent Analyzer logs

Logs from FlexxAgent Analyzer are stored in the %LOCALAPPDATA%\FAAgent\Logs directory. These can be configured to include or exclude information based on criticality levels.

Change log level for FlexxAgent Analyzer

From Workspaces, it is possible to change the log level for one or multiple devices using the options available in the Operations button.

FlexxAgent service logs

FlexxAgent service logs can be consulted in the Application branch, within the Event Viewer of Windows.