NetLock RMMNetLock RMM Docs
IV — Administration

Updates & maintenance

Concurrent-install throttling for agent updates, and maintenance-window controls that suppress notifications.

Updates & maintenance

This chapter covers two small admin pages that are often needed together during maintenance work: the Updates page, which controls how aggressively the server rolls updates out to agents, and the Maintenance page, which lets you silence outbound notifications while you do planned work. A third section covers the notice self-hosted deployments see when the MySQL server behind the Console has fallen out of support.

The Updates page has one setting, the concurrency cap. NetLock RMM itself is updated outside the Console; see Upgrade NetLock RMM.

A.2.1 Updates — concurrent installation throttle

Settings → Updates at /settings/updates has exactly one configurable field plus a Save button.

Updates page showing the concurrency slider and the two informational alerts

The field

Max concurrent installations & updates is a numeric value that caps how many devices the server will process at the same time when installing new software packages or applying update approvals. Ranges differ by deployment:

DeploymentMinimumMaximum
Cloud150
Self-hosted19999

Why the cap exists

Two information panels on the page explain why the cap exists, which helps you pick a sensible value:

  • In-memory package delivery. The server loads each installation package into memory once and serves every download from that single cached copy. Holding more downloads open at the same time does not multiply that memory. The cached packages are a fixed cost, independent of the concurrency number. Because delivery is from RAM, neither disk I/O nor CPU limits the rollout; network bandwidth does.
  • Bandwidth-limited rollout. Even on a fast network, the agents in any given location share egress. A concurrency ceiling keeps a mass rollout from saturating a branch uplink or degrading the Console for other users. Each in-progress update also writes to the MySQL database in the background, so the database host's capacity is a secondary consideration when setting a high value.

The cloud cap of 50 reflects the capacity of the hosted platform. On self-hosted deployments you can raise the number up to 9999, but the practical ceiling is almost always lower. It is set by your available network bandwidth and, to a lesser degree, by the MySQL database load that concurrent updates generate. Start with a low value and measure before raising it.

Applying the change

After editing the number, click Save. The new value takes effect on the next rollout cycle; no restart is required. The throttle affects the queues used for software deployment (Chapter 8.8) and patch approvals (Chapter 7), but does not affect one-off remote actions such as reboot, shutdown, or scripted jobs.

Other update tasks

The page holds only the concurrency cap and has no button that forces agents to update immediately. Other update tasks are handled elsewhere:

  • NetLock RMM itself is updated outside the Console (see Upgrade NetLock RMM).
  • Update history, logs, and per-device install status are in Events (Chapter 12) and on the Software Deployment detail pages (Chapter 8.8).
  • Release notes are published on the NetLock RMM website.

A.2.2 Maintenance — silencing notifications on demand

Settings → Maintenance at /settings/maintenance switches notifications off while you work. It only stops outbound notifications from leaving the server: agents keep running, scripts keep executing, and events are still recorded. When a planned maintenance window lifts, events that accumulated during the window are automatically marked as read rather than surfacing as a backlog of alerts.

A live status banner at the top of the page reflects the current state. When any trigger is active, it reads:

Maintenance mode is currently ACTIVE. Notifications are being suppressed (manual toggle | window '<name>' | …).

When nothing is active, it reads:

Maintenance mode is currently inactive. Notifications are being processed normally.

The banner lists which trigger is causing suppression, so if both a manual toggle and a scheduled window are active you will see both called out.

The page has two tabs: Manual and Scheduled Windows.

Maintenance page with the status banner active and the Manual and Scheduled Windows tabs visible

Manual maintenance mode

The Manual tab has a single toggle, Enable manual maintenance mode, and a Save button.

When the toggle is on, the server suppresses outbound notifications on every channel the deployment has configured:

  • Mail
  • Microsoft Teams
  • Telegram
  • ntfy.sh
  • Webhook

Events still accumulate in the Events log as they normally would, and during suppression they are automatically marked as read, so switching the toggle off does not bring up a backlog of overnight alerts.

Use the manual toggle for unscheduled work, such as immediate reboots, network changes in progress, or a firewall reconfiguration where the fleet will temporarily look offline. Turn it off when you are done; it does not time out.

