Updates & upgrades
Already running TechSavve RMM? Move to the newest version in a few minutes. You run the new installer over the old one: your data, settings and certificate stay.
The newest version: 1.3.3
Released 2026-10-28. You can go straight to it from any earlier version; the versions in between don’t need installing first.
Windows
The same download as a new installation. Run it on the computer TechSavve RMM is installed on.
Linux
The same download as a new installation. Copy it to the server TechSavve RMM is installed on.
The download asks for your name, email and phone, like the Download page. · SHA256SUMS
Which version am I on?
Any of these shows it:
- In TechSavve RMM, under the menu on the left: Version 1.3.2, for example.
- Admin → License, on the Version line.
- Your server’s address followed by
/health?format=json(for examplehttps://rmm.yourcompany.com/health?format=json) shows"version".
Before you start
Take a full backup. In TechSavve RMM, open Admin → Backup & Restore. Under Full backups, set a backup password if you haven’t yet, then use Download full backup and keep the file somewhere other than the server. The file holds everything the server needs to come back, and only opens with that backup password, so keep the password in a password manager.
Pick a quiet moment. While the installer runs, the console is unavailable for a few minutes as the services restart. Site collectors keep their settings and connect again on their own when it is back.
Upgrade in a few steps
Linux
- Copy the downloaded zip to the server and extract it there:
python3 -m zipfile -e TechSavve-MSP-Suite-Linux-Installer-1.3.3.zip . - Install the new installer package:
sudo apt install ./TechSavve-MSP-Suite-Linux-Installer-1.3.3.deb - Run it:
sudo techsavve-install
It says Existing installation found – upgrading it, puts the new version in place, updates the database and starts everything again. It does not ask for the administrator’s email again, and asks you to accept the license agreement only if the agreement has changed. - Check it:
techsavve statusshows what is running; sign in and the version under the menu reads 1.3.3.
Installed somewhere other than /opt/techsavve? Add the same --dir you used the first time. Installed from the older tar.gz package? Extract the new one and run sudo sh install.sh in its folder.
Windows
- Sign in to Windows as the person who installed TechSavve RMM.
- Extract the downloaded zip.
- Double-click
TechSavve-MSP-Suite-Windows-Installer-1.3.3.exe. It says An existing ‘TechSavveRMM’ appliance was found – it will be upgraded, keeps the ports it was installed with, updates the database and opens the console when it is done. - Check it: the version under the menu reads 1.3.3.
Did you install it with -AllowNetworkAccess, so other computers can reach it? Run the upgrade the same way, from a PowerShell opened with Run as administrator, in the extracted folder:.\TechSavve-MSP-Suite-Windows-Installer-1.3.3.exe -AllowNetworkAccess
What an upgrade keeps, and what it replaces
Kept: every customer, site, device, monitor, ticket and document; users and their passwords; stored device and cloud credentials; your settings and the key that protects stored passwords; the HTTPS certificate; the address and ports; your license; nightly backups and their schedule.
Replaced: the application itself (its services and the web app) and the installer’s own files. The database is brought up to date for the new version automatically.
If something goes wrong
There is no one-click way back to an older version: once the database is updated it belongs to the new one. If an upgrade doesn’t finish or something doesn’t look right afterwards, email assistance@techsavve.com or call (214) 430-9342 with the version you came from and what you see (a screenshot helps). The full backup you took first lets us bring the server back as it was.
What’s new
1.3.3 · 2026-10-28
- Payment cards and renewals. Record the cards your company, each customer and each site pays with (only the last four digits and the expiry date) and the subscriptions charged to them, so renewals and expiring cards don’t catch anyone out.
- Test emails. Admin → Platform settings can send a test email for each mail route and each kind of email, and says what to fix when one fails.
- Windows installer. It brings WSL with it, so nothing has to be installed first, and after the one restart WSL needs it carries on by itself.
- Platform settings tidied up: the old set-up boxes that no longer matched Microsoft’s pages are gone.
1.3.2 · 2026-10-27
- Customer portal. Each page says which site it covers, staff can preview each view as the customer sees it, and a page for one site keeps to that site’s risks.
- Linux installer. Ubuntu 26.04 is supported too, with Docker for it in the download; newer or Ubuntu-based releases use the newest set.
1.3.1 · 2026-10-24
- View-only administrator. A role that can open every administrator page and change nothing.
- Roles & permissions. Admin → Roles & permissions is now a matrix you can edit: a box per role for each thing people can see or change.
- Technicians. They can add knowledge base articles, diagrams and notes, run reports for their own customers and sites, and see the Collectors and Software patches cards. Menus never point at a customer they are not assigned to.
- AI. Admin → AI → AI history shows who asked the AI what, and when. The Standard Library can draft an SOP, policy or procedure with AI.
- The dashboard’s Automatic fixes tile opens a page of every automatic fix; runbook screens are easier to read; new logo artwork.
1.3.0 · 2026-10-22
- What changed? A timeline of the changes on a device around an alert, incident or ticket (programs, updates, services, local administrators, firewall rules and more), with the likeliest cause first.
- Dashboard. An Incident correlation card that groups related problems, and Automatic fixes and Technician time saved tiles.
- Admin → AI. Choose the AI engine (with a fallback), switch each AI feature on or off, and talk instead of type with the microphone button.
- Log forwarding. Send the audit trail, alerts and security findings to a SIEM or any HTTPS endpoint.