Privileged Remote Access 24.3.3 release notes
about 17 hours ago by Jenny
March 11, 2025
Requirements
- Requires Base 7.3.0.
- Requires ECM 1.6.2.
- Requires Integration Client 1.7.5.
- Supports upgrades from PRA 23.3.4++.
- Before upgrading, ensure any SSL certificates used are either from a trusted Certificate Authority, or, for self-signed certificates, the certificate is either trusted on all endpoints or explicitly included in their installation.
Issues resolved
| Product Area | Description | Resolution |
|---|---|---|
| Jump Clients | Remote agents did not use the secondary fully qualified domain name (FQDN) after upgrading, causing Jump Client upgrade failures for some customers. | The upgrade process now correctly maps to the customer-specified client addresses, ensuring that Jump Clients will try both primary and secondary after upgrading. |
| Jump Clients | Jump Clients uninstalled themselves if they had not connected within 180 days of installation. | Jump Clients now respect the configured offline and lost status durations, preventing unintended uninstalls when the Jump Client has been offline for an extended period. |
| SSH | The SSH fallback method only handled mismatches in four parts of the SSH negotiation, preventing connections to some older devices. | The SSH fallback method now includes client/server encryption and server/client encryption, improving compatibility with older devices. |
| Network | IPv4 subnet masks were incorrectly generated for certain prefix lengths due to how the mask was stored in network order. | The code now creates the subnet mask in host order before converting it to network order, ensuring accurate mask generation. |
| API | The reporting.xsd and command.xsd schemas did not match API responses, causing validation failures in XML validators. | The schemas have been corrected to align with API responses and now pass validation checks without errors. |
| Endpoint Automation | Endpoint Automation did not work with a Jump Proxy, always attempting to run directly instead of routing through the proxy. | Endpoint Automation now correctly uses the Jump Proxy by passing its address to the script execution utility, ensuring resources are downloaded and results are communicated through the proxy. |
| Access console | The console user field for the endpoint client displayed the full name instead of the account name. | The console user field now consistently displays the account name. |
| RDP Jump | FreeRDP 3.8 contained issues that needed to be addressed in a follow-up release. | Upgraded FreeRDP to 3.10.3, which includes fixes for some issues, including Windows 11 display artifacts. |