This project has moved. For the latest updates, please go here.

Timezone is not saved


Use Outlook -> Google one way sync.

Outlook Google Calendar Sync create google events without timezone.
So after other countries change to light saving time, events in Google are nor correct.

  1. Event created by user from different (origin) counery and in different timezone.
  2. Sync to Google.
  3. Google event is created with current time and zone, not with origin time&zone.
  4. Google event does not show that origin country change to light saving time.
Before light saving:
Look at Outlook: Event starts at 12:00
Look at Google: Event starts at 12:00

After light saving:
Look at Outlook: Event starts at 11:00 (!!!)
Look at Google: Event starts at 12:00

Possible solution: create events with origin time&zone.


phw198 wrote Apr 1 at 9:58 PM

What version of OGCS are you on? Lots of timezone improvements in the recent Alphas...

mkjyhuniolkj wrote Apr 6 at 9:31 AM


Last version -

mkjyhuniolkj wrote Apr 6 at 10:54 AM

Nothing changed with version 2.3.5. May be i should somehow resyncronize calendars.

mkjyhuniolkj wrote Apr 11 at 11:35 AM

I removed Google calendar and re-synced from scratch. Outlook contain master data.

Google events created without timezone. So in Google they are one our later that in Outlook.

mkjyhuniolkj wrote Apr 21 at 9:55 AM

Still having this issue on 2.3.5

How can i help with it?

phw198 wrote May 6 at 10:07 PM

Ah right, now I've reread your issue....and I don't think there's anything that can be done about it :(

I had exactly the same problem: invites created for a recurring series by someone in the US and for the 2 weeks where our DSTs were off (the UK moved 2 weeks later than the US), the meetings were off by an hours in that period.

Unfortunately, Outlook/Windows/MS calculates the local time of the calendar item into UTC when it arrives, with a timezone offset. This is what you see in step #3 of your opening post. The fact that this offset can change seems to be lost on MS and there's no way to force it to recalculate. So, with the data available to me through the API, OGCS is doing the right thing.

Can you confirm the issue was only apparent between 12 March (US DST) and 26 March (UK DST)?