Release Notes
Anyware Trusted Zero Client 25.03.5
Version 25.03.5 of the Trusted Zero Client is a maintenance release that replaces and deprecates 25.03.4.
Previous Releases in this Version
25.03.4
Version 25.03.4 of the Trusted Zero Client is a maintenance release that replaces and deprecates 25.03.3.
25.03.3
Version 25.03.3 of the Trusted Zero Client is a maintenance release that replaces and deprecates 25.03.2.
25.03.2
Note: 25.03.2 was the first public 25.03 release of the Trusted Zero Client. These release notes were previously published as 25.03.0, which was an error; the correct version number was 25.03.2.
Support for Multiple Audio Output Devices
Version 25.03 of the Trusted Zero Client introduces support for multiple audio output devices on the client side. You can now select multiple audio output devices for playing audio, in addition to a single audio input device while in session.
This capability is only supported on Linux clients and Trusted Zero Clients connecting to Windows Graphics agents or Windows Standard agents. For more information, see Selecting Multiple Audio Devices.
Support for Imprivata Authentication
Trusted Zero Client version 25.03 supports authentication of connections to Horizon hosts using Imprivata OneSign Single Sign-On. Imprivata OneSign enables users to access corporate networks, desktops, and applications with a single sign on. This reduces the need for maintaining separate passwords and prevents unauthorized access.
For more information, see Connecting Using Imprivata Authentication.
SIPR/NIPR Network Migration
In version 25.03, support has been added for securely migrating Trusted Zero Clients between SIPR, NIPR, and insecure networks. When re-commissioning a Trusted Zero Client for use on a SIPR/NIPR or insecure network, specific steps must be followed to completely erase all local data and configurations. This prevents accidental or malicious access to critical data during network migrations, and ensures compliance with security recommendations. A full set of instructions are available in Media Optimization for Zoom.
Introducing Zoom VDI for HP Anyware
Version 25.03 of the Trusted Zero Client introduces support for Zoom VDI when connected to Windows Agents. The feature works the same as Omnissa Horizon Agents by offloading the audio and video streams from HP Anyware agent devices to HP Anyware client devices, which handle the processing and transmitting of these streams to and from Zoom servers. This results in reduced latency, and improved meeting experience during PCoIP sessions.
Once installed and configured on the Anyware Windows Agent, the capabilities of Zoom VDI enable quick adoption, leading to a seamless experience while starting and joining meetings. The Zoom VDI Plugin is similar to the Standard Zoom Client, and includes features such as optional end-to-end encryption, gallery view, speaker view, language interpretation, breakout rooms, and screen sharing. For more information, see Media Optimization for Zoom.
Support for Wi-Fi Networks
Trusted Zero Client can now connect to Wi-Fi Protected Access 2 (WPA2) networks using password authentication. This facilitates access from places where wired networks are unavailable, and permits the mobility of Trusted Zero Clients across networks. For the purpose of enabling Wi-Fi use, new menu options have been introduced in the client interface. These menu options are described in the Settings topic.
Support for Xencelabs Pen Displays
Version 25.03 of the Trusted Zero Client supports Xencelabs Pen Display 16 and Xencelabs Pen Display 24 while connecting to Windows Graphics or Standard agents. Support is available in the locally terminated mode, as well as the bridged mode. For more information, see Supported Xencelabs Pen Displays.
Info:
This feature is currently in beta, and may be subject to future changes or may contain bugs.
Other Updates
Previously, the Trusted Zero Client connected to Anyware Trust Center on TCP port 32443. Going ahead, it will connect on TCP port 443.
Fixed Amazon Workspace Connectivity Issue
Amazon Workspaces was throwing an error due to a slash (/) in the Desktop Resource ID. This has been resolved.