DST 2007 changes - appointments pulled in 1 hour after tool ran?

[Sandy Wood]

Ran the Exchange mailbox update tool last night. Also patched the Windows OS
on each XP machine. This morning, some user calendar items are shown as
earlier by 1 hour for every one after March 11th. I've told our users that
this is correct and will be adjusted after March 11th when the OS Time Zone
changes. Am I correct in this assumption?

 

[K. Orland]

Are you running SBS or not?

 

[Sandy Wood]

No. Our Exchange server is running on Windows 2003 R2.

 

[K. Orland]

General order of updating for DST changes:

Apply and verify updates to server operating systems (KBs 931836 and 914387)

If you are running Outlook Web Access, Exchange Lotus Notes connecter, or
BlackBerry Enterprise Server for Microsoft Exchange , install the Exchange
Patch CDO.DLL (KB 926666)

Update your Windows client operating systems if they already have not been
updated using Windows Update or Windows Server Update Services (KBs 931836
and 914387)

Correct individual e-mail application calendars using the Outlook Time Zone
Update Tool (KB 931667)

For more information on daylight saving time changes, visit Preparing for
Daylight Saving Time changes in 2007.

Regarding Outlook, you didn't state the version. Some may require the TZedit
tool to be run:

Microsoft Office Outlook 2007

If you have installed Microsoft Outlook2007, you do not have to u se the
Time Zone DataUpdate Tool. However, we recommend that you runthe tool
because it includes many improvementsover the tool that is included with
Outlook 2007.

Microsoft Office Outlook 2003

Update for Daylight Saving Time changesin 2007 for Microsoft Office Outlook
(KB931667)

Update for Microsoft Office Outlook 2003 (downloadpage)

Microsoft Office Outlook 2002 Standard Edition

Update for Daylight Saving Time changesin 2007 for Microsoft Office Outlook
(KB931667)

Update for Microsoft Office Outlook 2002 Standard Edition (down load page)

Microsoft Office Outlook 2000 Standard Edition

Update for Daylight Saving Time changesin 2007 for Microsoft Office Outlook
(KB931667)

Update for Microsoft Office Outlook 2000 Standard Edition (download page)



http://www.itworldcanada.com/Pages/...1&ParaEnd=22&direction=prev&Previous=Previous

 

[Sandy Wood]

Thanks for the detail. We pretty much followed the correct steps to update
our Exchange server. We updated it in the evening and then updated all the XP
machines the same evening, only an hour later. I realize the order of
precedence was changed, but I don't think the OS update would cause any
issues since by the time the user logged in and opened Outlook, the patch
would've been applied for 2 days already.

I'm going to run the stand-alone Outlook tool this afternoon and see it that
fixes the issue. One other thing that may have created a problem was that one
of the user Calendars was a sub-calendar of her main Calendar. Not sure if
that has any bearing.

 

[K. Orland]

The order should be to patch the O/S on the Exchange server(s). Patch the O/S
on the workstations. Then apply the Exchange DST update.

You can use the following alternatives:
1) Run the Exchange Calendar update tool against affected servers or users,
or both
2) Push out the Outlook time zone data update tool to the clients and let
them update their own mailboxes
3)Run the Exchange Calendar update tool against all affected users, servers,
or both. However only modify recurring appointments. Then ask the users the
rebook single instance appointments that fall into the extended DST period or
ask them to run the Outlook time zone data update tool. I would recommend if
you use this choice that you have users print out their calendar during the
DST period so they don't lose data. This probably answers your original
question.
4) Run neither the Exchange or Outlook update tools. Tell the users to
examine their calendars and rebook as necessary.

I am not sure yet what happens if you patch out of order since I haven't
heard anything yet from anyone. I'll try to keep my ears open for you.

 

[Sandy Wood]

Thanks for the help on this one. It looks like we did everything in the
correct order yet we've got about 50 (out of 800) that didn't get fully
changed. The Exchange Calendar Update tool logs show changes made for each of
the 50, however further investigation (and a re-running of the Outlook Tool
on each system) showed that there were still calendar items that the Echange
tool did not find.

50 out of 800 is not too bad. We can live with it.