The page you requested does not exist. A search for microsoft windows 2007 spring daylight savings time dst changes patches mess resulted in this page.

Microsoft Windows 2007 Spring Daylight Savings Time (DST) changes/patches/mess

If you are reading this, its probably too late, but just to have somewhere to keep it for future reference.

Microsoft Windows did not handle the DST date change (U.S. Congress changed the date that Daylight Savings Time takes effect this year). Outlook apparently keeps appointments in two different ways... repeating appointments are kept with an offset from GMT (Greenwich Mean Time) and will handle the change just fine. Individual appointments were kept with a hard coded local time reference and no GMT offset. These would be off an hour for appointments in the window between the new date (March 11) and the old date (April 1).

There were a variety of patches that affect all of this:

  • Windows Client OS patches (XP, 2000, etc.)
  • Windows Server OS patches
  • Exchange server patches (?)
  • Blackberry server patches
  • Blackberry device patches
  • Windows Exchange mailbox "fix" tool that could be run on the server or the client

Much more could be learned here:

http://support.microsoft.com/kb/931667

http://support.microsoft.com/kb/931836/

These installed:
    C:\Program Files\MSECache\TZMove\
    C:\WINDOWS\Installer\2959b04.msi
   
    uninstall:
    MsiExec.exe /X{95120000-0038-0409-0000-0000000FF1CE}

    TZMoveFolder = C:\Program Files\Microsoft Office\Office12\Office Outlook Time Zone Data Update Tool\

%INST% tzmove.exe /quiet
“%PROGRAMFILES%\Microsoft Office\Office12\Office Outlook Time Zone Data Update Tool\tzmove.exe” /quiet

We created a package that installed the Windows client OS patch, installed the Outlook Time Zone Data Update Tool, then ran the Update Tool silently. We uses SMS to send this update to all machines and had pretty good success. The initial pass at the package called the Update tool with the long filename and that failed... so we had to create and send out a supplementary package that re-called it with the short filename.

Blackberry updates were problematical, and depending on timing of when updates were made and when appointments were scheduled (you made an appointment on your Blackberry which had not received the patch, but your client workstation had, but the server hadn't, etc.) you could get appointments up to TWO hours off.