Skip to content

Releases: amidaware/tacticalrmm

Release v0.15.3

13 Nov 01:55
Compare
Choose a tag to compare

Release notes

  • Added #1294 Ability to bulk delete using client and site
  • Fixed #1250 Race condition causing windows agent update to sometimes fail
  • Fixed #25 Cleanup agent update temp files
  • Fixed slow dashboard loading when lots of pending actions in db
  • Various dependency updates

New Contributors

Full Changelog: v0.15.2...v0.15.3

Release v0.15.2

25 Oct 22:15
Compare
Choose a tag to compare
  • Fixed macOS agent silent mesh install bug
  • UI bug fixes

Full Changelog: v0.15.1...v0.15.2

Release v0.15.1

19 Oct 22:55
Compare
Choose a tag to compare

Release notes

  • Fixed #1293 Agent assigned Automation Policy - patch policy not used
  • Fixed #1298 Issues with improper escaping of certain characters in script snippets
  • Fixed #1210 Daphne websocket service sometimes failing to start
  • Fixed #1307 Harden cert file permissions
  • Fixed #1317 Quit early during install if error
  • Fixed #1314 URL color for the Microsoft Update KB link when in dark mode is very hard to read
  • Improved linux install script for better OS detection
  • Added optional setting to enable NATS monitoring
  • Various reworks and code optimizations
  • Updated to Python 3.10.8
  • Updated various dependencies

PR's

New Contributors

Full Changelog: v0.15.0...v0.15.1

Release v0.15.0

24 Sep 03:11
Compare
Choose a tag to compare
  • Initial release of the macOS agent (beta, same functionality as the linux agent)
  • Fixed #1283 Bug with Block Policy Inhiretance from Agent
  • Windows agent no longer sets AV exclusions during install

Full Changelog: v0.14.8...v0.15.0

Release v0.14.8

12 Sep 07:01
Compare
Choose a tag to compare
  • Fixed a bug where enabling maintenance mode and assigning a policy via the agent's context menu wasn't working.
  • Fixed #1270 logic error in windows updates installation function causing some agents to skip installing pending updates. Thank you @af7567 for finding the bug and submitting the PR with the fix.
  • Updated agent to allow for setting custom environment variables in the process of commands and scripts (this will be exposed in the Web UI/API in a future release).
  • Updated nats-server to v2.9.0
  • Updated MeshCentral to 1.0.85
  • Updated various dependencies

New Contributors

Full Changelog: v0.14.7...v0.14.8

Release v0.14.7

23 Aug 06:02
Compare
Choose a tag to compare
  • Added #652 The following data from the 'Summary' tab is now filtered in the Search field of the agent table: version, OS string, public IP, cpu model, graphics card, local ips, make/model and disk info.
  • Added #1246 Added a Copy to Clipboard button for every entry under the 'Assets' tab
  • Fixed #1177 All checks for a client disappear
  • Fixed #1145 Limited User can See "Policy Overview" from all Clients/Sites
  • Fixed #1171 Policies marked as linux applying to windows when they're checks
  • Fixed #1191 Global automation polices aren't applied to Linux agents
  • Updated to Python 3.10.6
  • Updated MeshCentral to 1.0.72

Full Changelog: v0.14.6...v0.14.7

Release v0.14.6

09 Aug 21:49
Compare
Choose a tag to compare
  • Fixed #1238 Run as User permission issues with temp dir. Also standardized the temp directory used by the agent for various tasks (running scripts, agent updates etc), all files will now be created in %PROGRAMDATA%\TacticalRMM so please make sure to update your AV exclusions (C:\ProgramData\TacticalRMM\*).
  • Fixed #1239 Fixed agent update when SELinux is enforcing.
  • Fixed #1174 (again) Issues with Reboot Later.
  • Update to Django 4.1

Release v0.14.5

01 Aug 23:02
Compare
Choose a tag to compare

0.14.5

  • Fixed Run As User not working for non-admin users (requires agent v2.2.1)

0.14.4

  • Added Run As User support for all methods of running commands and scripts (requires agent v2.2.0 and only supported on Windows workstations SKUs, not Server). A "Run As User" checkbox is now available throughout the UI when running commands and scripts. To make a script always run as user, check the "Run As User" checkbox in the Script Editor. Doing so will override any of the ad hoc "Run As User" checkboxes throughout the UI and force that script to always run in the context of the logged in user (do this for script check or tasks that need to run as user). See video below for a quick example:
run_as_user1.mp4

Release v0.14.4

01 Aug 18:24
Compare
Choose a tag to compare
  • Added Run As User support for all methods of running commands and scripts (requires agent v2.2.0 and only supported on Windows workstations SKUs, not Server). A "Run As User" checkbox is now available throughout the UI when running commands and scripts. To make a script always run as user, check the "Run As User" checkbox in the Script Editor. Doing so will override any of the ad hoc "Run As User" checkboxes throughout the UI and force that script to always run in the context of the logged in user (do this for script check or tasks that need to run as user). See video below for a quick example:
run_as_user1.mp4

Release v0.14.3

27 Jul 07:22
Compare
Choose a tag to compare
  • Fixed #1174 Setting a date in the past for "Reboot Later" would cause the agent to crash.
  • Fixed #1189 When editing a task, UI was not populating with the original datetime of the task.
  • Fixed #1193 Windows update patch policy off by one day, causing patches to be installed a day late.
  • Fixed a bug affecting script checks part of an automation policy where the cache was not being invalidated after editing the contents of the script, causing the agent to run the old script.
  • Added #1224 Include latest agent version in monitoring API endpoint.
  • Update MeshCentral to 1.0.60
  • Added the Nginx reuseport socket option to help with instances with high agent counts.
  • Switched to official Nginx repos to update Nginx from 1.18 to 1.22. Note: when running the update script you will receive a prompt that looks like the text below. Make sure you choose the default action (just press Enter or type 'N') to keep your current version.
Configuration file '/etc/nginx/nginx.conf'
 ==> Modified (by you or by a script) since installation.
 ==> Package distributor has shipped an updated version.
   What would you like to do about it ?  Your options are:
    Y or I  : install the package maintainer's version
    N or O  : keep your currently-installed version
      D     : show the differences between the versions
      Z     : start a shell to examine the situation
 The default action is to keep your current version.
*** nginx.conf (Y/I/N/O/D/Z) [default=N] ?

Note for those on Debian 10: the update script will fail and exit after trying to update nginx. Once it fails, please run the following and then run the update script again

sudo apt --fix-broken install
sudo apt upgrade

Full Changelog: v0.14.2...v0.14.3