Overall improvement of Patch Management
This needs an overhaul and the following additional features would be an improvement.
Scheduled Device Scan for Updates
After updates have completed If a user is logged in prompt to reboot every set period of time until reboot accepted.
After Updates If a user is not logged in attempt to reboot to schedule based on local device time.
Allow local admin credential injection in order to force updates through that require a device to not just be turned on but logged in to work.
Approve or Reject updates and set priority for security and critical updates based on the CVE.
See status of patching without having to run a report on each customer. Under the customer there should be the option to see devices with failed, installed, pending updates etc. and color coded for ease of use.
Updates for 3rd Party applications that have not been installed with chocolaty.
These improvements i think would make a big difference to managing clients day to day without the need for full blown vulnerability scanning.
Stavros Patiniotis commented
Please make sure a report indicating client,device,software,software status (eg outdated, latest, cve exists etc).
luxminarayan luxminarayan commented
There must be a feature to filter updates based on date, So that we can install latest patches on a testing group.
And after one Month we can install these updates to production group
Primary Freight commented
This all very needed, and Scott is asking for the very things I was about to ask for. The only extra thing to mention is more control over reporting patches. We should be able to fully exclude patches to the point of not being reported at all.
Thank you, Scott.
InnerVision Computer commented
Also the ability to get all Windows updates including cumulative updates, let us make the choice which ones we want and don't want, but please lets grab them all.
Mark Bouman commented
this festures look nice , We could use this
AdminProduct Team (Product Team, Atera) commented
Thanks for the great ideas. We are currently working on increasing our patching capabilities, including some of the ideas you've listed.
Regarding software updates, we currently update a list of commonly used software regardless of their installation method. For more information please refer to the knowledge base article: https://support.atera.com/hc/en-us/articles/360015462840-Automate-Software-Patching-Via-Chocolatey-and-Homebrew-