Leostream Platform 9.1 Update 2 Release

Posted almost 2 years ago by Vlad Trofimov

  • Topic is Locked
Vlad Trofimov
Vlad Trofimov Admin

Leostream Platform 9.1 – Update 2

Important Notes

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.12


  • Component updates:
    • Leostream Agent 7.4.14 for Windows Operating Systems: Includes new functionality to receive instructions from the Connection Broker to close DCV sessions
    • Leostream Agent 5.2.12 for Linux and macOS
      • For Linux operating systems, includes new functionality to receive instructions from the Connection Broker to close DCV sessions
      • For macOS, resolves issues related to idle-time monitoring for Scyld Cloud Workstation sessions

  • AWS support:
    • You can now select multiple Availability Zones for provisioning in pools, to support failing over to a different zone when the primary zone no longer has capacity to provision your selected instance size
    • Added support for Asia Pacific – Jakarta region

  • DCV support: The Connection Broker now instructs the Leostream Agent to close DCV sessions when the desktop is released from the user in Leostream - requires Leostream Agent 7.1.14 for Windows operating systems and Leostream Agent 5.2.12 for Linux operating systems

  • Azure support: You can now provision instances using images in an Azure Compute Gallery

  • Managing user identities
    • The Associated all user notifications with assigned user option in pools is now Associate initial user login with assigned user, and the Connection Broker acts upon only the events related to the first user identity that logs into the remote operating system after the desktop is assigned, ignoring events for all other users
    • Policies for hard-assigned desktops now include the Associate initial user login with assigned user option to allow the Connection Broker to manage sessions for hard-assign users who log into the remote operating system with a different user identity

  • leostream-broker CLI
    • The new --info option returns the Leostream environment information displayed on the > System > Maintenance page
    • The new --health option checks if system requirements related to CPU, RAM, and disk are met by the machine running the Connection Broker, as well as checks functional requirements related to if the leo user has sufficient sudo privileges and is able to run nmap

  • PIV card authentication: Supports OCSP for CA certification chains that include multiple CA certificates

Resolved Issues

  • The Connection Broker now confirms an Azure VM is stopped before attempting to deallocate it
  • Launching PCoIP connections from the Leostream web client no longer instantly expires the user’s Leostream session
  • The DCV External Authenticator can now be used in Protocol Plans for users who log into Leostream using a SAML-based Identity Provider
  • The Connection Broker now sends Wake-on-LAN packets to power on machines, as requested, regardless of the machines current power state in the Connection Broker
  • Resolves issues authenticating with PIV cards that contain multiple SAN entries or non-standard UPN formats
  • Regenerate Mechdyne TGX credentials before launching TGX connections, to handle cases where the encryption tool returns an error code on the first attempt
  • Recursively delete AD entries for Computer records that include a nested “Windows Virtual Machine” object, when deleting virtual machines based on Release Plans
  • Double-byte characters now display correctly on the Pool Statistics page

0 Votes