Chat now with support
Chat with Support

Coexistence Manager for GroupWise 1.7 - Release Notes

Quest® Coexistence Manager™ for GroupWise 1.7

Quest® Coexistence Manager™ for GroupWise 1.7
These release notes provide information about the Quest® Coexistence Manager™ for GroupWise release.

About this release

Coexistence Manager for GroupWise (CMG) provides rich directory, email and calendar coexistence features between Novell GroupWise and Microsoft Exchange—both on-premises servers and hosted Exchange environments like Office 365. CMG can be deployed either for a finite transition period, as when migrating from GroupWise to Exchange, or for indefinite or even permanent coexistence.

CMG version 1.7 is a minor release, rebranded to Quest.

Known issues

Localization of CMG for other locales and languages is not yet available. The screens and documentation in the current release are English only.

CMG's Mobile IT Agent (x86) fails to restart after a Repair installation executed from CMG's AutoRun. If the Repair installation is then cancelled, and services.msc is opened, the Mobile IT Agent Service starts with no errors. Quest engineers are investigating this issue.

An Exchange-to-GroupWise Connector does not sync an Exchange user's description field to GroupWise.


After enabling the Add and Delete Verification features at particularly low limits (e.g., Add limit at 50 and Delete limit at 5), in some environments and scenarios a DC connector may run inordinately long without displaying either an error message or any "in-process" indication, while CMG reports the connector status as Running.


In some instances the CMG Management Console is unable to automatically restart the Directory Connector service.

Workaround: Simply restart the service manually in Windows' Services Control Panel.

The Management Console creates a folder for each defined DC connector (under ...\Directory Connector\Tools\Connections) to store connector-specific information. In order to be conservative with the deletion of data, the Remove feature does not remove this corresponding connector folder. The folders can be manually removed (if you like) after removing the DC connector.

External Recipients do not sync in a GroupWise-to-Exchange directory update.

CMG connectors may not be able to automatically create a new shared address book in GroupWise 8.0.0.

Workaround: The administrator can manually create the shared address book before the first connector run—as suggested in step 2 of the DC Configuration procedure (in chapter 2 of the CMG User Guide).

GroupWise does not honor the read-only permissions that CMG assigns to its DC's GroupWise shared address books, so end users are able to delete, change and add contacts. Quest is investigating remedies for this issue, and expects to resolve it in an upcoming CMG release. In the meantime, note that each re-run of the same Exchange-to-GroupWise connector should restore the data to the current state of the corresponding objects in the AD source if any unwanted modifications are made.

Within a few environments, customers have reported that some recurring meetings created in (or routed through) GroupWise are split into individual appointments rather than maintained as a recurring series. This behavior has been corrected in these environments by using a separate SMTP domain for the Exchange/Office 365 users, which modifies how GroupWise sends the invitations. Novell / Attachmate have reported that this behavior has been resolved in GroupWise 2014, so upgrading the GroupWise environment may be another alternative to consider when Quest certifies 2014 as a supported GroupWise environment.


GroupWise 7 does not display meeting requests in a rich context, nor does it display the calendar description. When CMG modified a meeting request with more than 365 occurrences, the user receives the request but is not apprised of the required modifications. This additional information can be revealed by choosing the View | HTML option in the menu.

When an Exchange user cancels a single instance of a recurring meeting after the instance had previously been rescheduled, the instance is not automatically removed from a GroupWise invitee's calendar. In these instances, CMG sends a message to any GroupWise recipients with instructions for updating their calendars.

When a GroupWise meeting organizer changes the date/time of one instance (only) of a recurring meeting series whose attendees include one or more Outlook users, and the organizer then later changes the entire series, the series will appear duplicated in the organizer's GroupWise calendar.

When a GroupWise user organizes a meeting whose invitees include one or more Exchange users, and the organizer then migrates to Exchange, and an Exchange invitee then proposes a new time, the organizer's Outlook calendar is unable to find the meeting.

This scenario generates a duplicate meeting in attendees' calendars:

1 GroupWise user organizes a meeting whose invitees include one or more Exchange users.

2 GroupWise organizer migrates to Exchange.

3 Exchange invitee proposes time change.

4 Migrated organizer replies "tentative and propose new time."

5 Invitees all accept organizer's alternate proposal.

Although no duplicates occur if the organizer replies "decline and propose new time" in step 4.

An invitation to a yearly recurring meeting spanning more than three years, originating in GroupWise and sent to an Exchange invitee, will be returned by CMG to the GroupWise originator.

When an Exchange user invites one or more GroupWise users to a meeting series, then reschedules a single instance to a different time, and then later changes the location of the entire series, GroupWise calendars are not updated for the location change except for the single instance that was earlier rescheduled, but that instance appears once at its original location and twice more at the new location (for a total of three instances).

An Exchange user's calendar is not correctly updated when a GroupWise meeting organizer reschedules a meeting that was originally accepted by the invitee in GroupWise, but then migrated (by Quest MFG) to Exchange.

Outlook 2007 does not update Free/Busy changes as quickly as OWA.

In the Directory Connector: The object Description field is not mapped from GroupWise to Exchange, due to a GroupWise API memory corruption issue.


OWA can render meeting start and end times only on the half-hour—e.g., 1:00, 1:30, 2:00, 2:30, etc. A meeting with a start time other than on a half-hour appears in OWA as starting at the preceding half-hour, and a meeting with an end time other than on a half hour appears in OWA as ending at the next (following) half-hour. So, for example:

This is an OWA rendering issue rather than a CMG issue, and occurs only in OWA, not in Outlook. The actual meeting times are correctly tracked in Exchange, so the same meeting appears in Outlook at its correct time, and free/busy queries are unaffected.

System requirements

Self Service Tools
Knowledge Base
Notifications & Alerts
Product Support
Software Downloads
Technical Documentation
User Forums
Video Tutorials
RSS Feed
Contact Us
Licensing Assistance
Technical Support
View All
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating