Calendar event showing up the wrong timezone

Anonymous
2015-03-16T12:28:08+00:00

Hi there, I refer to the screenshots below. The user, Pamela, sends out a calendar invite to both Jeff and Kok Guan, specifying the correct timezone UTC +0800. However, what Jeff views this event on his Mac running on Yosemite 10.10.2 is the UTC +0000 timezone, Monrovia, Reykjavik. The time indicated is displayed 6am instead of the actual 2pm, despite showing a notification that the event will commence at 2pm on Jeff's Mac. How do i go about correcting/removing the UTC +0000, Monrovia, Reykjavik, timezone stamp. Appreciate some help with this. Thanks!

Regards

Kenny

Outlook | MacOS | Legacy Outlook for Mac | For business

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2015-05-27T18:59:07+00:00

Unfortunately, the server update won't fix existing meetings automatically.  However, users MAY be able to fix it themselves if they find the original meeting invitation (could be in Deleted Items) and re-accept the meeting(s) with the "UTC" time zones.  (Let us know if that works.)

If that doesn't work, they will have to ask the organizer to re-send the invitation.  (Organizer just has to open the meeting on his/her calendar and click "Send Update." Make sure to "Edit Series" if it is a recurring meeting.)

Was this answer helpful?

60+ people found this answer helpful.
0 comments

104 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2015-06-02T18:04:18+00:00

    By the way, the fix is in Exchange server build v15.1.172 or later.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2015-05-27T12:41:09+00:00

    Hi all,

    The server fix for the "UTC/Monrovia" problem is being deployed this week on O365.  I have tested my own O365 account by creating meetings from iOS, and the time zone info is correct now in Mac Outlook.  If you are on O365 and are still seeing problems after this week, please post on this forum again. 

    Hi John,

    Since we have 60+ O365 users that are running on Apple's in the company and most of them are using iOS devices to set or modify meetings, I'll certainly keep your informed if this issue is still present after this server's fix.

    After a quick check right now, I noticed this server's fix are not "retroactively" fix the meetings that are already planned and that are affected by the "UTC/Monrovia" issue, is that correct? If we need to fix those affected meetings, what's the steps?

    Have a good day,

    Simon

    Was this answer helpful?

    0 comments
  3. Anonymous
    2015-05-26T22:20:10+00:00

    Hi all,

    The server fix for the "UTC/Monrovia" problem is being deployed this week on O365.  I have tested my own O365 account by creating meetings from iOS, and the time zone info is correct now in Mac Outlook.  If you are on O365 and are still seeing problems after this week, please post on this forum again.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2015-05-13T17:15:16+00:00

    The "UTC/Monrovia" time zone issue is caused when an EAS client (iOS, Android, Windows Phone) creates or modifies an Exchange meeting. There is some time zone information getting lost on the Exchange server.  We have tested a fix on the Exchange server and hope to roll it out soon when testing completes. 

    If you are seeing a meeting shift that does NOT involve "UTC/Monrovia," please install the 15.10 update that just came out yesterday. There is an issue with autoupdate, so it will not automatically be downloaded. You can download the update directly from here: https://support.microsoft.com/en-us/kb/3048682/

    Note: we have received differing reports regarding the behavior of existing shifted meetings after incorporation of the fix.  Some users have reported that installing the update was enough to fix the shifted meetings.  Others have had to re-accept the shifted meetings.  If neither of those options works, then the meeting organizer will have to resend the meeting invite by opening it from the calendar and clicking "Send Update."   In short, the fix should prevent any new meetings from getting into this state, but the impact on existing shifted meetings may vary.

    Was this answer helpful?

    0 comments