Last Updated: May 07, 2020
RMS Enterprise Scheduling Interface for Exchange
Current Version: 1.0.41
Release Date: March 2020
-- RMS Enterprise Server version 4.7.0 or later.
-- Microsoft Exchange 2013 SP1.
-- Microsoft Exchange 2016.
-- Microsoft Office 365.
Changes in this release
--Support of Java 11 using bundled JRE.
--Fixed the 'plugin service failure to start/stay running in Windows Server (German Language)' issue
--Fixed the 'mailbox communication failure not reported in the hotlist' issue
--Fixed the 'single resource sync issue caused the entire job & synchronization failure for remaining resources'
-- Any prerequisite Java version should not be uninstalled, if we are upgrading to v1.0.41.
After upgrade, users could uninstall existing Java as v1.0.41 is using bundled JRE.
-- Exchange Configuration Application needs to be closed before uninstallation.
-- Single meetings that start more than 23 months in the future will not be
synchronized into RMS. Also, the occurrences of recurring meetings will
be limited to 23 months into the future even if the recurrence pattern
specifies "No End Date" or has a defined end date that falls beyond 23
months into the future.
-- Changing the attendees of an existing meeting doesn't actually modify the
meeting in Exchange. This is simply how Exchange behaves. As a result,
the meeting will not be resynchronized to RMS and the attendee changes won't
be reflected in RMS. Something such as the subject, body, or date/time must
be changed in order for a synchronization to RMS to occur.
-- Ending or extending a meeting from the touch panel will only update the
resource's calendar. The meeting time will not be adjusted on the
calendars for the organizer and attendees.
-- Exchange Configuration Application needs to be closed to start uninstallation process.