Outlook Recurring Meetings off by one hour during extended DST per

[waterboy]

recently users noticed that the recurring meetings in their calendars are off
by an hour during the extended dst period (march9-april 6)

example: a meeting is set to recur every week on tuesday at 2pm. it will
display correctly before and after the 4 weeks of extended dst time. During
the affected 4 weeks the meeting will display incorrectly at 3pm.

All the attendees are showing the incorrect time except the organizer's
calendar. where the time is correctly shown at 2pm consistently.

the latest microsoft patches have been applied to both workstation(windows
xp) and exchange server(server 03). I have ran multiple patches, tools,
tzmove, tzedit, etc.

the issue still persist, any insights? thank you, your time is much
appreciated.

 

[Will]

I feel your pain. Some of my PCs are showing the same behavior. All PCs are
patched. They did not have this issue last year during DST. I assume
Exchange Server is correctly patched or else everyone would have the issue
instead of a small number of users??? No one seems to have any suggestion
for a fix once the fact that they are already patched is made clear. I
suspect this issue is about to blow up for Microsoft as we approach March 9.
I'll probaly call Microsoft paid support today. I'll post back if I get a
solution.

 

[Dcurtis]

Any luck finding a solution?

I feel your pain. Some of my PCs are showing the same behavior. All PCs are
patched. They did not have this issue last year during DST. I assume
Exchange Server is correctly patched or else everyone would have the issue
instead of a small number of users??? No one seems to have any suggestion
for a fix once the fact that they are already patched is made clear. I
suspect this issue is about to blow up for Microsoft as we approach March 9.
I'll probaly call Microsoft paid support today. I'll post back if I get a
solution.

 

[Will]

I called Microsoft support on Friday. I started with their Outlook group.
After their Outlook group determined my PC was correctly patched they
transferred me to Exchange support. Exchange support acknowledged they have
some unresolved DST issues they are researching. They suggested that BES may
be playing a part in some of the problems they are seeing and wanted to know
the version of cdo.dll on the Exchange and BES servers. They gave us a
possible fix but my Exchange group has not responded back yet as to whether
they are going to try it. My advice is for you is to call Microsoft product
support - the call for us was free because this is an unresolved issue on
their end.

 

[tiztiz]

I called Microsoft support on Friday.  I started with their Outlook group.  
After their Outlook group determined my PC was correctly patched they
transferred me to Exchange support.  Exchange support acknowledged they have
some unresolved DST issues they are researching.  They suggested that BES may
be playing a part in some of the problems they are seeing and wanted to know
the version of cdo.dll on the Exchange and BES servers.  They gave us a
possible fix but my Exchange group has not responded back yet as to whether
they are going to try it.  My advice is for you is to call Microsoft product
support - the call for us was free because this is an unresolved issue on
their end.






- Show quoted text -

Has anyone had any luck with solution, or know if Microsoft has
figured out a resolution??