(8/10/22): Leostream Platform 9.1 Update 6 Release Notes

Posted over 1 year ago by Zachary Leger

Zachary Leger Admin

Leostream Platform 9.1 – Revision 6

        The following release notes describes the issues resolved in this revision of the Leostream Platform.

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.

    • Leostream Agents installed on VMware templates that were not properly shutdown prior to creating the template return connection notifications when new machines are provisioned from the template, resulting in the Last Connect Time being updated. Ensure that you shut down virtual machines prior to creating templates to use with Leostream.

  • Connection Broker 9.1 enables the RESTful API, by default, and therefore requires additional RAM. Ensure that your Connection Broker has at least 8GB prior to upgrading or installing.

  • 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.25

  • Leostream Connect 4.4.6 for Windows Operating Systems: Resolves issues launching NoMachine connections

  • Ensure that the Match resolution user-configurable parameter for desktop connections using HP ZCentral Remote Boost is always honored when enabled by the user

  • Provisioning in pools is now disabled after the AWS account associated with the Center reaches its vCPU limit for the region

  • Customizations to table columns, such as the > Resources > Desktops page, made by users that log into Leostream using a SAML-based authentication server are not persistent

  • Previously inventoried Azure images are no longer removed from the Connection Broker if a Center scan is unable to retrieve images from an Azure Compute Gallery

  • Entries in the Proxy Address field can now be removed from AWS centers

0 Votes


Login or Sign up to post a comment