Release Notes
Anyware Trust Center 25.06.0
Release 25.06 of the Anyware Trust Center contains bug fixes and stability enhancements. Additionally, it also includes the following:
Darksite Downloads Now Available Through Two IP Addresses
Previously, darksite bundles were downloaded via dl.anyware.hp.com and utilized the global Content Delivery Network (CDN), requiring multiple IP addresses to be allowlisted. With version 25.03.5, darksite bundles will be downloaded through the prod.onboarding.hydra.teradici.com subdomain. This change simplifies allowlisting, as only the following two US-based IP addresses are now required:
- 166.117.189.248
- 166.117.55.125
Non-darksite (internet connected) installations continue to use the CDN, benefiting from its capabilities of supporting regionally distributed downloads. For more information, see Updating the config.yaml file.
Support for Manual Renewal of Registration Certificates
Version 25.06 of the Anyware Trust Center introduces support for manual renewal of registration certificates. This manual process is necessary if your Trust Center is installed in a darksite, or cannot utilize the automatic renewal mechanism. In the absence of a manual renewal process, Trust Center installed in darksite environments would become invalid. The ability to manually renew registration certificates ensures these Trust Center deployments stay both functional and secure.
For more information, see the Manually Renew the Trust Center Registration Certificate topic.
Support for Automatic Renewal of Registration Certificates
With version 25.06, Anyware Trust Center now automatically renews registration certificates. If Anyware Trust Center is internet-connected, registration certificates are renewed automatically 60 days before they expire. This ensures Trust Center deployments stay functional, without service interruptions.
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 Trusted Zero Clients connecting 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 from the Settings menu of the Trusted Desktop clients. For more information, see the Trusted Desktop Client guide.
Service Accounts documentation update
The API documentation has been updated to include additional information (username, etc), that is returned when a Service Account is created.
Improved installation process for fapolicy
Previously, when fapolicies were enabled on the latest versions of RHEL and Rocky Linux, services needed to be manually restarted for changes to take effect. The Trust Center installer now automatically restarts the necessary services during installation, so users no longer need to perform this step manually.
Corrected date-time format in API documentation
Previously, the API documentation referenced ISO8601 timestamps and provided ISO8601 examples for properties using the openapi date-time format. This was inconsistent with the OpenAPI specification, which requires RFC3339 section 5.6 timestamps. The documentation has been updated to reference RFC3339 and now provides RFC3339-compliant examples. Property validation has also been updated to accept only RFC3339 timestamps for date-time format fields.
Some Reported properties were not updated when Desired/Default properties were deleted. This is now resolved.
Anyware Trust Center Is Unresponsive After Hostname Change
If the hostname of the machine on which the Anyware Trust Center is installed changes after installation, the Trust Center will not start properly.