Settings and activity

1 result found

1. Use Local Time Zone for Automation Profiles

   42 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   3 comments  ·  Ideas and Feedback » IT Automation and Patch Management  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   Under Review  ·  AdminProduct Team (Product Team, Atera) responded

   Hello, Thanks so much for submitting your idea! It’s currently under review by our product team, and should a decision be reached to develop it, we’ll keep you in the loop!

   An error occurred while saving the comment
   Daniel Smith commented  ·  Aug 7, 2023  ·  Edit…  ·  Delete…

   +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 :(

   Save Submitting...
   Daniel Smith supported this idea  ·  Aug 7, 2023