Chat now with support
지원 담당자와 채팅

Coexistence Manager for GroupWise 1.7.1 - Release Notes

GroupWise server requirements

Supported GroupWise versions
(for all CMG components)

GroupWise 18.1

GroupWise 18

GroupWise 2014 R2: RTM

GroupWise 2014: RTM and SP1

GroupWise 2012: RTM, SP1, SP2, SP3 and SP4

GroupWise 8.0.0-8.0.3 (and see below)

GroupWise 7.0.1-7.0.4 (and see below)

For GroupWise 7 support

The GroupWise API Gateway and GroupWise Proxy GWIA must be installed to support the newer router/postoffice configuration option, which is required for connection to GroupWise 7.

For GroupWise 8 support

Admins may choose between the router/postoffice configuration (requiring the GroupWise API Gateway and GroupWise Proxy GWIA, as noted above for GroupWise 7), and the original shared-address-book configuration.

For mixed GroupWise 7 and 8 environment

If CMG's Free/Busy Connector is configured, the API Gateway and Proxy GWIA must be installed and running in a version 7 domain. If only the Directory Connector is configured, however, CMG can connect to GroupWise 8 via SOAP in a mixed 7/8 environment.

For GroupWise 8.0.x (only)

The GroupWise SOAP web service, enabled on the GroupWise Post Office where the CMG service account resides. To enable and configure SOAP, see this Novell article, and this one too.

A GroupWise admin account with valid Internet Address and Name attributes, and sufficient permissions to:

(For multiple GroupWise servers, DC requires one such account for each server.)

For GroupWise 7.0.x (only)

A non-GroupWise domain and non-GroupWise post office.

An account with:

An account to permit the assignment of the rights cited above.

General requirements

Smart hosts required, if not using internal routing domains. (If necessary see Email coexistence before and after CMG in User Guide chapter 3.)

GroupWise Default message encoding (on the SMTP/MIME tab of GWIA Properties) must be set to MIME, not Basic RFC-822.

For GroupWise 8.0.x (only)

Flat forwarding enabled in the GWIA.

For GroupWise 7.0.x (only)

A defined non-GroupWise domain and non-GroupWise post office.

A Novell Netware server version 6.0–6.5 running the API Gateway version 4.1v2.

General requirements

The GroupWise SOAP web service, enabled on the GroupWise Post Office where the CMG service account resides. For information about enabling and configuring SOAP, see this Novell article, and this one too.

For GroupWise 7.0.x (only)

A non-GroupWise domain and non-GroupWise post office.

A Novell Netware server version 6.0–6.5 running the API Gateway version 4.1v2.

A proxy GWIA: Copy the entire GWIA folder (the “real” GWIA) to a new proxy GWIA directory, and then delete the \wpcsout\gwiaXXXX subfolder (where XXXX is the gateway unique ID), and delete the \wpcsin subfolder. Do not start/enable the proxy GWIA, since the F/B Connector must process the files in the proxy GWIA folders. The proxy GWIA in turn requires:

GroupWise client on end-user workstations requirements

CMG Mail Connector and/or Free/Busy Connector

GroupWise 18.1

GroupWise 18

GroupWise 2014 R2: RTM

GroupWise 2014: RTM and SP1

GroupWise 2012: RTM, SP1, SP2, SP3 and SP4

GroupWise 8.0.0-8.0.3

GroupWise 7.0.1–7.0.4

Exchange server requirements

Office 365

Mail Connector and F/B Connector, but not Directory Connector

Exchange 2016: RTM

All CMG components

Exchange 2013: RTM or SP1

All CMG components

Exchange 2010 CAS Array: RTM or SP1

All CMG components

Exchange 2019: RTM

All CMG components

Exchange 2010: RTM, SP1, SP2 or SP3

All CMG components

Exchange 2007: SP1, SP2 or SP3

All CMG components

Exchange 2007: RTM

Directory Connector and Mail Connector, but not F/B Connector

Table 12. Apple iPhone support: CMG processes GroupWise-to-Exchange messages so they will be compatible with Apple iPhone's iOS6 and iOS7.

Directory Connector

An Exchange user account with membership in Exchange View-Only Administrators (for Exchg 2007) or Organization Management (Exchg 2010/2013/2016). This user must be added to the ACL for the Windows domain, and must have Create and Delete All Child Objects object permissions applied onto This object and all descendant objects (domain object Properties | Security tab | Advanced Security Settings | Edit).

Mail Connector

Smart hosts, if not using internal routing domains. (If necessary, see Email coexistence before and after CMG in User Guide chapter 3.)

Active Directory server requirements

Directory Connector

The Exchange schema extensions on the AD server.

Read/write access rights for the account configured to run the Directory Connector service. At a minimum, the target OU must be delegated to this account.

관련 문서