Release Notes
Anyware Connector (RHEL and Rocky Linux) 25.03.0
Version 25.03.0 of the Anyware Connector (RHEL/Rocky Linux) contains bug fixes and stability enhancements. Additionally, the following new features are supported:
Menu-driven Configuration for Connectors
Version 25.03 of Anyware Connector (RHEL) improves the menu-driven configuration for Connector management. This version enables bidirectional communication, where each tab reflects the current settings of all associated services upon selection.
Note:
This release offers only a few capabilities; additional capabilities will be added in future releases.
Issue with certificate configuration
Anyware Connector is incorrectly configuring Anyware Manager Installable certificate causing certain containers (ADSync, RWTelemetry, Healthstatus) to fail to communicate with Anyware Manager Installable. You can disable Anyware Manager Installable certificate validation on the connector with:
--manager-insecure
The certificate validation configuration has been fixed.
Changed permissions for service accounts
New functionality (Configuration Service) added to AWM/AWC requires additional permissions that were not available to the older versions. Upgrading Connector causes issues due to the incorrect permissions. Manually rotating Connector's service account resolves this issue.
Addressed SG User Disconnects
Fixed an intermittent issue that caused security gateway to crash and terminate active PCoIP connections
"tar" not included in some versions of Rocky linux
Due to the fact that Boot and Minimal ISO images for Rocky 9.* does not include tar package (unlike versions 8.* that did). Some customers experienced issues as Anyware Connector could not produce a support bundle file. Customers who installed DVD ISO (for example) were not affected. In future versions of Anyware Connector, if tar is missing on the host system shall be installed automatically during Connector installation.
Some pods fail to start
An issue in 24.07.3 was preventing the broker and the connection manager pods from starting. The issue was fixed in 24.07.4
Issues with Generating Support Bundles
Because Boot and Minimal ISO images on Rocky Linux 9 do not include the TAR package (unlike version 8), some customers will encounter issues, since Anyware Connector will not be able to generate support bundles. Customers who install DVD ISO (for example) will not be affected.
- To fix this issue, run the following command:
dnf install tar -y
In future versions, if the TAR package is missing on the host system, it will be installed automatically during installation.
In-place Upgrade Issues for Pre-Configuration Service Connectors
In-place upgrades of Anyware Connector installed before the Configuration Service was added prevent the activation of the Configuration Service. This happens because the service account associated with the Connector does not have the required privileges. In this scenario, you have two options:
- Disable the Push configuration service by running the following command:
anyware-connector configure -enable-configuration-service=false - Recreate the AWM Service account by getting a new Connector token:
anyware-connector configure --token
After recreating the account, you should be able to activate and use the Configuration Service without any issues.