Use Local Time Zone for Automation Profiles
The ability to schedule automation profiles to run based on a device's local time rather than using the General Time Zone setting. For example, an OS patching automation profile that runs at 11am will run at 11am across every country/location regardless of timezone difference. Currently, the limitation is that if the profile is run at 11am and your selected timezone in Atera is set to '(UTC) - Dublin, Edinburgh, Lisbon, London', then this creates a problem where the profile runs in the middle of the night for users in Australia, which then means they won't get patched at the right time. The only workaround for this is to have a new automation profile for each site/country which means more work for us in creating them and managing them. Most other RMMs do this by default so this shouldn't be missing in Atera.
Eric
shared this idea
Congratulations on helping shape Atera! The feature you requested is currently being considered for development. Please be patient as the process can take a while or even stall to make way for other features. We’ll update you once it’s been implemented and released!
-
Mike Dacre
commented
I have clients all over the world and typically end up making my own scripts to handle this. "Dave McPherson" mentions that this should be happening already, and it does, based on the windows scheduler typically but not for everything.
-
Daniel Smith
commented
+1 this is total pain!
So I've just started a trial of Atera with a view to migrate dozens of endpoints out of pulseway and hit this issue.
I have clients in 4 timezones with different prod and dev server patching schedules. To work around I need 8 automations (4 timezones * 2prod/dev) and need to attach each automation to the specific server in that timezone.
The bigger issue is when daylight savings changes across all of these I need to do the mental maths and modify them to maintain the same outage window date/time. Not fun :(
-
DAVE MCPHERSON
commented
You mean to say that the automation does not run based on the local time of the agent? We don't have this issue, as we have a small, local, customer base, but I would have thought that the automation would run at the time set, and it would be the time based on the agent.