The VSA does not automatically adjust scheduled events for changes between standard time (ST) and Daylight Savings Time (DST). When a task is scheduled, the time zone used to schedule that task is converted into the time used by the Kaseya Server. Regardless of the time zone preferences set by the user in System > Preferences or whether agent time scheduling is used or not, once scheduled the task only “knows” the Kaseya Server time it is suppose to run.
The following workarounds are available.
Use the System Clock Used by the Kaseya Server – On Premises only - If the system clock used by system hosting the Kaseya Server is configured to adjust for DST, then scheduled VSA tasks will adjust as well. This option is not available with SaaS because the same instance hosts multiple tenants in different countries and time zones. DST adjustments differ for each country. SaaS instances are set to Greenwich Mean Time (GMT) and never change.
Schedule Once – On Premises and SaaS - The easiest method of managing ST/DST changes is to set the schedules once and plan to run them one hour earlier or later, depending on whether ST or DST was used. For example, in the United States, DST runs for the majority of the year, 238 days out of 365. So for the U.S., scheduling using the DST version of your timezone is recommended.
