NetLock RMMNetLock RMM Docs
II — Console Reference

Patch Management

The global approval queue, update history, and SLA settings.

Patch Management

The Patch Management page is the Console's view of the fleet-wide patching pipeline. It answers two questions: which patches are approved for installation anywhere in the fleet, and how compliant the fleet is against the patches that exist. When the devices of a policy install updates, and how they restart, is configured in the policy itself.

Patch Management page with the Update Approval tab open

7.1 Scope — this page versus the policy editor

Patch Management in NetLock RMM is split across two places:

  • The Patch Management page at /patch-management, the subject of this chapter, is global. It shows every patch the system knows about, holds the approval state for each, tracks compliance against SLA thresholds and configures deployment-wide patch defaults.
  • The Policy Settings → Patch Management tab, documented in Chapter 6.12, applies per policy. It decides when and how the devices assigned to a given policy install the patches that have been approved on this page. That is where the per-platform rollout rules, deployment rings, maintenance windows, reboot behaviour, notifications, and retry configuration live.

Rollout scheduling and reboot controls are not on this page.

7.2 The tabs

Patch Management is a single page with these tabs across the top:

TabPurpose
OverviewFleet health rated by security relevance and SLA state, the compliance figures, the tiles and the top tables. Every figure follows the compliance scope of the Settings tab.
Devices Not Up To DateEvery device with listed updates still open, with the Last scheduled run column; updates outside the compliance scope are marked Not scored.
Update ApprovalThe main queue — every known patch with its approval state, compliance counts, and SLA status.
Update HistoryA history view of update installs, successes, and failures per patch and device.
Patch historyPatch Now and uninstall jobs together with the scheduled patch runs of the agents. See 7.5.
Auto-ApprovalRules that approve patches automatically. Shown only to accounts with the permission patch_auto_approval_manage.
SettingsSLA thresholds, the compliance scope (sources, update types, severities, approval state, grace period), history cleanup. Saving needs the permission described under Permissions.

On the Overview and Devices Not Up To Date tabs a tenant selector appears when the account may read more than one tenant. It narrows every figure of the two tabs, including the dialogs opened from them, to one tenant. The selection is a view only: the compliance scope of the Settings tab applies to every tenant, the other tabs are not affected, and the selection is not kept across page loads.

The page opens on the Overview tab as soon as the permissions and the settings are known. Every other tab loads its data when it is first opened and keeps it while the page stays open. The Update Approval, Update History and Patch history tables are paged: the rows per page are chosen at the bottom of the table (10 to 500), the counter above the table shows how many entries match the filters and reads more than 10000 entries beyond that cap, and the search box needs at least two characters before it filters. Sorting by the Status or Platform column of the approval queue and by the Action column of the history follows the order of the values in the matching filter list, not the alphabet.

Patch Management tabs across the top of the page

Most actions happen inline through row actions and toolbar buttons. The entries of the Patch history tab open in a details dialog.

7.3 The approval workflow

Every patch in the Update Approval tab is in one of four states:

  • Pending: newly discovered; no admin decision yet.
  • Approved: eligible for installation anywhere the policy-level rules allow it.
  • Rejected: explicitly blocked fleet-wide; no device will install it.
  • Deferred: postponed. The default defer period is 7 days; after the timer expires the patch returns to Pending.

From the table toolbar you can act on one or many selected rows. The checkbox in the table header selects the rows of the current page; unticking it clears the selection on every page. Rows stay selected while you page through the table, and the toolbar shows how many rows are selected. Every action clears the selection once it has run. Group by type groups the rows of the current page by update type, with the page ordered by type first. Available actions:

  • Approve: set state to Approved.
  • Reject: set state to Rejected. A confirmation is shown ("Are you sure?") because rejection is a fleet-wide block.
  • Defer: postpone for N days (default 7).
  • Reset to Pending: revert from any other state.

Bulk approval actions on the Update Approval tab

Every state change triggers an immediate re-sync of every device. Devices do not wait for their next scheduled poll; the updated approval set reaches every agent as soon as the server can deliver it.

Important: Approval on this page is global: it applies to every device, group, location and tenant at once. Narrowing a patch's rollout to a subset of the fleet is done with the Approval & Filtering and Deployment Rings sub-tabs inside a policy (see Chapter 6.12).

