MSP N-central

Patch Status v2 - Not Approved Patches should not Report Failed

Patches with No Approval or Declined seem to report under "Nofiy if not actioned in X Days"

There should be an option to Not Report a Failure for Not Approved Patches


Example, if someone declines the Windows 10 Anniversary Update for a month, their patch patch status v2 should not report failed for that period. They shouldn't expect to have to adjust thresholds to avoid seeing Failures

Submitted by (@nic.daines)

MSP N-central

Windows 10 Major Build control in Patch Management

Right now it is very difficult to try and stop workstations from auto-updating to the latest build of Windows 10. We would like to hold out on these updates until after a few months of it being out then begin to steadily roll it out with clients. Right now the only way I've found to try to do this, with only partial success, is to search in patch management for the build number and decline the patches. Sadly even that ...more »

Submitted by (@psaeryn)

MSP N-central

Include Superseded information in patch reports

We issue reports to the clients on Patch status and we are getting a lot of patches in reports that have been superseded and the client is asking why there was no record of that patch being installed, on a monthly basis. It would be nice to show in the report that the patches have been superseded.


This would be for all patch reports in N-Central and Report Manager.

Submitted by (@jtolivar)

MSP N-central

Place device in downtime during reboot

In the Patch Reboot Schedule, there is an option to "place device in downtime during reboot" however it doesn't actually do anything useful. The expectation is that this would put the device into maintenance mode for the duration of that reboot so that all alerts would be suppressed. Instead, it just disconnects the agent (which happens anyhow) and I get hammered with alerts because the server is offline (like DUH). ...more »

Submitted by (@mark.hodges)

MSP N-central

Limits & issues with "Force Missed Patch Installation on Boot"

Dear N-central team, It's now become a requirement for ourselves and a set of customers, who are going through Cyber Essentials Security Certification, that all patches are installed within two weeks of their release date. In the Patch Profile you can check the box 'Force Missed Patch Installation on Boot' but there are various issues / limitations around this: -Although it says the machine will just install the missing ...more »

Submitted by (@steadders)

MSP N-central

PatchStatusv2 to give indication of when patch became available

please setup Patch Status v2 to give us an indication of when a patch became available to a machine


let this indication show up in the service details portion of notificaions


I would hope that if a patch was released 3 years ago but wasn't available to a machine until yetserday that it would count yesterday as the approval date, but this would give us another way to verify that.

Submitted by (@wmorgan)

MSP N-central

3rd party patches

It seems that 3rd party patches by defualt are downloaded even when 3rd party patching is not enabled.

When there is an agent running there are 3rd party patches downloaded in C:\Program Files (x86)\N-able Technologies\PatchManagement\ThirdPartyPatch


Would like to have them only available when the option is active

Submitted by (@m.kooij)

MSP N-central

Don't download approved superseded patches

I have found (especially with Windows 10/Windows Server 2016 server devices), that the following patches will be downloaded into the Agent Patch Cache (C:\Program Files (x86)\N-able Technologies\Patch Management\archive\): - Patches that have been set to "Approved for Install" which are not yet installed, and are superseded by other another patch that is also in the list of "Approved for Install" and "Not Installed" list. ...more »

Submitted by (@johnnyva)


11 votes

MSP N-central

Stop patch downloads to Agent Patch Cache if insufficient space

I have noticed that when a patch is set to "Approved for Install", the target device agent will download the patches even if that means it will use up almost all space on the C drive. i.e. a Device has 5 GB of patches to download and only has 5.5 GB free space on the C drive. The Agent will download all the patches leaving only 500 MB of space on the C drive. This could cause issues with services running on that device. ...more »

Submitted by (@johnnyva)