Microsoft Outlook 2010 Forum

This is a community forum and not official technical support. — If you need official support: Contact Us

The following comments are owned by whoever posted them. We are not responsible for them in any way.

Back to Threads Reply to Thread

Time zone problems for Moscow time

At the moment ("winter" period), it works as follows:

  • my system time zone is Europe/Moscow. It is UTC+4. We do not have DST anymore.
  • Outlook thinks my time zone is Asia/Muscat. It seems to be similar UTC+4, but Outlook thinks it is not!
  • When someone sends me a meeting request, I see it with one hour offset (it is one hour later).
  • If I send someone a meeting request and select Europe/Moscow time zone manually, it appears in my calendar one hour earlier.

I am pretty sure everything is fine on Exchange side, we have all time zone updates installed.

Anyone else having similar problems? Is there a way to fix?

arkanoid wrote:

At the moment ("winter" period), it works as follows:

  • my system time zone is Europe/Moscow. It is UTC+4. We do not have
    DST anymore.
  • Outlook thinks my time zone is Asia/Muscat. It seems to be similar
    UTC+4, but Outlook thinks it is not!
  • When someone sends me a meeting request, I see it with one hour
    offset (it is one hour later).
  • If I send someone a meeting request and select Europe/Moscow time
    zone manually, it appears in my calendar one hour earlier.

I am pretty sure everything is fine on Exchange side, we have all
time zone updates installed.

Anyone else having similar problems? Is there a way to fix?

Okay, there are a few things to consider. The first most horrible thing is that Outlook 2010 is known to have tons of problems with time zones (I went out reading thinking I'd come across one simple fix for this and found more problems than there are fixes).

There are three places where the time for something in an email/meeting/etc can become borked:

Operating system time, email server and email reader...

I assume it's happening somewhere within Outlook though. I think that is probably because of the more recent removal of DST in Russia.

The first thing you'll want to do is make sure that you've applied Service Pack 1 to Office 2010.

The second is to consider applying this tool from Microsoft:

http://www.microsoft.com/en-us/download/details.aspx?id=17291

It's meant for other purposes but should update the rules of time zones within your bottle.

You can try disabling the use of DST within your Outlook bottle (note that I haven't tried this so your mileage may vary):

...Being that the situation you describe sounds like the machines
are using the DST rules, I would begin by making sure that DST is
definitely being disabled.

Go into Regedit:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation

Add a new DWORD value with the name "DisableAutoDaylightTimeSet"
--Set its value to "1". Which equates to "Disabled".

It would be highly helpful if you posted back anything that did or did not help you for future users. Here in the states we have very unfortunately not gotten rid of DST but the rules for it keep changing, I'm certain others will encounter this issue on a semi regular basis.

Articles for a good read on this issue:

http://social.technet.microsoft.com/Forums/en-US/winserverGP/thread/3e5adc56-7580-497e-a972-81d3b25a3e57
http://www.slipstick.com/outlook/calendar/appointments-and-time-zones/
http://support.microsoft.com/kb/982987
http://support.microsoft.com/kb/2507003

Thanks Caron!

Unfortunately I cannot try now if this helps -- while we discussed that, "old" Russian time zones were switched to DST, and while it happens the problem does not appear. We have to wait for the next winter 😊

arkanoid wrote:

Thanks Caron!

Unfortunately I cannot try now if this helps -- while we discussed
that, "old" Russian time zones were switched to DST, and while it
happens the problem does not appear. We have to wait for the next
winter 😊

Well, if you get to try it and something works, be sure to post back! Until then we'll hope that the problem maybe solves itself...

😉

Seems that it is fixed now, but I am not really sure which change led to the fix 😉

CrossOver Forums: the place to discuss running Windows applications on Mac and Linux

CodeWeavers or its third-party tools process personal data (e.g. browsing data or IP addresses) and use cookies or other identifiers, which are necessary for its functioning and required to achieve the purposes illustrated in our Privacy Policy. You accept the use of cookies or other identifiers by clicking the Acknowledge button.
Please Wait...
eyJjb3VudHJ5IjoiVVMiLCJsYW5nIjoiZW4iLCJjYXJ0IjowLCJ0enMiOi02LCJjZG4iOiJodHRwczpcL1wvbWVkaWEuY29kZXdlYXZlcnMuY29tXC9wdWJcL2Nyb3Nzb3Zlclwvd2Vic2l0ZSIsImNkbnRzIjoxNzM0NzIyMzMzLCJjc3JmX3Rva2VuIjoiUWFKTUZlOGhCRVpQU2RmZyIsImdkcHIiOjB9