7.4 The compliance model

Scored and listed

Every update the console knows is either listed, scored or neither:

  • An update is listed when its approval state qualifies (see below) and it is not a Defender security intelligence update. Listed updates appear in the Devices Not Up To Date tab, in the device dialogs, in the Devices missing OS patches / software updates tiles and in the Updates tab of a device.
  • An update is scored when it is listed and lies inside the compliance scope configured on the Settings tab: its source, its update type and its severity bucket are selected, and its grace period has passed. Only scored updates count toward the compliance percentage, the fleet and device health ratings, the SLA figures, the donuts, the top tables, the dashboard widgets and the critical tile.
  • Defender security intelligence updates (the signature updates of Microsoft Defender Antivirus, KB2267602, and of the older Microsoft Endpoint Protection, Microsoft Security Essentials and Windows Defender products) are never reported, listed, scored or installed. Windows republishes them several times a day and Defender keeps them current through its own updater; monitor their state with the sensor Microsoft Defender Antivirus status. Rejected updates, updates whose deferral is still running and updates blocked by the automatic rollback are never scored.

The update type of a Windows update is Microsoft's own classification (Security Updates, Critical Updates, Updates, Definition Updates, Update Rollups, Service Packs, Feature Packs, Upgrades, Drivers, Tools). It does not depend on the display language of the device (agent 3.3.0.11 or later). Updates of the Definition type other than the security intelligence updates, for example the Microsoft Defender antimalware platform (KB4052623) or the Windows Security platform (KB5007651), are managed like any other update: they are listed, scored when the compliance scope includes Definition, and installed when the policy allows the Definition type.

A listed update that is not scored carries the chip Not scored wherever it is shown, and the SLA column of the Update Approval tab reads Not scored for it. A device whose open updates all lie outside the scope is up to date for every compliance figure; the Devices Not Up To Date tab still lists it, marked with the chip, so the backlog does not disappear.

The default scope scores the operating system channels (OS-Mandatory, Apt, Dnf, Yum, MacOS), every update type except Driver, every severity and approved updates only, without a grace period. Winget and Chocolatey updates are listed but not scored until you add the two sources to the scope.

The approval state of the scope is either Approved updates only (the default) or Approved and pending updates. The second option scores pending updates and deferred updates whose deferral has expired as well, which shows the real exposure of a fleet that is not approved by hand.

The grace period (0 to 60 days) delays scoring: an update is scored only once it has been in the catalog for that many days, counted from First seen. It keeps Patch Tuesday from colouring the fleet red for the day or two before the scheduled runs have installed the new updates. The grace period has to be shorter than the SLA deadline for Critical, so a critical update can never be overdue before it is scored; the Settings tab refuses to save otherwise.

Security-relevant updates

An update is security-relevant when its update type is Security, or its severity is Critical, High or Important, or its catalog row carries at least one CVE. This definition is fixed and not part of the configurable scope. It drives the headline figure and the health ratings below. A monthly Malicious Software Removal Tool rollup without CVEs or a driver update is not security-relevant.

Fleet health

The headline figure of the Overview is the security compliance: the percentage of reporting devices without an open security-relevant scored update. A device reports once the server has received an update inventory of it in which every operating system source answered (Windows Update, apt, dnf, yum or softwareupdate); only authorized devices are counted.

Linux and macOS report pending updates only, so a fully patched Linux or macOS device reports without any catalog row and counts as fully patched. An inventory in which the operating system source failed changes nothing: a device that reported before keeps reporting with its last known updates, a new device stays not reporting. A Linux device with a package manager NetLock does not patch (zypper, pacman) never reports.

The second line, X of Y devices fully patched, counts the devices without any open scored update. The colour of the headline follows the tier thresholds: 90 % and above green, 75 % and above amber, below red.

The fleet health rating takes the first matching row:

TierCondition
No dataNo device reports.
CriticalA scored critical update is overdue, or the security compliance is below 50 %.
Needs attentionA scored critical update is open within its SLA, a security-relevant update is overdue, or the security compliance is below 75 %.
FairA security-relevant update is open within its SLA, an installation failed in the last 30 days (updates in the catalog scope only), or any scored update is overdue.
GoodOnly updates that are not security-relevant are open, all within their SLA.
ExcellentNothing scored is open.

