MCM 2.1 Release Notes

Fixed In This Release

This release fixes a problem in which MCM would generate spurious event IDs that WebCal could not process. Consequently, other WebCal clients like ConnectR would hang. This fix entails changes to the MCM code only. (48310)

If your environment includes both MCM and ConnectR users, you should also install the following software (if you haven't already done so):

Known Issues In This Release

  • After successfully syncing calendars with large amounts of data, MCM could consume a lot of CPU cycles and memory when a slow sync is triggered by an exception. (PR 46642)
  • If MCM is configured for SSL authentication and an unrecognized root certificate is encountered, MCM will not sync data nor will it provide adequate information about the problem. (46420)
  • Regardless of the attendee availability (Free/Busy) displayed in WebCal, availability always displays as "Busy" in Entourage following a sync. (PR 46370)
  • Even though MCM is configured to sync every 15 minutes, MCM might sync every 5 minutes if it is configured to sync with Entourage. (PR 46489)
  • In time zones with negative offsets (GMT -X:Y), recurring events set up in Entourage will display one less instance in WebCal. This problem occurs when you create the recurring event in Entourage with the end-date option configured and you synchronize. (PR 46231)
  • An all-day event created via WebCal and then synced to Entourage will be scheduled in Entourage for the day before. This problem is specific to Entourage 2004 only. (PR 46163)
  • Non-recurring meeting invitations that are accepted within WebMail/WebCal and then synchronized to Entourage will display the time zone as Casablanca, Monrovia. This problem occurs regardless of the time zone configured on the calendar server or in Entourage. (PR 46020)
  • The conflict resolver window will appear if a meeting invitation is read within both WebMail/WebCal and Entourage and then you sync. (PR 45487)
  • Occasionally if you create an event/to-do item via WebCal while a sync is underway, the item will not get synchronized to Entourage or iCal during subsequent synchronizations. (45107)
  • Once you reinstall MCM, the upgrade option will no longer be available within Leopard OS. (PR 45091)
  • With non-English locales, you cannot download the MCM installer from WebCal using the Firefox browser.
    Workaround: Use the Safari browser to download the installer.

Known Issues With Microsoft Entourage 2008 and iCal

The following are known problems with Microsoft Entourage and/or iCal, independent of the MCM application.

  • Following a sync, an all-day event created in WebCal displays in Entourage as an event scheduled one day prior. This is a problem with Entourage 2004 and Mac OS 10.5.5 only. (PR 46639)
  • Occasionally events created via WebCal fail to display in iCal without a calendar refresh. (PR 46164)
  • Duplicate meetings occur in Entourage in the following scenario:
    1. Schedule a meeting via Entourage and then sync
    2. In WebMail/WebCal, change the meeting time
    3. Sync the revised meeting back to Entourage using MCM.
      The meeting is duplicated in the owner's Entourage calendar.
    (PR 45899)
  • An attendee cannot respond (with an accept, tentative, or decline response) to a meeting request if the invitation is not read/opened in Entourage. (PR 45715)
  • If you create an all-day recurring event via WebCal, any exceptions you make to the event using Entourage will not be synchronized if the time zones on the calendar server and within Entourage differ. (PR 45699)
  • If you schedule a meeting via WebMail/WebCal and then sync, a message displays within Entourage informing you that the invitation has not been sent. (PR 45486)

Copyright © 2009 Mirapoint Software, Inc. All rights reserved.