Release Notes
Anyware Trusted Zero Client 25.06.0
Release 25.06 of the Trusted Zero Client contains bug fixes and stability enhancements. Additionally, it also includes the following new features:
Support for Imprivata OneSign Virtual Channel
Version 25.06 of the Trusted Zero Client introduces support for Imprivata OneSign virtual channels, which enables a seamless and secure authentication experience for users connecting to Omnissa Horizon remote sessions.
Virtual channels allow users to use their proximity cards to do the following:
- Authenticate Trusted Zero Clients connecting to Omnissa Horizon hosts,
- Initiate Single Sign-On (SSO) within their remote sessions,
- Unlock or disconnect their sessions, and
- Seamlessly log on to multiple workstations and resume their sessions without re-entering credentials.
This results in a fast, secure, and frictionless authentication experience, making it ideal for environments where speed, security, and mobility are crucial. For more details about this feature, see Imprivata OneSign Virtual Channel Support.
Keyboard Configuration Settings
Version 25.06 introduces Keyboard Configuration options in the Settings menu, which enable users to personalize their typing experience. These settings optimize keyboard responsiveness and adjust keyboard behavior to match individual typing style and preferences. For more information, see Keyboard Configuration.
Notifications for Scheduled Power Events
In version 25.06, support has been added for notifications in event of scheduled reboot of Trusted Zero clients. Previously, scheduled reboots were not accompanied by notifications, resulting in abrupt interruption of user work. Now, a warning will appear up to 5 minutes before reboot, giving users time to save their work.
Optional Connectivity for Trusted Zero Clients
Version 25.06 now supports using Trusted Zero Clients without a Trust Center connection, making it ideal for proof-of-concepts, evaluations, and air-gapped minimal environments. In this scenario, Trusted Zero clients will operate with a reduced feature set, and connections to hosts will only be secured by the PCoIP protocol. The Trust Center is required if remote management, observability, end-to-end trust, and security policy enforcement is desired. The ability to connect to Trust Center is fully controlled on Trusted Zero clients. For more information, see the Trusted Zero Client guide.
Info:
Trusted Zero Clients are updated using the over-the-air (OTA) updates sent by the Trust Center they are connected to. If a Trusted Zero Client is not registered to a Trust Center, OTA updates will not be available. As a result, Trusted Zero Clients cannot be updated.
Support for Additional Wacom Tablets
Version 25.06 of the Linux Anyware Client now supports the following Wacom tablets:
- Intuos Pro Small
- Intuos Pro Medium
- Intuos Pro Large
For more details, see Wacom Tablet Support.
Support for Xencelabs Pen Tablet Medium V2
In version 25.06, support for Xencelabs Pen Tablet Medium V2 has been added to Anyware Clients connecting to Windows Graphics agents. This support is available in the locally terminated mode, as well as the bridged mode.
Additional information is available in Supported Xencelabs Pen Displays.
Support for In-session Localization
Previously, localization was only available for pre-session display. In version 25.06 of the Trusted Zero Client, support for localization of the in-session menu bar during active PCoIP sessions has been introduced. UI elements will be displayed in the language selected in the Settings menu prior to commencement of a session. For more information, see Language Support.
Info:
At present, the in-session menu is displayed in English because it does not yet support Chinese, Japanese, or Korean characters. This issue will be fixed in an upcoming release.
Media Optimization Improvements
In version 25.06, several improvements have been added to the Media Optimization feature. They include streamlining the process for the following:
- Enabling Media Optimization for Zoom
- Creating and joining Zoom meetings
This enhances the video conferencing performance during remote sessions.
Improvements to the Multiple Audio Device Feature
Previously, if multiple audio devices were connected to a Trusted Zero Client, only one could be selected as an input. In version 25.06, up to three input devices can be selected after a PCoIP session has been established.
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.
Trusted Zero Client Rejected Previously Valid Certificates
Certificate validation has been fixed to correctly validate certificates that were incorrectly identified as invalid by Trusted Zero Client 25.03.2.
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.
Custom Certificate Chain Validation Issue in Trusted Zero Client 25.03.1
Trusted Zero Client 25.03.1 failed to validate certain custom certificate chains that had previously been validated. This issue has now been fixed.
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.
Session Connection no longer fails when Certificate Serial Number is 0
25.03.1 Anyware Clients, Trusted Zero clients, and Agents will now accept a broker certificates where a certificate in the chain contains Serial Number 0 (zero). This fixes a problem where connections using these certificates would fail during session establishment.
Skipping Trust Center FQDN During Initial Setup
Users can now skip adding a Trust Center FQDN during initial setup and enter this information later. This helps facilitate PoCs and Demos of Trusted Zero Clients before setting up a Trust Center.
The user receives a security warning message before skipping the step. Customers who do not want users to skip this step can set up the anywaretrustcenter CNAME on their LAN. When this CNAME is configured, the Skip Step button will not be displayed to the end user, and the Trusted Zero Client will automatically register with your local Trust Center.
More information on setting up Automatic Anyware Trust Center discover can be found on the following pages:
- Internet Connected setup: https://anyware.hp.com/web-help/trusted-endpoints/trust-center/25.06/installation/installation-single-node/#3-create-dns-records
- Darksite setup: https://anyware.hp.com/web-help/trusted-endpoints/trust-center/25.06/installation/installation-single-darksite/#step-v-create-dns-records
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.
Wacom Tablets can be connected to the remote session using one of two modes: Tablet Performance (the default), which provides highly responsive performance and better tolerance of high-latency networks, and LAN Connect, which is less performant and susceptible to latency issues, but may provide support for additional features such as force touch.
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.
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.
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.