Month: December 2020

Released flexVDI gateway 3.1.1

Changes since 3.1.0

  • Fixed bug: A race condition caused flexvdi-gateway to crash sometimes, closing all user sessions it was serving, and restarting immediatelly.

To update your servers, log in to your flexVDI Hosts with ssh and run:

yum update flexvdi-gateway

You can do this at any time, as it will not cause any service disruption.

Afterwards, you will have to start the new version of the gateway with:

systemctl restart flexvdi-gateway

This second step will not stop any virtual machine, but it will close established connections that are going through the restarted gateway. All end users that are connected through the restarted flexvdi-gateway will see their connection closed and will have to login with flexvdi-client again.

 

 

Released flexVDI Manager 3.1.6

Changes since 3.1.5

  • Fixed bug: all timestamps in flexVDI manager log lines are now shown in local time. This is effective for new installations. If you want to fix the configuration of a flexVDI manager installed with a release of flexVDI Manager before 3.1.6 see https://docs.flexvdi.com/display/V31/Problems+with+flexVDI+Manager
  • Fixed bug: volatile desktops lost their disk contents when they where modified in flexVDI Dashboard and restarted or .
  • Many CentOS packages, including kernel and mongodb have been updated in the flexVDI Manager appliance.
  • Privacy improvement: error messages returned when authenticating against an LDAP server are now not written to the log file file by default. Some LDAP servers include sensitive information in these messages.

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 portal.flexvdi.com, for servers not connected to the internet.