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 »
The Synology NAS systems have a variety of apps available for use and some of them have desktop components. It would be nice if the patch management component of RMM had the ability to patch Synology software, such as their Drive Client (formerly Cloud Station Drive).
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.
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
My company uses the Solarwinds RMM agent on many thin clients and since thin clients do not need to be kept up to date with the latest security patches we would love to see the ability to completely turn off vulnerability scans without uninstalling patch management.
I'd like to manage the Power Config on the remote devices via a DirectSupport tool, and have it incorporated into Rules.
This way, if devices are set to go to sleep, we could change it remotely for maintenance windows.
Further, if we could set sleep schedules via the agents and rules, we could then schedule maintenance windows to run, then let the devices sleep when there is no maintenance cycle.
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 »
One of the key features the current MDM is missing, is the ability to configure data usage threasholds, and send an alert when the threashold is met.
For better management in an VMWare environment, it would be great to have openvmtools installed.
It helps with better managebility and such.
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.