The reason line under the rating names the security compliance, the fully patched count and every figure above zero.

Device health

The smiley in the Patch status column of /devices rates one device on the same scale:

  1. A device that never reported its update state is grey.
  2. A device without an open scored update is Up to date, whatever its last job did. The tooltip names the listed updates that are not scored and the updates not approved yet.
  3. Up to two open scored updates are Good, up to five Fair, more need attention. A backlog without a security-relevant update stops at Fair.
  4. An overdue critical update is Critical; an open critical update within its SLA or an overdue security-relevant update is at least Needs attention.
  5. A Patch Now job that finished in the last 14 days lowers the rating when it failed, but only for failed items whose update lies in the catalog scope.
  6. An outstanding restart that pauses the scheduled runs with operating system updates open is at least Fair.

SLA status

Each row in the Update Approval tab carries three compliance indicators in addition to its approval state:

  • Installed: count of devices that already have the patch installed.
  • Devices pending: count of devices where the patch is available but not yet installed.
  • SLA: one of Compliant, At Risk, Overdue or Not scored.

SLA status is computed per row based on the patch's severity and how long it has been known. The threshold for each severity is the number of days after first discovery within which a device is expected to have installed the patch:

SeverityDefault daysField under SLA Compliance Deadlines
Critical7Critical (days)
High, Important15High (days)
Medium, Moderate30Moderate (days)
Other / Low / Unspecified60Other (days)

SLA state transitions:

  • Compliant: within SLA. The deadline has not passed.
  • At Risk: three days or fewer to the deadline.
  • Overdue: the deadline has passed.
  • Not scored: the compliance scope does not score the update, so no SLA applies to it.

Grace period and SLA both count from First seen: the grace period decides when an update starts to count, the SLA deadline when it is overdue.

Dashboard widgets

Widgets that make a compliance or health statement follow the scope: Patch compliance, Patch SLA status, Most missing updates and Missing updates by platform. Widgets that break down the inventory show every approved update regardless of the scope: Pending approved updates by severity, Available updates by type and Update approval status; the history and job widgets do not depend on the scope. The description of each widget says which rule it follows.

7.5 The Patch history tab

The Patch history tab lists what was installed or removed on the devices, and why a run installed nothing. It shows two kinds of entries in one list, newest first:

  • Jobs. Patch Now and uninstall jobs that an operator started. The Action column reads Install or Uninstall, and Triggered by names the operator.
  • Scheduled runs. The runs an agent started on its own from the patch schedule of its policy. The Action column reads Scheduled run, and Triggered by reads Schedule. Scheduled runs are reported by agents 3.3.0.5 and newer. Runs of older agents appear only as the Last patch run line on the device.

The same list exists for a single device as the Patch history tab next to Updates in the device's detail view on /devices.

Columns and filters

The columns are Device, Tenant, Location, Action, Status, Triggered by, Created, Finished, Items and Actions. For a job, Items shows how many updates were installed (removed) and failed, an orange count of skipped updates when there are any, and the total. For a scheduled run, Created is the start of the run and Items shows how many updates were installed, failed and held back. A skipped run has no items.

The status of a scheduled run follows its result:

StatusMeaning
CompletedThe run installed updates, or found updates and none of them failed.
Partially completedSome updates were installed and some failed.
FailedUpdates failed and none was installed.
Nothing pendingThe run found nothing to install.
Waiting for restartAn outstanding restart from an earlier run blocked the Windows updates; from agent 3.3.0.11 Winget and Chocolatey updates are still installed in such a run and show their own decision.
SkippedNo run started. The reason stands next to the chip, for example Insufficient disk space or Patch management is disabled in the policy of this device. A run that held every update back (filters, approval, deferral, updates that need a user at the device) and installed nothing is Skipped as well; the number of held-back updates stands next to the chip.

The toolbar filters the list:

  • Status accepts several statuses at once. With none selected every entry is listed, including Skipped. Select every other status to leave the skipped entries out.
  • Trigger switches between All entries, Patch Now & uninstall and Scheduled runs.
  • Action narrows the list to Install or Uninstall. Scheduled runs count as installations: Install lists them together with the Patch Now jobs, Uninstall hides them.
  • Period loads Last 7 days, Last 30 days, Last 90 days or All time. The default is Last 30 days.
  • The search box matches the stored values, not the translated text shown in the table: the device, tenant and location names, who started a job, the action word of a job (install, uninstall), the note of a run and the stored outcome keyword of a run (for example nothing_pending or disk_space). It needs at least two characters. Statuses are filtered with the Status select, not with the search box.

