RMMZit 0.13.2

RMMZit 0.13.2 — the product name next to the logo.

Fixed

• Console, sign-in page, reports and the agent window on Windows: the name next to the logo now reads RMMZit (it still showed the old name).
• Downloads folder: agent installers of version 0.12 and earlier are removed when the server starts.
• Appliance OVA: imports in VMware again. The disk is written as a complete stream-optimized VMDK (VMware Workstation rejected the earlier ones) and the hardware description follows the OVF schema order (ESXi refused it).

Updating

Settings → RMMZit updates installs it; agents update themselves as usual. Docker: docker compose pull && docker compose up -d.

RMMZit 0.13.1

RMMZit 0.13.1 — guide and README tidy-up, Docker setup token command.

Fixed

• Docker: docker compose exec rmmzit rmmzit-server -setup-token prints the setup token (the image has no shell tools, so reading the file did not work); the guide and the Compose file use it.
• Windows agent and tray: folders left by version 0.12 and earlier (agent status and tray window data) are removed.
• Console backups made by version 0.12 and earlier get the names of new backups when the server starts.
• User guide and README: only the name RMMZit.

Updating

Settings → RMMZit updates installs it; agents update themselves as usual. Docker: docker compose pull && docker compose up -d.

RMMZit 0.13.0

RMMZit 0.13.0 — a new name and logo, and the server runs in Docker.

New name: RMMZit

The product is now RMMZit (repository Max-Zit/rmmzit, new logo with the same icon). Installations of version 0.12 and earlier update as usual and keep everything:

• Server: Settings → RMMZit updates installs the package rmmzit-server, which replaces the package of the earlier versions and moves its data (/var/lib/rmmzit) and settings (/etc/rmmzit/server.env; the variable names of earlier versions are still read). Appliances keep their administrator czadmin; new appliances have rzadmin (first password rmmzit).
• Agents update themselves: on Windows the MSI installs RMMZit Agent (service RMMZitAgent) in place of the agent of earlier versions; on Linux the agent moves to the service rmmzit-agent. The enrollment and the device stay the same.
• New enrollment codes start with RZ1-; codes with CZ1- keep working. New console backups end in .rzb; .czb backups are still listed and restored.

New: Docker

• The server as a container image, ghcr.io/max-zit/rmmzit (tags latest, testing and the version), built from the signed server package, with a Compose file (PostgreSQL included) in packaging/docker.
• Before a new image changes the database, the server writes a console backup; Settings → RMMZit updates shows how to update a container.
• The guide has a new section Installing the server → Docker.

Updating

Settings → RMMZit updates installs it; agents update themselves as usual.

RMMZit 0.12.2 (release candidate)

RMMZit 0.12.2 — user guide brought up to date.

Release candidate: this version is offered only to consoles on the Testing update channel. It becomes the official release after testing.

Fixed

• User guide: a stray character at the start of the Update channel paragraph (Settings page of the guide, all languages) is gone; the guide's test now checks that every page is valid UTF-8.
• User guide, Getting started: the overview now lists the terminal on Windows, the registry editor and scheduled tasks, event log and process monitors, history with the disk-full forecast, Chocolatey, the software library, vulnerabilities and policies.
• User guide, Troubleshooting: backing up and moving the server now describe Settings → Console backup and rmmzit-server -restore.
• README updated with the same features and the load test result (1,000 agents on 2 vCPU / 1 GB RAM).

Updating

Settings → RMMZit updates installs it; agents update themselves as usual (Settings → Agent updates).

RMMZit 0.12.1

RMMZit 0.12.1 — update channels for release candidates, lower memory use per agent and security fixes.

New

• Update channel (Settings → RMMZit updates): Official releases (default) or Testing — release candidates before they are released. Use Testing only on test consoles.

Fixed

• Memory per agent: agent connections no longer keep a compression context; a server with 500 agents uses about 140 MB instead of almost 500 MB. Tested with 1000 simulated agents on 2 CPUs and 1 GB RAM (195 MB, all reconnected 7 s after a restart).
• Scheduled tasks: task names with typographic quotes (‘ ’ ‚ ‛) are refused like straight quotes, and the Group Policy script on the site page doubles them, because PowerShell reads them as quotes.
• go-jose updated to 4.1.6 (CVE fixes in the library used for single sign-on).

Updating

Upgrades from older versions were tested from 0.5.0. Agents update themselves as usual (Settings → Agent updates).

RMMZit 0.12.0

RMMZit 0.12.0 — terminal on Windows, registry editor and scheduled tasks, monitors for event logs and processes, and deployment with Group Policy and Intune.

New

