Be aware: October 26 2014 Russian time zone changes and Exchange

We wanted to give you a heads up that depending on the version of Exchange you are running, there might be some impact to either names of time zones that are changing on October 26, or the way that actual meetings are displayed in affected time zones. Customers using our newer versions of Exchange, 2010 and 2013, can expect meetings to appear on calendars correctly (provided underlying operating systems have been updated). Customers who are running Exchange 2007 might see meetings displayed at wrong times.

We are committed to correct these inconsistencies in our December release wave.

Update 11/11/14: We have just announced that the November 2014 Exchange releases are being delayed by one month, to December. Please see this. We updated the above wording accordingly.

Please see KB article 3004235 for more information.

Nino Bilic

Comments (6)
  1. Mike Crowley says:

    Russians getting rid of DST – I’m jelly!

  2. Martin says:

    Thanks for the hint.
    We use Ex2007 servers in several countries, but Russia is using Ex2010 servers. If I understand correctly, we only need to update the underlying OS? Or will the Ex2007 mailbox users in other countries be affected (if they scheduled meetings with colleagues
    in Russia)?

    Many thanks.


  3. RU says:

    Thanks for the information.
    Mentally preparing myself for bad day or week.

  4. EWS Exception says:

    Actually after I have installed this KB, I am getting the "Microsoft.Exchange.WebServices.Data.TimeZoneConversionException" on call of "ExchangeService.GetUserAvailability" method: "Unable to convert from (UTC+03:00) Moscow, St. Petersburg, Volgograd (RTZ
    2) to UTC."

  5. Bob Hyatt says:

    Is exchange online affected ?

  6. filipp says:

    Does this only affect OWA-Users (where Exchange does all rendering) or will this also have an affect on Outlook-Users? I’d assume, that for Outlook-Users, Exchange doesn’t care about UTC-Offsets, but leaves this up to the client.



Comments are closed.

Skip to main content