The counter above the list shows how many entries of both kinds match the filters, at most 10,000.

Details of a scheduled run

Double-click an entry or use View full details in the Actions column to open its details. A job opens Patch Job Details (see Details of a job). A scheduled run opens Scheduled patch run, which shows:

  • The device, tenant and location.
  • Started on the clock of the instance, and underneath Device time: … on the device's own clock. Finished carries the duration of the run.
  • Maintenance window: Inside the maintenance window (…) or Catch-up of a missed maintenance window (…), followed by the window of the policy, or no time restriction when From equals To.
  • The status, the agent version, the note of the run and the counts of installed, failed and held-back updates, with Reboot required when the run left a restart outstanding.
  • A notice when Winget and Chocolatey updates were not checked because Windows updates wait for a restart (agents before 3.3.0.11 skip the application stages of a run whose Windows stage leaves a restart outstanding; from 3.3.0.11 the application updates are installed in the same run), and when the agent reported only part of the updates of a very large run.
  • One row per update with Source, Name, Status, Reason and Details. The chips above the table filter the rows by All, Failed, Installed and Held back.

The status of an update is Installed, Installed, restart pending, Failed, Held back (held back for one of the reasons below) or Skipped (nothing to do). Details carries the error text, for Windows updates the error code Windows Update returned, and for Linux the package manager's message. The reason is one of:

ReasonMeaning
Installed / Failed / SkippedThe result of the installation.
Installed, waiting for restartWindows installed the update; it takes effect after the next restart.
Blocked by severity filterThe severity filter of the policy excludes the update.
Blocked by update type filterThe update type filter of the policy excludes the update.
Not approvedThe update is not approved for this device.
Deployment ring until …The deployment ring of the device holds the update back until that time.
Retry after …The update failed before and waits for the retry delay of the policy.
Needs user inputThe update cannot install without someone at the device. On macOS: a macOS update on a Mac with Apple Silicon, or an update for which softwareupdate asked for a password; see macOS.
Major upgrade not allowed by the policymacOS: an upgrade to a new major version (for example macOS 26 to 27) that the policy does not allow in scheduled runs, or that Patch All left out.
Deferred to a later runThe policy installs one update per run; this one follows in a later run.
Framework package, updated with its appA Winget framework package that is updated together with the app that uses it.
No upgrade availableWinget had nothing to install for the package.
Already up to dateChocolatey found the package current.
Package manager query failed in the last runWinget or Chocolatey could not be queried when the run started, so the run could not decide about the updates of that source; the note of the run names the failed query. Shown on the device's Updates tab, not on the items of a run.
Replaced by another packageLinux: the upgrade replaced the package with another one.
Kept back by the package managerLinux: apt keeps the package back, usually because the upgrade would remove another package.
On hold in the package managerLinux: the package is on hold (apt-mark hold).
Dependencies cannot be resolvedLinux: the package manager cannot resolve the dependencies of the update.

With agent 3.3.0.11 or later, the Last run chip on the device's Updates tab also shows the decision of the last scheduled run for Winget and Chocolatey updates, in the same way as for Windows updates: Installed, Failed, Retry after …, Not approved, Deferred to a later run, No upgrade available, Package manager query failed in the last run or Not offered in last run. A Retry after … reason names the time of the next allowed attempt. An older agent reports no decision for these rows, so their chip stays empty.

Details of a job

Patch Job Details shows the device, the action, the status, who started the job, when it was created, started and finished, the note of the job, and one row per update with Name, KB ID, Source, Status and Details.

Above the rows, Items counts the updates: Installed (on an uninstall job: removed), Failed, Skipped and the total. When some installed updates still wait for a restart, an extra chip reads of which restart pending: n. The counts of a finished job are taken from its rows, so the header, the list and the rows always agree.

The status of an update is one of:

