We need to ability to run Patch on Demand as a Patch Self-healing option so that when an endpoint comes online and patch monitoring is in a failed state, it runs Patch On Demand.
i would like to have the ability to schedule patches by the X Monday on the month
a few larger clients need this scheduling.
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 »
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 »
Patch Management / Languard should show Date Installed, even if not installed by Languard. Many of the patches have the information available, e.g. when querying Windows Update. It is nice to know if Languard installed a patch, or not, so perhaps add another column to South Pane for that indication.
This is not really a feature request but more of a bug! However, Solarwinds MSP Support suggest that I add this bug into here. There is an issue where if a patch has been identified by N-able Patch Management as Needed / Not Installed, and then someone manually installs this patch on the device itself, then the Patch Management system will not detect this and the patch will remain as Needed / Not Installed. What SHOULD ...more »
Over the Christmas period and other holidays my company occasionally requests a patch freeze - to prevent issues occurring when we have minimal staff in. An option to halt patching with one switch - or to be set via a paused time frame across all the customers we support would be ideal as currently I would have to go through and adjust each individual one.
I have noticed that if you approve a patch for install. Then the device discovers that this patch has been superseded, the original patch is removed from any patch reports and in the Patch Management, and it still gets installed. There is no way to track what has been installed when it has been superseded. So a step by step scenario would be: 1. Patch is detected i.e. Patch1 2. Set Approval to 'Approve for Install' ...more »
it would be extremely handy to be able to, at the very least, export the selected customers from the rules grant customer/site access tab, at the very most, have a report that will show me the associations between customers and rules, allowing me to pick which customers, or which rules I want to run the report against. In particular I need this for all of my patch management rules as we currently have to audit patch ...more »
When I re-apply a patch approval rule, I need to be able to tell when it is done applying and what all was changed - if anything.
Associated with ticket # 00897232.
We have a patch policy for each day of the week that is applied to various customers. Say for example on a Monday we have 15 Customer sites that all patch over night on the "Monday Night Patch Policy". I want a report that is ran automatically at the end of the maintenance window that lists all of the devices that should have been patched, whether they patched on or not and which patches have installed or failed. This ...more »
Add the functionality to recognize whether a device is set to defer updates and accept patches adhering to the requirements accordingly.
This should prevent buggy OS patches affecting software without an update which fixes it already existing.