Release Notes
Anyware Trusted Zero Client 25.03.3
Version 25.03.3 of the Trusted Zero Client is a maintenance release that replaces and deprecates 25.03.2.
Previous Releases in this Version
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.
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.
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.
WiFi Access Point info not reported back when configured from TC
Configuring WiFi from the Trust Center would not always update the reported properties back from the Client, making it appear that the settings were inconsistently applied.
Enhanced error message feedback during Kiosk mode setup
Previously, when an empty broker list was set from the Trust Center and a Trusted Zero Client was configured in kiosk mode, clicking the retry button to attempt to connect to a non-existant broker caused the kiosk page to spin indefinitely without displaying the error again to inform the user of the misconfiguration. This issue has been resolved. The error message now reappears if no brokers are set, ensuring users are always informed that an issue persists.
OAuth window now pops up on primary display
Previously, when multiple displays were connected, an OAuth window would pop up on a non-primary display. This has been changed to ensure the window always pops up where the user is most likely gazing.
Fixed an Arrange Displays limitation
When a secondary monitor had a different resolution than the primary, it could not be moved to the left side of the primary monitor. This has been resolved.
Audio enforcement update
When enforcing what audio device to be used on a Trusted Zero Client, the Client Settings UI made it appear that the user could still change the audio settings. The form is now disabled when the settings are enforced by the Trust Center.
Horizon MFA prompt text missing
Some MFA providers provide a description of what the user can enter into the MFA input box. This was missing on Horizon login flows, so has been added. The user will now receive information about what they can enter in the input field, such as "push", "phone", "sms", etc.
Username cached when enforced by the Trust Center
When the "remember username" setting was enforced by the Trust Center, Trusted Zero Clients did not retain the username on the login screen—despite the “Remember my username” checkbox appearing to be selected. When Connections (Brokers) were set by the user or set as Defaults by the Trust Center, "remember username" worked fine. Users will now see their previously entered username pre-filled on the login screen when this option is enforced from the Trust Center.
Added support for Wacom tablets
DTH-227 and DTH-172 are now supported for "Tablet Performance" on the Trusted Zero Client.
NOTE for PE: The same documentation changes made in [https://hp-jira.external.hp.com/browse/TSW-245715] need to be made on [https://anyware.hp.com/web-help/trusted-endpoints/trusted-zero-client/25.06/features/usb/wacom/] and [https://anyware.hp.com/web-help/trusted-endpoints/trusted-zero-client/25.06/features/usb/xencelabs-support/] pages.
Imprivata reset pin not functioning
When the PIN on an Imprivata proximity card expires, the PIN reset form displays a backend error without providing a failure reason to the end user. A fix is in development.
Some components not adhering to log-level set
When log level was set on a Trusted Zero Client, some components would always log at a debug level. The UI and Trust Agent logs now respect the log level set by the user. We are leaving session logging as debug for now as this does not impact performance and GSS will always require "level 3" logs if a support ticket is opened.
Arrange Displays UI does not always show all monitors
Fixed an issue when using three or more 4k monitors, not all the monitors fit within the Arrange Displays UI. The UI now dynamically adjusts the preview of each monitor so that they fit within the viewport.
Fix for Network Settings Config tab reverting to manual instead of automatic
Previously, when disabling either the IPv4 or IPv6 protocol, the default "Config Type" would change to "Manual" instead of "Automatic" (static vs DHCP). Automatic is the preferred default.
Changing the primary monitor now causes the UI to switch screens
Previously when changing a monitor to be the primary, it was not obvious that this resulted in a change as the UI would stay on the same monitor. When entering a session, the desktops were arranged as expected. Now when the primary monitor is changed, the UI will switch to that monitor, as well.
Sometimes an incorrect Error message is displayed during authentication
During the authentication process, if an error is thrown with a localized message, the UI would sometimes present the previous error message. This issue is resolved.
Smart Card SSL Errors Handled Properly
Resolved an issue when an SSL Error is thrown from the Smart Card authentication flow, where the error would flash on the screen and then redirect the user to the Connection page. The error message now waits for the user to click OK to confirm they understand that an error occurred.
Collaboration works differently on TZC as compared to the Desktop Client
The Collaboration feature only works in-session with a Anyware Client. That is why to establish a collaboration session from a Trusted Zero Client, you must first install Anyware Client on the Anyware Agent you are connecting to.