StatusMeaning
PendingThe job has not reached the update yet.
Installing / RemovingThe agent is working on the update.
Installed / RemovedThe update was installed (on an uninstall job: removed).
Installed, restart pendingWindows Update installed the update; it takes effect after the next restart of the device. It counts as installed. The row keeps this status after the restart, because it records what the job did; the device's Updates tab shows the update as Installed once the device has restarted and sent its next inventory. Windows updates of Patch Now jobs get this status from agent 3.3.0.11, and so do macOS updates that softwareupdate prepared for the restart (see macOS). Most cumulative and driver updates need a restart, so this status is common.
FailedThe update failed; Details carries the error.
SkippedNothing was done for the update. Details names the reason, for example that the update is no longer offered. Skipped with the detail not processed by agent means that no result for this update reached the server before the job ended.
Cannot be removedWindows does not allow removing the update.

The agent keeps the results of a job on the device until the server has received them. When the agent or the device restarts during a job, or before the completion report reached the server, the agent reports the job after the restart with the results it had reached: with its decided outcome, or as Partially installed (some updates installed) or Failed with the note The agent restarted while this job was running. Updates it had not finished read Skipped with the detail not processed by agent.

When a scheduled run creates an entry

The agent checks every five minutes whether a scheduled run may start. Not every check creates an entry:

  • A run that reached the installation always creates one entry, including runs with the result Nothing pending or Waiting for restart.
  • Insufficient disk space and informational mode create a Skipped entry at most once per day. Neither uses up the maintenance window.
  • Patch management disabled in the policy, no patch settings on the device yet and an incomplete maintenance window create a Skipped entry when the state changes, not at every check.
  • Waiting for an allowed patch day, waiting for the maintenance window and already ran in the current window never create an entry. The device's Scheduled patching line in the detail view shows these states with the next possible run.

A link to /patch-management?run=<id> opens the details of a scheduled run, and /patch-management?job=<id> the details of a job; both open the Patch history tab. /patch-management?tab=jobs opens the tab, and &status=Skipped or another status preselects the status filter. An entry outside the selected period still opens; the tenant scope of the account applies.

Scheduled runs are deleted after 90 days by default. The retention is set under Scheduled Patch Run History Cleanup on the Settings tab, separately from the update history. Jobs are not affected by it.

7.6 The Settings tab

The Settings tab holds the configuration of the page. These settings are deployment-wide: they affect the whole Patch Management page, not a particular policy.

Patch Management Settings tab with SLA and compliance scope fields

SettingDefaultMeaning
SLA Compliance Deadlines: Critical (days)7SLA threshold for Critical-severity patches.
SLA Compliance Deadlines: High (days)15SLA threshold for High-severity patches.
SLA Compliance Deadlines: Moderate (days)30SLA threshold for Moderate-severity patches.
SLA Compliance Deadlines: Other (days)60SLA threshold for remaining severities.
Compliance scope: SourcesOS channels on, Winget and Chocolatey offWhich update sources are scored: Windows Update, Apt, Dnf, Yum, macOS and the package managers Winget and Chocolatey.
Compliance scope: Update typesall except DriverWhich update types are scored, as the agents classify them. Defender security intelligence updates are never scored, whatever is selected.
Compliance scope: SeveritiesallWhich severity buckets are scored: Critical, High (High, Important, RequiresRestart), Medium (Medium, Moderate, Recommended), Low (Low, Optional), Unspecified (Unspecified, Informational, None). Winget, Chocolatey and driver updates carry no severity and fall under Unspecified.
Compliance scope: ApprovalApproved updates onlyWhether pending updates (and deferred updates whose deferral has expired) are scored as well.
Compliance scope: Grace period (days)0Days after First seen before an update is scored; has to be shorter than the Critical SLA days.
Update History Cleanup (Auto-cleanup enabled, Keep history (days))on, 90 daysDeletes update history entries once they are older than the number of days set.
Scheduled Patch Run History Cleanupon, 90 daysDeletes scheduled patch runs of the Patch history tab and their per-update results once they are older than the number of days set. Patch Now and uninstall jobs are not affected.

Changes apply once saved: the overview, the Devices Not Up To Date tab, the dialogs, the Patch status column of the devices list and the dashboard widgets read the saved values within a few seconds. The Save Settings button of the Settings tab and the one of the Auto-Approval tab save the same settings; both need the permission described under Permissions. Without it the fields are read-only and a hint names the required permission.