• Terminal on Windows: the device's Terminal opens Windows PowerShell as SYSTEM in the browser (Windows 10 1809 / Server 2019 and later, on a pseudo console). Leaving the page ends the shell and every program it started. Linux keeps its root shell.
• Registry editor (Registry tab, Windows): browse keys of HKLM, HKU, HKCR and HKCC, add, change and delete values (REG_SZ, REG_EXPAND_SZ, REG_DWORD, REG_QWORD, REG_MULTI_SZ) and keys. Roots and the system's own branches are protected; every change is audited with the value it replaced.
• Scheduled tasks (Scheduled tasks tab, Windows): the Task Scheduler's tasks with state, last run and result, next run, account and command; run, end, enable, disable and delete them (audited). Windows' own tasks are hidden unless you include them.
• Monitors (new policy part): event rules for the Windows event logs (log, event IDs, source, level, at least N events within M minutes) and processes that must run (Windows and Linux). The devices are asked every 5 minutes; alerts open and close by themselves, and the device page shows each rule's last result. Events are counted with the Windows Event Log API.
• Deployment to many computers: the site page shows, filled in with a new enrollment code, a Group Policy computer startup script (with the path of the MSI on your share) and the settings for a Microsoft Intune Win32 app (install and uninstall commands, detection rule).

Updating

Settings → RMMZit updates installs 0.12.0 from GitHub; agents update themselves (Settings → Agent updates). The terminal on Windows, the registry editor, scheduled tasks and monitors need agents 0.12.0.

Testing channel

Current candidate: RMMZit 0.13.2 (https://github.com/Max-Zit/rmmzit/releases/tag/v0.13.2). For test consoles only: Settings → RMMZit updates → Update channel: Testing.

RMMZit 0.11.2

RMMZit 0.11.2 — complete third-party notices.

Fixed

• Third-party licenses: THIRD_PARTY_LICENSES now also carries the NOTICE file of go-oidc (Apache-2.0), the license of Microsoft's WebView2Loader.dll used by the agent's window, and the license of the Lucide (ISC) and Feather (MIT) icons the console and the agent's window are drawn after. The installer note about WiX is corrected.
• The Windows agent installer now installs THIRD_PARTY_LICENSES.txt next to LICENSE.txt.

Nothing else changes; no third-party code with an incompatible license was found in a review of the code.

Updating

Settings → RMMZit updates installs 0.11.2 from GitHub; agents update as usual.

RMMZit 0.11.1

RMMZit 0.11.1 — the appliance keeps its SSH hardening.

Fixed

• Appliance SSH: on freshly installed appliances the hardened SSH settings (no root sign-in, no chacha20-poly1305 — Terrapin — and no 64-bit UMAC) were removed during installation, because the installer has no host keys yet and the check of the SSH configuration failed for that reason. The file is now only taken out when it is itself the cause. Existing appliances get the settings back with this update.
• Restoring a console backup checks the file names inside the backup twice (defence in depth; flagged by CodeQL).

Updating

Settings → RMMZit updates installs 0.11.1 from GitHub. Agents do not change in this release, but they update to 0.11.1 as usual.

RMMZit 0.11.0

RMMZit 0.11.0 — metric history with a disk-full forecast, backups of the console, and a server that stays quick with many devices.

New

• History tab on every device: CPU and memory, network traffic and the used space of each disk over 24 hours, 7, 30 or 90 days. Minute values are kept 7 days, hourly summaries 90 days.
• Disk-full forecast: from the growth of the last 14 days the server tells when each disk will be full. Disks full within 90 days are shown on the device page; the new alert rule Disk full within (days) in the policy's alerts opens an alert (14 days for new policies, critical within 3 days).
• Console backup (Settings → Console backup): a daily backup at the chosen hour or Back up now — database, secret key, the certificates the agents trust and the software library. Keeps the newest N, optional encryption with a passphrase (AES-256-GCM), optional copy to an SFTP folder (the server's host key is confirmed once). Failures are emailed to the alert recipients.
• Restore: on the appliance in the setup menu (Restore a backup), with the Linux packages rmmzit-server -restore <file> while the server is stopped. The database is restored in one step; agents keep working with a server restored from a backup.

Better

• Background work runs in separate loops: a slow mail server or a large report no longer holds up alerts, schedules or tasks.
• When agents reconnect (for example after a server restart), each one only picks up its own waiting work instead of every device's.
• Alert checks read the policies once and compute the load of all devices in one query.
• Job runs wait as waiting until one of the 32 places is free, instead of showing running while they wait.
• A device that loses its connection shows offline in under a minute (pings every 30 seconds, from the server and from agents 0.11).
• Agents 0.11 send their network traffic with the load.

Updating

Settings → RMMZit updates installs 0.11.0 from GitHub; agents update themselves (Settings → Agent updates). Network traffic appears for agents 0.11 and newer.