We really need to be able to auto approve patches for a particular vendor or product. For instance, auto approve all patches for Adobe products or auto approve all Java patches. Right now we can only choose to auto approve ALL non-microsoft patches that fall into a specific severity (critical, important, etc).
Reports are about showing the value of the service to the customer. As IT business owners we need to automate as much as possible. I would like to see automated monthly reports that contain all the other reporting mechanisms like workstations, patch management, remote support, automated task report, device hardware/software inventory, bandwidth/performance etc. This way the customer can see everything the service does ...more »
If a patch fails, there may be all sorts of information in the Windows event log or elsewhere explaining why. But the information presented to the technician is virtually nil - all we know is "patch failed/patch succeeded" - meaning we have to go to every PC with failed patches and interrupt the user's day with a support session to find out what went wrong. It'd be far more efficient if such information could be presented ...more »
Patch installation seems to fail frequently without any indication of why if fails or how to resolve the problem. Since "something" happens for the agent to know that the patch didn't install, couldn't that "something" be conveyed into the status info perhaps even with some useful information about what to do about the problem.
In earlier feature requests it was already asked to implement schedules like "2nd Tuesday of the month", etc. (Note: not by me)
As yet that request has not been full-filled...
In many cases it would be greatly appreciated if an approved patch can be scheduled at a given set date/time. Same like a planned reboot.
While we're able to view all of the patches that were installed or failed to install on a server/workstation, that report is really quite useless for our clients. We would like to be able to send a summary page that says here's the number of patches that were installed, here's the number of patches that are pending, and here's the number of patches that failed to install. We would like to generate that in a pie chart ...more »
Please add the ability to perform patch management for OSX computers. Currently, there isn't much that GFI can do for Mac computers.
One of the biggest benefits of patch management is that the customer no longer has to worry about Adobe Reader, Java, OpenOffice, Skype and a hundred other applications all flashing up a window saying "An update is ready, do you want to install it? You must reboot your PC to complete". Except - unless I've missed something - patch management doesn't disable the inbuilt update functionality of supported applications. ...more »
In Addition to the, very useful, Patch Pending Column it would be great to have an additional column for Patches Missing. That would mean that you could quickly get an overview of which systems/sites need work straight from the dashboard. Ideally some thing like:- Green Tick - No patches missing Orange Cross - up to 5 Critical Patches Missing Red Cross - More than 5 Critical Patches Missing Blue Dot - Non Critical Patches ...more »
LanGuard do have the option to to delay reboot after patching.
You might want to patch at 11 PM, but first want to reboot at 5:00 AM, after backup. Right now you do reboot right after patching.
Due to problems with "perform action immediately" staying flagged for all time and causing problems with patches and reboots happening out of sync on machines when they are first added to N-Central. Instead I'd like an option to run patch on demand against whichever machines I like for a specific patch or patches instead of having it just do ALL patches that are approved but needed.
during the patch decline process we'd like to have a field to notate why it was declined and have that show up on all the patch reports. We have to keep track of declines, their reasons and ticket numbers for clients, and in Kaseya we could just enter that information into the system while declining it and report on it. Would be great to see this functionality in N-Central.