Advanced options in IT automation profiles (scan and reboot window)
Support told me that new updates on servers will be searched at the start of the IT automation profile which leads to
- higher bandwidth usage
- more time for applying patches
- reboot time which may is outside of customer's window
What we need:
Scan window: set time window for scanning (e.g. on day of patching in the morning/afternoon)
Patch window: set time window for the execution of the patches
Reboot window: window for rebooting (last reboot no later than X:YY)
Patrick Fasser
shared this idea
-
Bart Ilg
commented
We face issues with the current patch management options. We try to schedule our patches at night to avoid impacting users, but this doesn't work for many laptops that are powered off in people's bags. The new automation queuing feature helps with this quite a bit, but takes too long to apply updates in many cases. Users will begin working and then an hour later the machine will suddenly reboot on them. We would like the option to force the machines to reboot at night, but to allow users to defer a reboot if it arrives during business hours.
-
John Dickinson
commented
We have had several servers where the overnight patching was slow resulting in the server rebooting during work hours.
Can a 'time window' be added so that reboots after patching are NOT performed outside of that time window?
-
Michael Fahey
commented
A time variation option to avoid high bandwidth usage at a single site. Vary by x minutes or hours.
Options WHEN to download updates vs during update process. Could download at a specific time of day with some time variation. -
Patrick Fasser
commented
More than 9 months gone and no further information on what's going on with this idea and others from automation profiles.
These advanced options are still a must-have. Other RMMs are ahead of Atera, again.
-
Mark Bouman
commented
this would be very helpfull