The onset or passage of Daylight Savings Time causes recurring DS jobs to run either an hour early or an hour late
|Article:TECH11927|||||Created: 2006-01-17|||||Updated: 2011-03-17|||||Article URL http://www.symantec.com/docs/TECH11927|
|NOTE: If you are experiencing this particular known issue, we recommend that you Subscribe to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made.|
If a job is scheduled to run at 9:00 every morning, the job will run at 9:00 until Daylight Savings Time takes effect or passes. The time of year the job was scheduled will become the reference point from which the job's scheduled time changes with the onset or passage of Daylight Savings Time.
For example, suppose a job is scheduled to run in December at 9:05, and then repeat in 22 weeks; this should put it in April or May, after the time has changed. When the job runs the second time, it will run at 10:05. Conversely, if the job were originally scheduled to run in April at 9:05 and then again 22 weeks later, it will run in December at 8:05.
Deployment Solution 6.9 (all builds)
Deployment Server bases job scheduling on UTC and GMT. Consequently, variations in local time caused by Daylight Savings Time are ignored.
This behavior was purposefully implemented so as to avoid complications that arise over job scheduling across time zones.
Logged in Littlebuggy (Altiris - Lindon, Plymouth) database
Development has refused to address this as a defect because it is the product working as designed.
See CRT notes from February 23, 2011.
Article URL http://www.symantec.com/docs/TECH11927