Patch approval
Ability to approve patch for release date (install only if before date or older than days).
Ability to don't approve specific ones (es. do not approve KBxxxxxx).
We usually postpone installing patches on clients for a few days and manually approve the patch for servers, blocking approval of patches based on their release date.
This allows us to test them and block the installation of specific patches in case we encounter problems.
Daniele | WeDigitale - Supporto Tecnico
shared this idea
Great news! This feature has been released! Thank you for helping shape Atera. You can learn more about our new patch approval here: https://support.atera.com/hc/en-us/articles/7887279377564-Patch-Approval
-
luxminarayan luxminarayan
commented
This is really a very. critical feature.
There must be option to install some particular type of alerts which are older than particular days.
This is .really very helpful if we need to test updates on a particular group of computers then then we can choose to install updates which are older than 30 days to ensure critical systems get only tested updates -
Andrew
commented
This is very important, currently the entire patching interface operates against all logic. Turn off windows updates, and let Atera perform the exact same role (explicitly install all available updates on a schedule) makes no sense what so ever.
We need the ability to select which updates to install, and do it when we choose. Atera should not be blanket approving all available patches, with an exemption list.
Look at WSUS functionality as an example, this is ideally on a basic level what Atera should be offering, otherwise this feature is quite literally pointless and offers no value.