As we get closer to the DST change here in the US, we have received some reports from a few customers that the system time erroneously reverted back an hour last Sunday (October 28). On these systems the customers did have KB931386 and / or KB933360 installed. What we have found from reviewing the data provided by these customers that the affected clients appeared to have some unexpected registry values, as shown in the keys below (the bold / red sections are the pertinent values)
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation\StandardStart: 00,00, 0a ,00, 05 ,00, 02 ,00,00,00,00,00,00,00,00,00
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation\DaylightStart: 00,00, 04 ,00, 01 ,00, 02 ,00,00,00,00,00,00,00,00,00
In order to recover from this scenario, you can use either of the recovery methods below.
Method 1 - Use the "Date & Time" Control Panel Applet: Assuming that the user has the rights to modify the system clock, they can do the following.
Method 2 - Use a single command-line statement OR the RefreshTZInfo.vbs script provided below: If the user does not have the rights to modify the system-clock, then either of the methods below can be used to push the refresh to multiple clients
First recovery option - single command-line statement: Add the following statement to a login script or batch file: control.exe timedate.cpl,,/Z Time Zone Name
For Example: control.exe timedate.cpl,,/Z Eastern Standard Time
Note that this method assumes you know the name of the time zone of the client that you will be running the command on. If you have clients in multiple time zones, see the second recovery option below.
Second recovery option - the RefreshTZInfo.vbs Script: Cut & paste the script below into notepad or another text editor, and name it RefreshTZInfo.vbs. Deploy this script via group policy or other deployment mechanism. See KB 914387 for more details about how to deploy this script. The script is also attached to this post as a text file.
After using either of the methods above, the registry keys for the affected clients should look like the ones below and properly modify their time correctly at 2:00 a.m. on November 4.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation\StandardStart: 00,00, 0b ,00, 01 ,00, 02 ,00,00,00,00,00,00,00,00,00
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation\DaylightStart: 00,00, 03 ,00, 02 ,00, 02 ,00,00,00,00,00,00,00,00,00
As always, please test any changes in a controlled environment before deployment to production. That's it for this post - the main Microsoft resources for DST are listed below. Until next time ...
Additional Resources:
EDIT (11/2/2007): Please see Microsoft KB Article 944524 for more information on this issue
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.