Scheduled maintenance windows

The Scheduled Windows tab covers recurring windows, for example a weekly Sunday patching slot that you want to suppress every week without remembering to toggle anything. The tab's master toggle, Enable scheduled maintenance windows, switches evaluation on and off as a group; when it is off, none of the configured windows apply.

Underneath the master toggle is a table of windows with one row per window and the following columns: Name, Weekdays, From, To, Timezone, Enabled, and Actions. Each row's Actions cell exposes Edit and Delete.

Click Add window to open the window editor. The editor fields are:

  • Name (optional): a friendly label. The helper text suggests something like Weekly Sunday Patch Window. The field is optional; when blank the table shows a record number instead.
  • Weekday checkboxes for Monday through Sunday. At least one weekday must be selected.
  • From: the window start time in 24-hour HH:mm format.
  • To: the window end time in 24-hour HH:mm format. When To is earlier than From, the window wraps past midnight. For example, From 22:00 and To 02:00 suppresses notifications from ten in the evening to two the next morning. The table row for such a window displays a +1d chip.
  • Timezone: the wall clock From and To are meant in. A new window starts with the instance display timezone (see Chapter A.5.2); Server time (legacy) keeps the window on whatever clock the server runs on.
  • Window enabled: per-window toggle. Disable a single window without deleting it when you want to keep its definition but skip it this month.

The server evaluates each window in the timezone stored with it, not in the user's browser time or personal display timezone. If your team is distributed across time zones, pick one zone for your maintenance rota and use it on every window.

Editing and deleting windows

Edit in the table actions reopens the editor with the existing values. Delete opens a small confirmation dialog titled Delete maintenance window with a body message of Delete window '<name or #id>'?. Confirm to remove the window permanently; there is no undo.

Permission nuance

Viewing the page requires settings_maintenance_enabled. Making changes (toggling the manual switch, adding, editing, or deleting windows) requires settings_maintenance_manage. Without the manage flag, the page renders read-only: you can see the current state but none of the controls respond.

A.2.3 Database server version (self-hosted)

Self-hosted only: Cloud deployments never see this notice; the hosted platform runs the database for them.

The Console compares the MySQL server it is connected to with the recommended release, currently MySQL 8.4. When the server is older, two things appear:

  • A warning icon next to the update notice in the top bar (on phones, an entry in the account menu). It opens a dialog that names the running version, the date Oracle support ended where that is known, the recommended version and the steps of the Docker upgrade, with a link to the guide.
  • A warning above the status card on Settings → Database, with the same link.

Both are visible to accounts that hold settings_enabled and settings_database_enabled, the permissions of the Settings → Database page. The notice cannot be dismissed or snoozed; it disappears once the database reports version 8.4 or newer. The Console reads the version at start, once an hour, and every time Settings → Database loads, so after an upgrade a visit to that page clears the notice at once.

ReleaseOracle support ended / ends
MySQL 5.731 October 2023
MySQL 8.030 April 2026
MySQL 8.4 LTS30 April 2032

The innovation releases 8.1 to 8.3 are flagged as well; the notice shows them without a date. The upgrade itself happens at the host level. Upgrade MySQL to 8.4 walks through it for the Docker container.

Permissions

ActionRequired flags
View Settings → Updatessettings_enabled, settings_updates_enabled
View Settings → Maintenancesettings_enabled, settings_maintenance_enabled
Change maintenance settingssettings_enabled, settings_maintenance_enabled, settings_maintenance_manage
See the database server version noticesettings_enabled, settings_database_enabled
  • Chapter 7 — Patch Management. The approval queue feeds the rollout throttle this chapter governs.
  • Chapter 8.8 — Software Deployment. Deployments respect the concurrency cap.
  • Chapter A.8 — Notifications deep dive. Maintenance mode suppresses the channels configured there.
  • Chapter 12 — Events & Audit. Events continue to record during maintenance; they are auto-marked as read.
  • How-to — Upgrade MySQL to 8.4. The Docker steps behind the database server version notice in A.2.3.