(8/4/22): Leostream Platform 9.1 Update 5 Release Notes

Posted over 1 year ago by Zachary Leger

  • Topic is Locked
Zachary Leger Admin

Leostream Platform 9.1 – Revision 5

Important Notes

  • The Last Connect Time on the > Resources > Desktops page is now updated only when the Leostream Agent returns a valid username in the connection notification. This change improves the accuracy of the Last Connect Time field, except for the following two cases.
    • Leostream Agents installed on Windows 7 machines may not return usernames in the connection notifications, resulting in the Last Connect Time not being updated. Note that Leostream no longer officially supports Windows 7 guest operating systems.

    • Leostream Agents installed on VMware templates that were not properly shutdown prior to being used in Leostream will return connection notifications when new machines are provisioned from the template, resulting in the Last Connect Time being updated as soon as the new VMs are provisioned. Ensure that you shut down virtual machines prior to creating templates to use with Leostream (see “Provisioning from VMware Templates” in the Connection Broker Administrator’s Guide.)

  • Connection Broker 9.1 enables the RESTful API, by default, and therefore requires additional RAM. If you are upgrading from Connection Broker 9.0 or installing a new Connection Broker, ensure that your Connection Broker RAM is at least 8GB prior to upgrading or installing Connection Broker 9.1, respectively.

  • Version 7.4.13 and higher of the Leostream Agent for Windows Operating system and 5.2.10 and higher of the Leostream Agent for macOS and Linux now distinguish between older versions of RGS and newer versions of HP ZCentral Remote Boost. If you define Pools based on the Installed Protocols attribute having a text value of RGS, edit the pool to include machines with Boost installed, as well, to ensure desktops running all versions of the protocol appear in the pool.

Connection Broker 9.1.24


  •  The leostream-broker CLI includes a new option to specify if the Connection Broker should automatically reboot after installing a license that enables features that require a reboot 
  •  Additional AWS instance types and Azure instances sizes are available for provisioning in pools

Resolved Issues

  •  Client settings, such as client bindings, are no longer overwritten every time a user logs into the Connection Broker from that client 
  •  Windows Server 2019 instances from an AWS center are now labelled with the correct operating system version

0 Votes