[
https://issues.apache.org/jira/browse/OPENMEETINGS-1316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15115071#comment-15115071
]
Evgeniy edited comment on OPENMEETINGS-1316 at 1/25/16 11:38 AM:
-----------------------------------------------------------------
In configuration set default.timezone in Europe/Moscow
All users settings set Europe/Moscow too.
Server Exchange 2013 have actual timezone. Client Outlook 2013 too.
See iCal letter:
!tz.png!
What could be the problem?
was (Author: evgeshah):
In configuration set default.timezone in Europe/Moscow
All users settings set Europe/Moscow too.
Server Exchange 2013 have actual timezone. Client Outlook 2013 too.
See iCal letter:
!tz.png|thumbnail!
What could be the problem?
> Older timezone's in OM
> ----------------------
>
> Key: OPENMEETINGS-1316
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-1316
> Project: Openmeetings
> Issue Type: Bug
> Components: UI
> Affects Versions: 3.0.7
> Environment: CentOS 6.7 x86-64
> Reporter: Evgeniy
> Assignee: Maxim Solodovnik
> Labels: time_zone
> Fix For: 3.1.0, 4.0.0
>
> Attachments: tz.png
>
>
> OM used out-of-date timezone information
> For example from /openmeetings/languages/timezones.xml
> {code}
> <timezone orderId="11" name="Etc/GMT+4" label="Moscow, Saint Petersburg,
> Georgia, Armenia, Azerbaijan, United Arab Emirates" iCal="Europe/Moscow" />
> {code}
> This file has information about where to store information about time zones,
> but it is false.
> {quote}
> This file is loaded during installation to the database table "om_timezones"
> of OpenMeetings.
> {quote}
> Table "om_timezones" in the database does not exist.
> Russian time zones have been changed 26.10.2014. Now Moscow is Etc/GMT+3.
> I update OS tzdata and java tzdata (with tzupdater.jar) to tzdata2015g. Used
> jre by oracle (1.8.0_51).
> This problem affects the scheduler iCal and incorrectly sets the meeting in
> MS Exchange/Outlook. How to fix it?
> h6. (sorry for my English)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
