MSP N-central

Auto Approve Updates with Missing Meta Data

Sample Patch Feature update to Windows 10, version 1803 Description: Install the latest update for Windows 10: the Windows 10 April 2018 Update. KB Number: 4345421 Release Date: 2018-07-17 Classification: Upgrades Severity: Unspecified Status: Needed Approval: No Approval Products: -- Superseded: No Removable: No Restart Behaviour: Can Request Reboot Request User Input: No Installed Exclusively: ...more »

Submitted by (@nic.daines)

MSP Remote Monitoring & Management

Define patch installation settings for Microsoft Updates

I would like to see the features similar to those that are available in ConnectWise available in SolarWinds RMM, such as Microsoft Update Policies. Microsoft®️ Update Policies allow you to define the patch installation settings for Microsoft updates. A single Microsoft Update Policy can be applied to one or more patching groups. You can define pre and post install scripts as well as optional settings such as daytime ...more »

Submitted by (@john.cottier)

MSP N-central

Linking Patch Management Windows

Not sure if this has been previously posted but it's similar to something I have previously requested for the same reasoning. I think it would be a nice touch to Patch Management if you could schedule the windows to run after a previous maintenance window. So, for instance, if the pre-download takes 1.5 hours, it will start the installation as soon as the pre-download is done. Or, failing that, it just starts it after ...more »

Submitted by (@sabir.ahmed)

MSP N-central

Patch Management Notifications

I think we need to be able to configure notifications for end users to alert them that Patch Management will proceed on a given day. It will serve as a reminder to leave their PCs on as well as to save their work - might be worth making the notification itself customisable in the content. Currently, I've found two ways to notify users. One is through the patch profile but it will only alert users if a reboot is required. ...more »

Submitted by (@sabir.ahmed)

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)