Changelog
- Native Terminal: a fully native terminal with no MeshCentral dependency, configurable global and per-agent shell defaults, on-the-fly shell switching, and run-as system/user support. See details and screenshots at the bottom. A short video demo is available here: https://youtu.be/ZZfnmpldL4Q
- The agent recovery functions now perform a complete unattended reinstall/recovery, which is especially helpful in cases where an agent has been removed due to Antivirus false positives. amidaware/rmmagent#27
- Added rate limiting protection for login endpoints to help prevent brute-force attacks; see the documentation for configuration details, troubleshooting, and monitoring current rate limit status.
- Fixed a bug in the registry editor where large registry entries could fail to load or display correctly.
- #2440 Fixed an issue preventing the agent from installing on Apple M5 Macs.
- Fixed the Send Command "Live Stream" mode so commands run as the selected user (when "Run As User" is enabled) instead of running as SYSTEM.
- "Run as User" on Windows now uses the user’s elevated admin context when available, so commands, scripts, and terminal sessions no longer run with the user’s limited permissions even if they are a local administrator.
- Fixed several underlying issues in the Alerts Manager, including a case where tasks configured to run on check failure would not execute.
- #2388 #2478 Fixed a regression from the previous release where the agent hostname was missing from the subject of resolved alert emails.
- Windows Update schedules now install manually approved patches even when auto-approval is disabled.
- Updated the bundled portable Python on Windows to version 3.14.5
- Added search to the Manual Agent Update dialog to quickly filter the agent list.
- Fixed several edge cases affecting Linux agent installation.
- MeshCentral updated to 1.2.0
- Various dependency updates.
Native Terminal
This release introduces a fully native terminal, built entirely on the Tactical RMM agent and web interface. It does not depend on MeshCentral. This is the first of the three MeshCentral-backed features (terminal, file browser, remote desktop) to be reimplemented natively, with the other two to follow in future releases.
Global shell defaults can now be configured under Global Settings > General, applied to all agents:
- Windows: CMD, PowerShell, or a custom shell specified by full path (e.g. C:\Program Files\PowerShell\7\pwsh.exe)
- Linux: Bash or a custom shell (e.g. /usr/bin/fish)
- macOS: zsh/bash or a custom shell (e.g. /bin/zsh)
Individual agents inherit the global default but can be overridden under the agent's edit settings, allowing a different shell per agent:
Within an active session, the shell can be switched between CMD, PowerShell, and Custom without reconnecting. The Edit Path option allows pointing at any interpreter on the fly, such as PowerShell 7 or a Python interpreter. Sessions can also run as either the local system account or the logged-in user.
The native terminal requires agent version 2.11.0. Until the agent is updated, it will continue to use the legacy terminal.
Terminal access is now controlled by a dedicated permission (Role > Agents > Use Terminal), separate from the previous "Use MeshCentral" permission. Existing users who had the "Use MeshCentral" permission have been automatically granted the new terminal permission. Newly created users will need to be explicitly granted terminal access in the permissions manager.
**NOTE**: This update includes a new (v2.11.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.11.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.