Release Notes
Anyware Trust Center 23.12.1
Release 23.12.1 of the Anyware Trust Center is a maintenance release which replaces and deprecates 23.12.
It includes the following:
- Bug fixes and security updates.
Previous release information:
Release 23.12 of the Anyware Trust Center includes the following:
Endpoint Maximum Increased
Performance improvements in 23.12 allow the Anyware Trust Center to support 5,000 endpoints (previously, the maximum was 1,000).
Minimum Requirements Lowered
Performance improvements also allow the Anyware Trust Center to use half the previous vCPU and RAM specification; the Anyware Trust Center now requires at least 4 vCPUs and 16GB of RAM (previously, the minimum was 8 vCPUs and 32GB of RAM). See System Requirements for more information.
New Device Timeout Policy
You can now set a policy for the length of time that a Trusted Zero Client can remain disconnected from a Anyware Trust Center before it becomes untrusted.
Vault Health status correctly being reported
Previously the diagnose command was erroneously showing Vault health status as unhealthy. The diagnose command was updated to correctly collect and report the Vault health status. It will now show Vault as healthy (when it's healthy).
Improved installation resliency
Resolved a somewhat rare case where the Trust Center activitylog service was not initializing in-time for the liveness/readiness probes to succeed causing installation to fail.
Trusted Zero Client OTA Updates Enabled by Default
In 23.08, the enableSync property in the config.yaml file was being set to "false", disabling OTA update syncing. In the 23.12 release, OTA updates syncing is set to "true" by default.
Any existing Trust Center 23.08 installations where enableSync was set to "false" must be updated manually to set the value to "true". This value will not automatically be changed when upgrading to 23.12. You must edit the config.yaml file and change the property endpointUpdate/enableSync to "true". Running an upgrade will apply the setting: sudo ./trust-center-ctl upgrade
Anyware Trust Center not responsive after changing hostname
Currently if the hostname of the machine which the Anyware Trust Center is installed upon changes after installation, the Trust Center will not start properly.
In order to avoid this issue, a fixed/persistent hostname needs to be set on the machine before installing the Anyware Trust Center. This prevents this issue from potentially being encountered on subsequent reboots of the machine.
In order to configure this, simply run the following command before installing the Trust Center:
hostnamectl set-hostname <desired hostname>
This hostname can be anything but is usually set to the machine's DNS name on the local network.