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 No 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 No comments

104 additional answers

Sort by: Most helpful
  1. Anonymous
    2016-06-29T00:04:40+00:00

    I'm sorry for my late reply! I was expecting an email saying that you had replied but it never came.

    Yes, I'm creating an all-day event from my iPhone. 

    I live in Sweden i.e timezone UTC + 1:00.

    My Iphone has version 9.3.2.

    I've also reproduced it on my Ipad version 9.3.2.

     

    Susanne,

    Are only all-day events being displayed on the calendar on the wrong day?  For non-all-day events, are your meetings showing up in the right calendar time slot, just with the wrong time zone when you open the meeting?

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2016-06-29T00:01:25+00:00

    @JohnWang_MSFT can you please confirm if a fix has been released for Exchange 2010 since your last post? What is the KB issue number for the fix in Exchange 2013?

    Unfortunately, the time zone fix for EAS has not been backported to Exchange 2010, and there are no current plans to do so.  You can try escalating to the Exchange team through your support channel (it is a completely different team from the Outlook for Mac team).  The KB article is https://support.microsoft.com/en-us/kb/3099522#bookmark-issues, though I didn't see specific mention of the EAS bug.  The Exchange version numbers with the fix are 15.xx and later.

    Are meetings showing in the right slot on your calendar, even if the time zone is set to UTC?

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2016-06-28T21:09:06+00:00

    I'm sorry for my late reply! I was expecting an email saying that you had replied but it never came.

    Yes, I'm creating an all-day event from my iPhone. 

    I live in Sweden i.e timezone UTC + 1:00.

    My Iphone has version 9.3.2.

    I've also reproduced it on my Ipad version 9.3.2.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2016-06-28T01:59:27+00:00

    I'm having this issue here in Australia. Creating a calendar event on iOS shows up on Outlook for Mac as UTC 0 so the date at time is wrong. It doesn't have to be a recurring event for this to happen or an all day event. Any calendar event created on on iOS is read incorrectly on Outlook for Mac.

    The Mac Outlook client is 15.19.1 at the time of writing. Our Exchange server is Exchange 2010 14.3 (Build 123.4). 

    I am updating to the latest Mac client now, 15.23. @JohnWang_MSFT can you please confirm if a fix has been released for Exchange 2010 since your last post? What is the KB issue number for the fix in Exchange 2013?

    Thanks!

    Was this answer helpful?

    0 comments No comments