SOON.EXE started scheduling jobs for 1 hour earlier than they should be after Daylight Savings Time came into effect on Sunday. So executing “SOON 30 sample.exe” at 10 AM executes AT 9:00:30 sample.exe. This is true when executing from my server machine through SQL Server’s xp_cmdshell. But if I execute interactively to run on my server, ala “SOON \\myserver 30 sample.exe” at 10 AM it executes “AT \\myserver 10:00:30 sample.exe” correctly.
The obvious place to look is the “Adjust for Daylight Savings Time” box in the Time Zone tab of Date/Time applet. But these are set correctly for all of our servers. We do use NTPDATE to keep the clocks in synch on all our servers.
Have checked MS KB articles to no avail. Any ideas out there?