7.7 Platforms and sources

The Update Approval tab filters by platform and by source. The platform dropdown supports:

  • Windows
  • Linux
  • MacOS
  • Docker

The source dropdown supports:

SourcePlatformNotes
OS-MandatoryWindows, macOSNative OS-provided updates.
WingetWindowsWindows Package Manager updates.
ChocolateyWindowsChocolatey package updates.
AptLinuxDebian / Ubuntu package updates, and derivatives such as Proxmox VE.
DnfLinuxFedora / modern RHEL package updates.
YumLinuxOlder RHEL / CentOS package updates.
DockerDockerContainer image updates on Linux hosts running Docker Engine.
MacOSmacOSNative macOS updates.

Approval is per patch regardless of source. An Approved patch from Winget installs under the same rules as an Approved patch from OS-Mandatory. The per-policy Approval & Filtering sub-tab decides which sources the devices of a particular policy accept.

On Apt systems, a package update can ask what to do with a configuration file that was modified on the device. The agent answers this automatically according to the policy's Configuration file conflicts option (Linux tab, Approval & Filtering): by default the currently installed file is kept; alternatively the package maintainer's version is installed. Dnf and Yum never ask (rpm writes .rpmnew / .rpmsave files instead), so the option does not apply to them.

On Apt systems the agent also decides how the packages are handed to apt. When the run covers everything apt has pending (no severity, type, approval or deployment-ring filter drops a package), apt resolves the upgrade itself: apt-get upgrade --with-new-pkgs by default, which installs new dependencies but never removes a package, or apt-get dist-upgrade when the policy option Allow package removal (full upgrade) (Linux tab, Approval & Filtering, shown for apt) is on. With the option off, packages that apt can only upgrade by removing another one (a renamed library such as libzfs6linux to libzfs7linux on Proxmox VE) are kept back and listed in the job as Skipped, together with the packages a full upgrade would remove; Proxmox VE hosts need the option on.

A filtered selection installs the named packages only (--no-remove unless removal is allowed) and, if apt rejects the set as a whole, is retried package by package. apt waits up to five minutes for a package lock held by another process. When apt fails, its E: lines are shown in the item details of the job, in the job note and in the agent's Error.txt. A kernel update marks the device as reboot-required as soon as a kernel newer than the running one is installed in /boot, so the reboot policy applies on Debian and Proxmox VE hosts as well.

On Dnf and Yum systems (Fedora, RHEL and its rebuilds such as Rocky Linux and AlmaLinux, CentOS) the agent refreshes the repository metadata with dnf makecache / yum makecache before it reads what is pending. Pending updates are listed once per package, with the exact version dnf offers, and once per advisory, with the advisory's type and severity and its packages in the description; a package an advisory covers appears in both. On Fedora 41 and later (dnf5) the advisories are read with dnf advisory list.

When the run covers everything dnf has pending, dnf resolves the upgrade itself with dnf upgrade, which also handles obsoleted packages, kernels installed next to the running one and every advisory. A filtered selection installs exactly the approved package versions (name-version-release.arch) in one transaction and the approved advisories (--advisories= on dnf, --advisory on yum) in a second one. A package dnf cannot use (excluded by excludepkgs in dnf.conf, or a version the repository no longer offers) fails with dnf's own message (No match for argument, matches only excluded packages) and the other packages are installed in a second run; a transaction dnf rejects as a whole is retried update by update.

After the run the agent asks rpm what is installed: a package item is Success only when the approved version is installed (in a full upgrade, also a newer one), an advisory item only when dnf no longer lists the advisory as pending. dnf's error lines are shown in the item details of the job, in the job note and in the agent's Error.txt.

Windows

