Since the Daylight Savings time change on 3/13 we have been noticing some scheduled tasks running 1 hour earlier than expected. This is now happening with tasks on both Windows Server 2016 and 2019 boxes that are patched up until last month. Once the task runs early it continues to run early for each subsequent daily run.
The strange part is DST moved us 1 hour forward so jobs running 1 hour earlier than expected do not make sense to me.
DST just happens to be the only change in our environment and so I am focusing currently on that as a related cause.
The job history prior to DST change shows, for example, the job starting at 0200. After the DST change the job task still shows a trigger of 0200 but the job history shows the jobs are running at 0100. This is not all tasks on the box just a small number of tasks
Running SCHTASKS on the server shows the same trigger time as the task scheduler interface, which is the correct trigger time. But its the job history tab of the job that shows its running 1 hour early.
For the 3 jobs that this is happening on we are noticing a trend of the scheduled trigger to run the job Tuesday through Saturday. I dont see any other correlation between these jobs.
We have restarted the box as well as changing the start time of the job and the job continues to run 1 hour early.
Next up is just to delete the job and recreate it. Anybody experience anything like this?
