(12/13/22): Leostream Platform Update

Component Updates 

• Leostream Agent 7.4.23 for Windows operating systems – Returns the public and local hostnames for AWS instances to the metadata returned to the Connection Broker
• Leostream Agent 5.2.23 for Linux and macOS operating systems – Returns the public and local hostnames for AWS instances to the metadata returned to the Connection Broker
• Leostream Connect 3.8.5 for Linux and macOS operating systems – Opens the Remote Boost authentication dialog when the Leostream protocol plan does not specify a username for the connection

Leostream Platform December 2022 Update: 

Connection Broker 2022.1.3 

Features 

• The TGX encryption tool has been updated to version 2022.1.4
• Minor enhancements when defining multiple SAML-based authentication servers using tenants
• Store the public and local hostname for AWS instances when returned by the Leostream Agent
• New dynamic tags {HOSTNAME_PRIVATE} and {HOSTNAME_PUBLIC} for use in Leostream Protocol Plans
• Support Standard NVadsA10v5-series instance size in Pools when provisioning into an Azure Center
• Prepend the PCoIP device IP address to syslog messages received by the Connection Broker prior to relaying them to an external syslog server specified in the PCoIP Devices Center Resolved Issues
  
  

Resolved Issues

• Properly handle cases where users enter incorrect passwords into a PCoIP Software client that is launched from the Leostream Web client
• For Leostream environments that have reached their license limit, users with an existing Leostream license are no longer blocked from logging in when their policy enables the Prompt user for alternate credentials before connecting to selected desktop option and they launch the PCoIP client from the Leostream Web client
• Properly release desktops that are forcefully shutdown before the Leostream Agent is able to register the shutdown with the Connection Broker, for example when using the Power off power control option
• Allow Printer Plans to be deleted when they are currently assigned to a Location or specific Client
• Removed support for the if_assigned_only parameter for the cb_status Web query
• Improve handling of center scans that run while there are active provisioning jobs, to avoid removing desktop records associated with virtual machines that are still being created
• Resolve cases where provisioning jobs for virtual machines on Scale Computing HC3 resulted in duplicate desktop records
• Paginate inventory of images from OpenStack centers to handle cases where the OpenStack project has more than 25 images
• Properly log out rogue users that are connected to desktops using HP ZCentral Remote Boost (RGS) based on the Policy option to log out rogue users
• Change desktop power statuses to Stopped for desktops marked as Stopping when a Center scan occurs and confirms that the desktop is powered off
• Improve disconnect logic for PCoIP Remote Workstation Cards to attempt to disconnect the PCoIP session from the Remote Workstation Card if the PCoIP client cannot be disconnected
• Pass the region to the AWS API when checking if an AWS center is online
• Properly fail over to the second value for dynamic tags that use the or syntax and reference hostnames or IP addresses, for example IP_PUBLIC-or-IP
• Resolved permission errors when trying to send Leostream log messages to a syslog server

Leostream 9.1 Revision 8:

Important Notes

•  The {IP_PRIVATE} dynamic tag is now strictly replaced by the IP address found in the IP Address (Private) column on the > Resources > Desktops page. If that field is empty, the {IP_PRIVATE} tag is replaced with an empty string. Prior to this release, the {IP_PRIVATE} field was replaced with the value in the IP Address field when there was no private IP address. If you leverage the {IP_PRIVATE} dynamic tag in your protocol plans and use those protocol plans to connect users to on-premises virtual machines, update your protocol plans to use the {IP_PRIVATE-or-IP_ADDRESS} or {IP_ADDRESS} dynamic tag.
• 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.33

Features

• Store the public and local hostname for AWS instances when returned by the Leostream Agent
• New dynamic tags {HOSTNAME_PRIVATE} and {HOSTNAME_PUBLIC} for use in Leostream Protocol Plans

Resolved Issues

• Properly handle cases where users enter incorrect passwords into a PCoIP Software client that is launched from the Leostream Web client
• For Leostream environments that have reached their license limit, users with an existing Leostream license are no longer blocked from logging in when their policy enables the Prompt user for alternate credentials before connecting to selected desktop option and they launch the PCoIP client from the Leostream Web client
• Properly release desktops that are forcefully shutdown before the Leostream Agent is able to register the shutdown with the Connection Broker, for example when using the Power off power control option 
• Allow Printer Plans to be deleted when they are currently assigned to a Location or specific Client 
• Removed support for the if_assigned_only parameter for the cb_status Web query

0 Votes