The agent installs Windows updates through Windows Update, one update after the other. With agent 3.3.0.12 or later the rules below apply. The limits are fixed; there is no policy setting for them.

  • Time limit per update. Every update has 6 hours for its download and installation. When an update is still running after that, the agent stops waiting for it and ends the run. The update is listed as Failed with the detail The update did not finish installing within 360 minutes, so the agent stopped waiting for it and ended the installation run. It counts as a failed attempt, so Retry count for failed patches and Retry delay (minutes) of the policy apply to it. Windows may still complete such an installation on its own; the device then reports the update as Installed or Installed, restart pending at its next synchronisation, next to the Failed result of the run. Updates that finished earlier in the same run keep their result, including a required restart. Updates the run had not started are Skipped with the detail The installation run ended before this update was started; it is attempted in the next cycle., and the note of the run or job names the limit.
  • Starting further updates. A run starts no further update once 60 minutes have passed since it began installing. A scheduled run that started inside its maintenance window keeps starting updates until the window ends, when that is later than the 60 minutes. An update that is already downloading or installing at that point is not interrupted, so a run can end after the window. A run that ends up to 60 minutes after its window restarts the device as usual. When it ends later than that, the device is not restarted automatically at that moment: with Automatic reboot (and with Ask user and Reboot immediately on a device where nobody is signed in) the restart stays outstanding, and the next scheduled run inside the maintenance window of the policy carries it out. With one allowed patch day per week that is the following week; until then the update is installed but not in effect, and the device shows the pending restart. The note of the run says that the restart was left to the next maintenance window. Updates that were not started are Skipped with the detail The run reached its time limit before this update was started; it is attempted in the next cycle. Catch-up runs outside the window and Patch Now use the 60 minutes.
  • Windows is installing something else. Before the agent hands an update to Windows Update, it checks whether Windows has an installation in progress, for example one that Windows started itself or one that an earlier run started. It waits up to 10 minutes for it. When Windows is still busy after that, the run starts no installation: the updates are Skipped with the detail Windows is still installing updates that were started earlier, so this run did not start another installation., and the next run tries again.
  • Long installations in a Patch Now job. The job stays Running for as long as an update installs. An update reads Pending until its turn comes, Installing while it is worked on, and gets its result as soon as it is finished, not at the end of the job. A Patch Now that is started while a scheduled run is still installing waits for that run for up to 60 minutes and then ends as Failed with Another patch run was still active on this device after 60 minutes.; start it again once the run has ended.
  • Agent updates during a run. A new agent version is not installed while a patch run or an installation started by the agent is in progress; the agent updates itself after the run, at the latest after 12 hours.
  • Agents before 3.3.0.12. The whole run (search, download and all updates) has 60 minutes. When they are used up, every update of the run is Failed with The installation run timed out after 60 minutes and was terminated., including updates that had already finished.

The status of a Windows update on the device's Updates tab (Available, Installed, Installed, restart pending) is what Windows Update on the device reports at each device synchronisation. It is not taken from the result of a run; a run records its own result in the Last run chip and in the patch history. The two can differ, for example Installed next to Last run: Failed when an update failed in a run and was installed another way later.

  • Dates in the update history. The History action of an update on the Updates tab opens its update history. Under the status, the dialog shows when the device last reported it (Reported by the device on …), and under Last run when that decision was taken (Decided on …).
  • Several updates under one KB number. When Windows Update lists more than one update under the same KB number, the update is Installed only when all of them are installed (server 3.3.0.12 or later, with any agent version). A run reports such a KB as installed on the same condition; when only part of its updates went in, the item is Skipped and its detail says so.
  • Rolled back. The update history records Rolled back when an update was waiting for the restart and is offered again without a pending restart, or when the device had reported it as installed and Windows offers it again (server 3.3.0.12 or later). The status stays Available, so the update counts as open. A newer update that Microsoft publishes under the same KB number, such as the monthly Malicious Software Removal Tool, is not recorded as rolled back.

macOS

