Outlook Recurring Meetings off by one hour during extended..

Any luck finding a solution?

"Will" wrote:

> 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.
>
> "waterboy" wrote:
>
> > 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.
> >
> >

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.



"Dcurtis" wrote:

> Any luck finding a solution?
>
> "Will" wrote:
>
> > 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.
> >
> > "waterboy" wrote:
> >
> > > 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.
> > >
> > >

On Mar 11, 3:40 pm, Will wrote:
> 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.
>
>
>
> "Dcurtis" wrote:
> > Any luck finding a solution?
>
> > "Will" wrote:
>
> > > 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.
>
> > > "waterboy" wrote:
>
> > > > 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.- Hide quoted text -
>
> - Show quoted text -

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

We are having this issue as well. However support from MS has come back and said:

I’m assuming that after applying the OS updates meetings are being created correctly and that it’s only existing meetings (either recurring or single instance) that are displaying as being +1hr in the calendar. If this is the case then it sounds like the existing meeting items have not been updated yet to be aware of the TZ change occurring and so will still think that DST ends on March 30th rather than the extended April 6th date (for AUS Eastern Standard).

To correct previous existing meetings that were created pre-DST update, rebasing needs to be run against these items via the Exchange update tool (KB941018), or via Outlook on a per user/client base using the Outlook version of the tool (KB931667).

If NEW meetings are showing as being incorrect +1hr, then what seems to be happening is that Outlook users have TZ information that do not match on the operating system and so the conversion from GMT to UTC occurring when being sent to Exchange is incorrect, which then has the flow on effect).

With regards to Blackberry, the same ExchangeCDO update (KB943068 if SP2) is required to be installed on the BES server just the same as all the other Exchange (FE/BE) servers since BES uses CDO to communicate with Exchange messaging.

(Names have been removed of course), hope this helps somewhat