Remote Support 25.1.1 release notes
12 days ago by Jenny
April 3, 2025
Requirements
- Requires Base 7.4.0.
- Requires ECM 1.6.2.
- Requires Integration Client 1.7.3.
- Supports upgrades from RS 24.2.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.
New features and enhancements
-
Endpoint automation enhancements
-
PowerShell scripts now default to "-ExecutionPolicy Unrestricted".
-
Tags have been added to jobs, allowing you to filter by tag from the main Jobs page.
-
Jobs can now be archived using the Hide option.
-
-
Dashboard enhancements:
-
A secondary session details window now appears when a user clicks on a session ID from the session list.
-
The dashboard is now available for on-premises sites.
-
The Session Details Properties table now displays the time the first representative joins a session.
-
-
Admins can now download or email Jump Clients from the Jump Client installer listing, making deployment easier.
-
SHA-256 checksums are now displayed in the Session Details report for transferred files, allowing for easy verification against standard hash tools.
-
The name of the credential used to initiate a Jump Item session is now displayed, making it easier to track and reuse credentials for subsequent sessions.
-
Installed application patches are now displayed on the Status page, providing visibility into applied updates.
Issues resolved
| Product Area | Description | Resolution |
|---|---|---|
| Administrative interface | ||
| Reporting | Deleted vendor groups did not appear in reports, leading to missing data. | The reporting system now correctly displays deleted vendor groups. |
| Reporting | Some exit survey questions were not being properly stored, preventing results from being displayed. | Exit survey responses are now properly handled to allow for data retrieval. |
| API | Increased the API version to 1.25.0. | |
| API | Corrected several issues with attributes in the following Configuration APIs:
| |
| API | Added three status codes to the Failover Command API:
| |
| API | Some links to OAuth authentication information in the integrated Configuration API documentation were outdated. | Updated the links in openapi.yaml and /login/apidocs.html to ensure they point to the correct information. |
| API | The start_session API did not work correctly when called from a different origin than the appliance domain. | Updated the API to handle cross-origin requests properly, allowing sessions to start successfully even when initiated from a different domain. |
| Support Portal | It was unclear that users were interacting with a trial version of the software, which could lead to confusion or misuse. | Now, a notice appears on the public portal, making it clear that the site is a trial version. This improves transparency and security. |
| Support Portal | The "Describe Your Issue" text field had no character limit, allowing users to enter excessive amounts of text and causing errors when submitting a support request. | Now, the "Describe Your Issue" text field has a 1024 character limit to prevent errors, ensuring smoother functionality on the support portal. |
| Support Portal | The Name Prompt field in the Click-to-Chat section was not allowing edits. | Users can now successfully edit the Name Prompt in the Click-to-Chat section. |
| Support Portal | All exit survey questions were displayed, even those that were excluded from the Displayed Questions section. | Now, only questions designated as Displayed Questions appear in the exit survey. |
| Dashboard | Users could accidentally overwrite the access key by copying it first and then copying the dashboard URL, requiring the key to be regenerated. | The Copy button was removed from the Dashboard URL to improve the process and mitigate this issue. |
| Pathfinder | The URL for mobile device downloads was not redirecting correctly, causing a 404 error when trying to install the Jump Client on Android devices. | The issue was resolved by ensuring the correct redirection to the site hostname, allowing the Jump Client to install without errors. |
| Pathfinder | The SAML groups were not being parsed correctly when the groups came across in the downlevel format (Domain\Username), causing the backslash character to be ignored and the group to display incorrectly. | The issue was resolved by ensuring the backslash character is properly escaped, allowing the group to display as intended. |
| Atlas | The web rep console experienced slowness when connected to traffic nodes. | The connection handling to traffic nodes was optimized, improving performance and reducing lag. |
| Atlas | Traffic node hostnames were being changed after upgrading or reinstalling version 24.3.1 on Cloud Atlas sites, altering the original traffic node names. | The process was updated to preserve the traffic node names during upgrades or re-installs, ensuring the correct hostnames are maintained. |
| Atlas | Intermittent data sync failures could occur across traffic nodes when multiple primary nodes were used. | A networking issue was resolved, which corrected the data sync failures. |
| Text Updates | The "Start the Shell" button in the web rep console was inconsistent with the other buttons. | The button has been updated to "Start Shell". |
| Text Updates | The Configuration API documentation lacked details on which fields must be unique within each object or API endpoint. | The Config API documentation has been updated to specify which fields are required to be unique, clarifying the schema for both users and automated tests. |
| Text Updates | The help text in the tooltips on the Jumpoint creation screen was unclear. | Tooltips on the Jumpoint creation screen were updated for clarity. |
| Text Updates | The help text in the tooltip for Restrict Local Uninstall/Disable of Jump Clients was unclear. | The tooltip for the setting has been updated for clarity. |
| What's New | The What's New section in the administrative interface now points to the release notes page at docs.beyondtrust.com. | |
| Clients | ||
| Rep Console | When joining a shared Shell Jump session, invited representatives saw the OS icon instead of the Shell Jump icon in the queues tab of the representative console. | Now, the correct Shell Jump icon displays for all representatives. |
| Rep Console | If a representative started a screen-sharing session with app sharing enabled and restricted apps blacked out, logging into the same representative account on another computer caused all restrictions to be removed. | App sharing restrictions now remain in place when the representative logs in from another computer. |
| Rep Console | The comments field in the Invite External Rep window allowed more than 256 characters to be entered but then displayed an error upon submission. | Now, the field enforces the 256-character limit while typing. |
| Rep Console | When logging into the desktop representative console, rep invite keys containing spaces would cause authentication to fail. | Now, spaces in rep invite keys are ignored during authentication. |
| Rep Console | The What's New section in the representative console now points to the release notes page at docs.beyondtrust.com. | |
| Click-To-Chat | The Close button in the click-to-chat window did not have an ARIA label to describe its function. | The button now includes an ARIA label attribute to improve accessibility. |
| Support Button | The Embedded Support Button feature is being deprecated in preparation for integrating callback button functionality into the Jump Client. It will be removed in a future release. | |
| Shell Jump | When transferring files during a Shell Jump session, if a file was successfully transferred to the remote system but the same transfer was attempted again and canceled when prompted to overwrite, the file would be deleted from the remote system. | Canceled file transfers no longer result in the deletion of previously transferred files on the remote system. |
| RDP | When using the "Use all my display sizes" setting during an RDP session on a system with multiple displays, white space appeared on smaller monitors when clicking "View All". | Smaller monitors no longer display white space when the "View All" button is clicked during a multi-monitor RDP session. |
| Linux | Clicking the Key icon to bring up the credential window could cause the representative console to freeze or fail to load the window properly on Ubuntu 24.04. | The credential window now loads properly without freezing the representative console on Ubuntu 24.04. |