With agent 3.3.0.11 or later, the agent installs macOS updates one at a time with softwareupdate -i <label>, in this order: first the updates that are not macOS itself (for example Safari), then at most one macOS update per run. The rules:

  • Proof of installation. An update counts as installed only when softwareupdate no longer offers it and either reported it done or lists it in its installation history. A failure message, an exit code other than 0, output without such proof, or a run without output for too long ends the update as Failed, with the output of softwareupdate in Details. Every update the agent handles gets its own result in the run history and in the job; with Patch All, updates the policy filters leave out are not listed in the job.

  • Open apps. softwareupdate quits the apps an update replaces, for example Safari during a Safari update, and waits when one of them does not quit. A run that stays waiting is stopped by the time limits and the update is Failed with that reason; the next run tries again.

  • Macs with Apple Silicon. A macOS update on Apple Silicon has to be approved by a user who owns the startup disk; the agent runs as root and has no such credentials. It therefore does not start macOS updates on these Macs. They are listed with the reason Needs user input, and the tray icon asks the signed-in user to install them from System Settings > General > Software Update (window texts on the macOS Notifications sub-tab of the policy). The window is not repeated within a day for the same updates; when one of them is due again, it lists all updates that are still open. Other updates, such as Safari, are installed by the agent. A Patch Now job in which some updates were installed and others need the user ends as Partially installed; one in which all updates need the user ends as Failed with a note that names them.

  • Intel Macs. The agent starts the macOS update itself. When softwareupdate reports it prepared, the update is listed as Installed, restart pending and the restart follows the Reboot sub-tab of the policy, or the reboot choice of Patch Now. After the restart the agent compares the installed macOS version with the update and records the result in the next scheduled run: Installed, or Failed with Not installed by the restart. A macOS update that the restart did not install is not prepared again by scheduled runs or Patch All; it is left to the user, or an admin selects it in Patch Now.

  • Major upgrades. An update to a newer major version of macOS than the one installed on the device (for example 26 to 27) is a major upgrade and is listed with the update type Feature. Scheduled runs install it only when the policy option Allow upgrades to a new major version of macOS in scheduled runs is on; Patch All never includes it; Patch Now installs it when it is selected and the confirmation is accepted.

    Whether an update is a major upgrade is decided per device. When a macOS update of the installed version and a major upgrade are both due, only the first one runs; the upgrade follows after the restart. An approval, manual or by an auto-approval rule, only makes the upgrade eligible; the policy option on each device decides whether it installs. The Software Update page of macOS can still offer the upgrade to the user, also when the policy holds it back; without an MDM, NetLock cannot hide it there.

  • Restart. The agent requests a restart only when it prepared a macOS update or installed an update that softwareupdate marks as requiring a restart. A Patch Now job with Reboot if required that installed nothing does not restart the Mac.

  • Compliance. A major upgrade that the policy holds back is still an open update: it counts as pending in the compliance figures when the compliance scope includes its update type (Feature). Unticking Feature in the compliance scope of the Settings tab leaves such upgrades out, and Windows feature updates with them. The update type in the catalog is shared by all devices and is the one the last reporting device sent: an upgrade such as macOS 27.2 shows as Feature when a Mac on macOS 26 reported it last, and as a regular update when a Mac already on macOS 27 did.

7.8 What is not on this page

Several controls that other RMMs place on their patch management page are part of the policy in NetLock RMM.

  • Per-device or per-group exclusion lists. A patch is Rejected fleet-wide or not at all. To exclude a subset, use the Approval & Filtering sub-tab inside the relevant policy (Chapter 6.12), or move those devices to a different policy with stricter filters.
  • Rollout scheduling (maintenance windows, allowed days, time ranges). Configured on the Schedule sub-tab inside a policy's Patch Management tab.
  • Deployment rings. Configured on the Deployment Rings sub-tab inside a policy's Patch Management tab.
  • Reboot behaviour and user prompts. Configured on the Reboot sub-tab inside a policy's Patch Management tab.
  • Retry on failure. Configured on the Retry sub-tab inside a policy's Patch Management tab.
  • Notifications. Per-event patch notifications are toggled on the Notifications sub-tab inside a policy's Patch Management tab; the channels and recipients those notifications are sent through are configured in A.8 Notifications deep dive.

Patch management makes one global decision ("may this patch install anywhere?") and many per-policy decisions ("how do these particular devices install the things that are allowed?").

Permissions

Patch Management uses two permission flags:

  • patch_management_enabled: master flag. Users without this flag do not see the Patch Management navigation entry and cannot reach /patch-management. A user who has the flag can approve, reject, defer and delete updates and read every tab.
  • Patch management: auto-approval rules and settings (patch_auto_approval_manage): shows the Auto-Approval tab and allows saving the auto-approval rules, the auto-approval master controls and the Settings tab (SLA thresholds, compliance scope, history cleanup). Because these settings apply to the whole instance, saving them additionally requires that the account has access to every tenant.

The figures of the page follow the tenant scope of the account: an account assigned to a subset of the tenants sees the devices and updates of those tenants only, in every tab and dialog.