Changelog
- Native File Browser: a fully native file browser with no MeshCentral dependency. Browse, create, rename and delete files and folders, upload and download with pause and resume, download folders as ZIP archives, and extract ZIP files directly on the agent. With the native terminal and now the file browser, we're just one release away from being fully off MeshCentral: the next release will include our own native remote desktop solution. See details and screenshots at the bottom. A video demo is available here: https://youtu.be/ufdXwdixurg
- The installer and restore scripts now support Debian 13 and Ubuntu 26.04. In-place OS upgrades are NOT supported, you must do a backup/restore. Please read the Operating System Support section below before upgrading your OS.
- The macOS agent is now signed with our Apple Developer ID. macOS privacy permissions such as Full Disk Access now stay granted when the agent updates, and you can pre-approve them for your fleet with a PPPC profile from your MDM. The Team ID, signing identifier and code requirement are in the documentation. Important: existing Mac agents will lose Full Disk Access and Accessibility once when they update to v2.12.0, and these need to be granted again (or pre-approved with a PPPC profile before updating), see the documentation.
- Server performance has been greatly improved. This lowers server load, especially on instances with a high number of agents or with lots of checks and tasks that run frequently.
- #2524 The agent History tab and the agent history API are now paginated. Previously, requesting the history of all agents could return the entire history table at once and run the server out of memory on large installs.
- Fixed an issue where the background workers (Celery) could hang and stop processing tasks.
- The monitoring status endpoint (
/core/v2/status/) now reports a Celery heartbeat (celery_heartbeat_age,celery_heartbeat_health), so you can alert when background tasks stop running. - Fixed the web interface not reconnecting its websocket after logging back in, which required a hard refresh of the browser.
- Fixed long output not scrolling in the Run Script and Test Script dialogs.
- Fixed characters typed quickly in the native terminal sometimes arriving out of order.
- The update script now upgrades Node.js to version 24 if your server is on version 20 or older. It also warns if your server is still running Debian 11, which is end of life.
- Updated MeshCentral to 1.3.1, a MeshCentral release with security fixes. Because of the way Tactical RMM integrates with MeshCentral, Tactical RMM instances should not be affected, but we still recommend updating as soon as you can.
- Various dependency updates.
Native File Browser
This release introduces a fully native file browser, built entirely on the Tactical RMM agent and web interface. It does not depend on MeshCentral, and it is around 3x faster than the legacy MeshCentral-based file browser. After the native terminal, this is the second of the three MeshCentral-backed features (terminal, file browser, remote desktop) to be reimplemented natively.
To open it: right-click an agent > Remote Background > File Browser.
- Browse, create, rename and delete files and folders, with sorting and a name filter.
- Upload files (including drag and drop) and download files, or whole folders as a ZIP archive.
- Extract ZIP files directly on the agent.
- Pause and resume transfers, even after a page refresh. Transfers recover on their own from network drops and server or agent restarts.
- Every file operation is recorded in the Audit Log.
Video Demo
Full details are in the File Browser documentation.
The native file browser requires agent version 2.12.0. Until an agent is updated, it will continue to use the legacy MeshCentral file browser.
File browser access is now controlled by a dedicated permission (Role > Agents > Use File Browser), separate from the previous "Use MeshCentral" permission. Existing users who had the "Use MeshCentral" permission have been automatically granted the new file browser permission. Newly created users will need to be explicitly granted file browser access in the permissions manager.
Operating System Support (Debian 13 and Ubuntu 26.04)
This release adds support for Debian 13 and Ubuntu 26.04. Please note, in-place OS upgrades are NOT supported. Upgrading the OS of an existing Tactical RMM server in place (for example with do-release-upgrade or by changing your apt sources) will break your installation.
The approved method for moving to a new OS is our backup and restore scripts: back up your current server, install a fresh Debian 13 or Ubuntu 26.04 server, and restore the backup onto it. This process has been designed to be seamless. Agents reconnect on their own once DNS points to the new server, so the downtime is just a few minutes. The backup/restore process also works across distributions and architectures, so you can, for example, back up a Debian server and restore it to Ubuntu (or the other way around), or back up an x86 server and restore it to an ARM (aarch64) server.
The backup script does not update itself, so please download the latest version before taking your backup. The restore script now supports Debian 13 and Ubuntu 26.04 only.
Please note that moving to a new OS is optional. Existing installations on Debian 11, 12 and Ubuntu 22.04 will continue to operate normally. If you don't wish to backup/restore to a new OS, you can treat this update like any other standard update and just run the update script as usual. If you are still on Debian 11, which is end of life, we strongly recommend planning a backup/restore to Debian 13 or Ubuntu 26.04.
NOTE: This update includes a new (v2.12.0) agent version. While extensive work has been done with antivirus vendors to reduce false positives, AV software is not perfect and the agent may still be flagged in some environments.
If you have not already set exclusions: to avoid potential issues, it is recommended to follow this process when updating:
- Before updating your instance, disable Automatic Agent Update: (Web UI: Settings > Global Settings > Enable agent automatic self update)
- Update your Tactical RMM instance as usual.
- Manually update a small number of agents (Web UI: Agents > Update Agents) and confirm they successfully update to agent version 2.12.0 (wait a few minutes after triggering the update and refresh the summary tab of the agent and check the version).
- Once confirmed, re-enable Automatic Agent Update from step 1.