Category: ChangeLogs

Released flexVDI agent 3.1.7

Fixes a bug in the creation of flexvdi manager that causes flexvdi manager to get a wrong clock time from the hardware clock when it is started, if the flexVDI Host is not configured in UTC.

The fix will take effect after updating the package, the next time flexVDI manager is started.

The new release can be updated executing in the flexVDI hosts:

# yum -y update flexvdi-agent

Released flexVDI manager 3.1.4

Changes since 3.1.3

  • Includes support for LDAPS protocol (LDAP over TLS/SSL). Instructions for configuring flexVDI manager to trust additional CA’s or server certificates is available at
  • Port 7777 is now reserved and, flexVDI does not try to use it for spice connection to guest virtual machines. This port is used by default by the OCFS2 file system, which is usually used by flexVDI hosts. This number can be changed setting the value of “flexvdi.host_reserved.port” in /flexvdi/external/manager/flexvdi.conf.


flexVDI manager is available for update running flexvdi-config command on the host where the current manager is running. Instructions are available here. Also it can be manually downloaded from, for servers not connected to the internet.

Released flexvdi-webportal 3.1.1

Changes since 3.1.0

This release includes several changes:

  • Kiosk mode is properly implemented in the HTM5 client: when using a unauthenticated policy, end user is not required to enter a user password any more.
  • Full restyling: modern look with new background, fonts…
  • Desktop list presented to the end user is sorted, for easily finding the desired desktop.
  • Terminal ID is now shown in the login screen.
  • All software in the base system is updated to the latest CentOS 7.8 release.
  • Updated jquery library.

The new release can be freely downloaded at

Installation instructions are available at

Released flexvdi-client 3.1.4

Changes since 3.1.3

Fixes two problems when using a password that contains the ” character.

  • It now lets the user to login succesfully.
  • The part of the password after the ” could be written to flexvdi-client log file.

Also HTTP timeouts are longer now, so that even if the flexVDI server OS is not well configured (when the server is not able to resolve its own name to an IP address), flexVDI client can connect succesfully.