Windows

FlexxAgent supports 64-bit Windows operating systems, it is not possible to install it on 32-bit systems. The installation binary is available with and without a graphical interface, making it perfectly compatible with unattended deployment mechanisms, as well as by using the installation wizard.

FlexxAgent consists of a Windows service called FlexxAgent Service, which directs 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 target multi-session devices, such as terminal servers, Citrix, or AVD, and acquire detailed metrics to improve 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 from the user's identity; and if the device hosts multiple user sessions, in addition to FlexxAgent running at the system level, FlexxAgent Analyzer would run for each user session on that device.

Regarding resource requirements, FlexxAgent has very optimized consumption, 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.
• Error events from the event log 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.
• Data is collected locally every 15 seconds.
• The report is sent to the service every 5 minutes.

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

Supported versions

The operating systems compatible with FlexxAgent are those that are still within their manufacturer's support cycle. Although installation is allowed on versions that do not have that support, it should be noted that certain functionalities may not be available.

Supported and fully compatible Microsoft operating systems 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, unsupported Windows operating systems, 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 with a graphical interface.

Download the installation binary with a graphical interface

In Home there is a button to download FlexxAgent with a graphical interface. If the subscription has more than one reporting group, the button will redirect to the reporting groups view to allow downloading the agent from the desired group.

A few seconds after completing the installation, the device will be visible in Workspaces. From that moment on, all functionalities to control, monitor and automate tasks on your devices will be activated.

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 repair. Fails if the agent is not installed.
proxyAbsoluteUri	string	URI and port of the proxy.
proxyUser	string	User for authenticated proxy.
proxyPass	string	Password for authenticated proxy.
proxyPersistConfig	switch	If specified, the configuration is persisted in the registry.
DebugMode	switch	When specified, it creates a text file in the same folder with the script execution transcript.
configFilePath	string	Alternate directory for the FlexxAgent-Configuration.conf file.

Proxy Configuration

FlexxAgent supports transparently configured proxies at the system level, without the need for configuration. Proxies with and without authentication are also supported. Proxy configuration can be performed via 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 to the IP or DNS plus the proxy port, or including credentials:

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

Configuration via registry keys

The registry keys that handle storing the proxy configuration for FlexxAgent are located:

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

Registry keys related to proxy configuration:

• Proxy_URL Key
• Proxy_User Key
• Proxy_Pwd Key

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
• Accepted values: The password for proxy authentication. It can be omitted for unauthenticated proxies. The value of the key Proxy_Pwd can be set in plain text (not recommended) or encoded in base64 and enclosed by "&&&". For example: &&&VGhpc0lzTjArQCQzY3VyZVBAJCR3MHJk&&& for the value "Proxy_Pwd". In either case, FlexxAgent encrypts the value as soon as the FlexxAgent starts or attempts 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 by a setting in Workspaces that is usually enabled. The path to view or change this functionality's configuration is Workspaces -> Level 3 -> Settings -> Auto update. Selecting True will allow, when a new version of FlexxAgent is detected, it to be automatically sent to all active devices in the organization. This action will leave a Job in Workspaces with all operation details.

Manual Update

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

The different installed versions can be viewed in the dropdown option My filters -> Predefined filters -> FlexxAgent version summary. This will generate a view of all devices grouped by FlexxAgent version.

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

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 issues from the installation of FlexxAgent.

Installation and update logs

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

FlexxAgent Analyzer logs

Within the directory %LOCALAPPDATA%\FAAgent\Logs, the logs of FlexxAgent Analyzer are stored. These can be configured to include or not include information by criticality levels.

Change log level for FlexxAgent Analyzer

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

FlexxAgent service logs

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