outlook 2016 for mac is off 1 hour after time change

Outlook 2016 for mac is off 1 hour after time change windows#

The only way I've found to resolve this incorrect synchronization problem is to delete the Google calendar being synchronized to, recreate it as empty, and perform a clean synchronization. The problem persisted even after I returned to my home timezone events that were first synchronized while I was travelling were never updated and were left with the wrong time. This occurred for events that I scheduled while in my home timezone, events I scheduled while in the travelling timezone, and events received that were scheduled for very different timezones by the creator (meetings with coworkers on different continents). Events that had already been synchronized to the Google calendar prior to my travel were left at their original times, but any new events that were received while I was traveling, or events that entered the synchronization window while traveling, were added to Google calendar with the wrong times. As a result, all devices viewing my Google calendar events were showing the wrong time for the event since the devices themselves were also accounting for the difference in timezones between my home timezone and my current timezone. A synchronization was performed and events were added to my Google Calendar using my default Google timezone, which was still set to my home timezone.

Outlook 2016 for mac is off 1 hour after time change windows#

It doesn't seem to matter what timezone the actual event was scheduled in/for.įor example, while I was traveling to a different timezone I had my Windows timezone set to the timezone I was in. If those timezones don't match for any reason, the times end up wrong. It appears that the Outlook event time is being retrieved assuming the current Windows timezone setting, then stored into Google Calendar using the default Google Calendar timezone setting. This same problem is easily demonstrable by modifying the system timezone of your Windows instance.

But I would assume that recurring events will need to be written as individual ones if they aren't already.Īlternatively, the program could come with a DST database (or use Windows's inbuilt one, if it exists?) to re-calc dates, though it would have to loop through recurring calendar items to find out which ones to adjust. If the events could be formatted/written with the 'original' event timezone instead of the timezone of the computer itself, that may resolve the issue. Or possibly you can get the original timezone? REST API docu says 'You can use the OriginalStartTimeZone and OriginalEndTimeZone properties on the Event resource to find out the time zone used when the event was created.' (Other APIs may have similar capabilities.) Not sure if it helps at all, you could force outlook to return events in a specific timezone if using REST API (see ). My google calendar is only correct half of the year for those appointments, sadly. I live in a country with no DST, and have long-running appointments with people in the US. I have the same issue, but for me it is not temporary.