Chat now with support
Chat with Support

Coexistence Manager for GroupWise 1.7.1 - User Guide

About the Coexistence Manager for GroupWise documentation suite Introduction Coexistence Manager for GroupWise Directory Connector
Directory Connector overview Installation and configuration DC Management Console Connector Creation Wizard Connector Advanced Settings Running and stopping the Directory Connector service
Coexistence Manager for GroupWise Mail Connector Coexistence Manager for GroupWise Free/Busy Connector The Log Viewer Appendix A: Known limitations Appendix B: Troubleshooting Appendix C:Configuring Coexistence Manager for GroupWise logging

Appendix A: Known limitations

The known limitations of any coexistence method are usually due to feature inconsistencies between the two environments. That is, features that are available in one environment may not have an equivalent function in an alternate environment. Other limitations are due to feature incompatibilities, where similar features are available in both environments, but their implementations are so different that remediation is impractical.

NOTE: Many of the Known Limitations documented here are due to known or suspected problems with the connected systems, rather than any inherent limitation of the coexistence process with Coexistence Manager for GroupWise. We list them here as a courtesy, with known solutions (upgrades and hotfixes) where they exist.

Many of the known limitations listed here are inherent to the process and, as such, may not be resolved. Other items we expect to resolve in upcoming releases are itemized in the Coexistence Manager for GroupWise Release Notes, under Known Issues.

Directory Connector issues

A G-to-E connector between GroupWise 7 (only) and Exchange 2007 (only) does not sync a user or contact whose middle initial field contains a "." character (period) in the source. The easiest work-around is to use the Name Rules feature of the connector's Advanced Features to assign some value other than the cn common name to the object name. For example, you could change the object name to the given name, or surname, or could assemble and/or process values from some combination of other attributes to generate a unique object name without a period.
An "access to the registry key ... denied" error that occurs when clicking the Set Configuration button (on the SQL Settings screen) can be dismissed with no disruption to the SQL setup by clicking OK in the error dialog box. This appears to be an OS issue that occurs only with Windows Server 2012 R2, and occurs only the first time SQL Settings are configured. If Set Configuration still generates the error after you have dismissed the error notice once, reboot the computer and try again.

Mail Connector issues

When a custom meeting invitation is sent from a GroupWise organizer to an Exchange invitee using an older release of Outlook 2007 (only), the attendee may mistakenly appear as the meeting organizer. This is a known Microsoft problem in Outlook 2007, which may be corrected by applying either Microsoft's Hotfix 941275, or SP2 of Office 2007.
When a custom meeting invitation is sent from a GroupWise organizer to an Exchange 2010 invitee using an Outlook 2007 12.0.4518.1014 (RTM version) client, an .ics file arrives in Outlook with a blank message body. This is a known Microsoft problem that has been found only in the particular combination of Exchange 2010 with the above-cited Outlook 2007 release. The problem may be corrected by applying either Microsoft's Hotfix 939596, or SP1 of Office 2007.
Some custom recurring meetings created in GroupWise versions earlier than GW 2012 with complex, obscure recurrence patterns arrive in Exchange without the .ics attachment, and can be incorrectly entered into an Outlook invitee's calendar. For example, a recurring series of weekly Tuesday, Wednesday and Friday meetings may appear in Outlook calendars with the Friday meetings dropped from the series. This appears to be a GroupWise issue in versions earlier than GroupWise 2012, where it appears to have been resolved.
An Exchange invitee to a meeting organized by a GroupWise user is not notified of the addition of a new invitee (a person or a resource) added by the GroupWise Modify Recipients feature. If the organizer wants other invitees to know of additions to the attendee list, he/she may use the Resend function rather than Modify Recipients.
The organizer could use the GroupWise Modify Recipients feature to remove all Exchange users from the invitees list, which will generate cancellations to the invitees, although this method generates a cancellation for each instance of the series. That is, cancelling a series with 500 instances would generate 500 single-instance cancellations to each Exchange invitee. Once the Exchange invitees are removed, the organizer can cancel the series for the GroupWise invitees, and then (if rescheduling) re-invite all invitees to an entirely new meeting series.
In a meeting invitation originating in Outlook and sent to a GroupWise 7 (only) invitee, the Location appears in GroupWise with the EXID appended to the actual Location entered in Outlook.
The Mail Connector does not add its usual recipient instructions to the message portion of a GroupWise counterproposal to an Exchange 2003 meeting invitation. This is an apparent limitation of Exchange 2003, which misidentifies a meeting counterproposal as a message reply.
Exchange-side users using OWA or Outlook (or some other outside client) who try to send messages to GroupWise groups get: Error 550 - no such recipient. This is a limitation on the GroupWise side, since it occurs with or without Coexistence Manager for GroupWise involvement.

Free/Busy Connector issues

Related Documents