Coexistence Manager for GroupWise

Maintain GroupWise and Exchange coexistence throughout your migration

Minimize disrupted end-user messaging and communications.

Coexistence Manager for GroupWise provides complete directories and consistent calendars while enhancing messaging collaboration in order to maintain business productivity. The tool offers interoperability between GroupWise and Exchange, Office 365 and hosted Exchange by:

  • Providing free/busy lookups
  • Ensuring accurate calendar scheduling, including custom recurring meetings
  • Synchronizing directories between platforms

Features

  • Free/busy connect—Enables users to view availability and schedule meetings with other users, no matter where their mailboxes reside with free/busy lookups between GroupWise and Exchange, Office 365 or hosted Exchange.
  • Direct connect—Synchronizes directories between GroupWise and Exchange so users on both platforms can view a unified list of users, groups and resources.
  • Calendar guard—Ensures the accuracy of calendar appointments (including custom recurring meetings, re-schedulings and cancellations) that are sent between platforms.
  • Improved management—Lets you control the operation of all installed components from one central location with real-time health and performance monitoring.
  • Smart scale—Delivers scalability and provides for load balancing and failover by enabling you to deploy multiple instances of Coexistence Manager for GroupWise.
  • Remote control—Supports Mobile IT so you can receive and respond to alerts, monitor performance, and control collaboration services from your mobile devices.

Specifications

Before installing CMG 1.5, ensure that your system meets the following minimum hardware and software requirements:

GroupWise server(s)

Supported environments

Requirements for particular environments

Supported GroupWise versions (for all CMG components)
  • GroupWise 7.0.1–7.0.4 (and see below), or
  • GroupWise 8.0.0–8.0.3 (and see below), or
  • GroupWise 2012 (RTM, SP1 or SP2)
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 CMG Directory Connector

Requirements for particular environments

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.)

    • own the shared address book (to serve as repository for the contacts created from AD object data), and
    • access the GW domain files specified by the GW path.
For GroupWise 7.0.x (only)

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

An account with:

  • GroupWise admin rights to the External Domain and Post Office to which CMG’s Exchange-to-GroupWise Directory Connector will write.
  • GroupWise rights to be able to see all requisite objects in the GroupWise domain (including but not limited to all eDirectory Trees in the environment), to be used for CMG’s GroupWise-to-Exchange Directory Connector.

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

 

For CMG Mail Connector

Requirements for particular environments

General requirements
  • Smart hosts, 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.

 

For CMG Free/Busy Connector

Requirements for particular environments

General requirementThe 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:

  • Account rights with a minimum of Read, Write and Delete rights for all folders in the proxy GWIA. These rights may vary depending on the OS to which the proxy GWIA is installed. For example, the equivalent rights on Netware are Read, Write, Create, Modify, Erase and Filescan [RWCEMF].
  • A GroupWise mailbox for use with the F/B Connector and associated services.

 

GroupWise client on end-user workstations

Database Server

Supported GroupWise clients

CMG Mail Connector and/or Free/Busy Connector
  • GroupWise 7.0.1-7.0.4, or
  • GroupWise 8.0.0-8.0.3, or
  • GroupWise 2012: RTM, SP1 or SP2.
Note: CMG does not support GroupWise Web Access.

Exchange server(s)

The CMG Directory Connector, Mail Connector and Free/Busy Connector support these Exchange target types:

Exchange environments

Supported by

Exchange 2003All CMG components
Exchange 2007: RTMDirectory Connector and Mail Connector, but not F/B Connector
Exchange 2007: SP1, SP2 or SP3All CMG components
Exchange 2010: RTM, SP1, SP2 or SP3All CMG components
Exchange 2010 CAS Array: RTM or SP1All CMG components
Exchange 2013: RTM or SP1All CMG components
Office 365Mail Connector and F/B Connector, but not Directory Connector

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

CMG Components

Requirements for particular components

Directory ConnectorAn Exchange user account with membership in Exchange View-Only Administrators (for Exchg 2007) or Organization Management (Exchg 2010/2013). 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 ConnectorSmart hosts, if not using internal routing domains. (If necessary, see Email coexistence before and after CMG in User Guide chapter 3.)
For GroupWise 7.0.x (only)A special configuration, as described in User Guide chapter 4.

Active Directory server

CMG Components

Requirements for particular components

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.

SQL server

CMG Components

Requirements for particular components

Directory Connector

Access to a Microsoft SQL Server, installed on the CMG workstation or by connecting to an existing SQL instance, with a minimum of 20GB free disk space. Note:

  • You may use an existing (installed) Microsoft SQL Server version 2012, 2008 or 2008 Express, 2008 R2, 2005 or 2005 Express, or 2000, or you can download and install a free copy from Microsoft, from the link provided in the CMG AutoRun installer.
    For best performance, particularly at sites with a large number of groups or domains, Dell recommends a full-featured (non-Express) edition of SQL Server.
  • CMG running with SQL Server 2008 requires the SQL 2005 Native Client on the admin server to communicate with SQL. The SQL 2008 Native Client is not supported at this time.
  • Any account used for SQL access must be configured (in SQL) with sysadmin and dbcreator permissions. If the DC will connect to SQL via Windows Authentication, the account must also have "logon as a service" permission.

Outlook end-user workstations

The CMG Mail Connector and Free/Busy Connector support these Outlook client types, with exceptions as noted here:

Outlook clients:

Supported by:

Outlook 2003All CMG components
Outlook 2007: RTM or SP1Directory Connector and Mail Connector, but not F/B Connector
Outlook 2007: SP2All CMG components
Outlook 2010: 32- or 64-bitAll CMG components
Outlook 2013: 32- or 64-bit, RTMAll CMG components
* But see User Guide chapter 4 for special F/B Connector configuration required for Outlook 2003 clients.

Outlook Web Access host server

CMG supports Outlook Web Access 2007, 2010 or 2013.

Admin CMG servers (running CMG components)

IMPORTANT: Admin CMG servers must reside on separate machines from the Exchange and GroupWise servers.

Windows Operating Systems Supported:
Directory Connector
Mail Connector
Free/Busy Connector
Windows Server 200332-bit, SP1

 
32-bit, SP2

64-bit, SP2 

Windows Server 2003 R232-bit

64-bit 

Windows Server 200832-bit, SP1 or SP2

64-bit, SP1 or SP2

Windows Server 2008 R2RTM or SP1

Windows Server 2012RTM

Windows Server 2012 R2RTM

 

Hardware Specifications

Minimum Required

Recommended

Directory Connector
  • 500MB disk space
  • 2GHz processor
  • 4GB memory
  • 1+GB disk space
  • 2- or 4-core processor
  • 8GB memory
Mail Connector and/or Free/Busy Connector (for each)
  • 20GB disk space
  • 4-core 3+GHz processor
  • 4GB memory
  • 20GB disk space
  • 4-core 3+GHz processor
  • 8-16GB memory

 

CMG Components

Requirements for particular components

On every computer hosting any CMG componentMicrosoft .NET Framework 2.0, and 4.0 Full Framework. (The CMG Installer provides links to these, for your convenience if they are not already installed.)
For Directory Connector

GroupWise client installed, version 7.0.4 (for any supported 7.0.x server), or version 8.0.x or GW 2012 (to match the version of the installed GroupWise server).

Novell NetWare client installed: ver 4.91 SP2 for any Win XP or Win 2003, or NetWare Vista client ver 2 SP2 (IR2A) for Windows 7, Vista, Server 2008 or Server 2012. CMG does not support NetWare client version 1.0 for Vista.

If running under Win Server 2008, Data Execution Prevention (DEP) must be disabled in Windows system settings.

No drives may be mapped to NetWare.

For GroupWise 8.0.x (only): Computer cannot contain a mapped drive pointing to the same location (wpdomain.db) as the UNC path for a GroupWise-to-Exchange connector. (DC connectors will not run if a mapped drive points to that location.)

For Free/Busy Connector

Microsoft PowerShell 2.0, 32- or 64-bit (a component of Windows Management Framework, downloadable at this Microsoft link).

Also: Depending on your environment, you may need to run this command to enable the PowerShell layer using remote PowerShell:

get-executionpolicy | set-executionpolicy $unrestricted

For CMG’s Autodiscover, EWS and F/B Bridge: Microsoft IIS 6.0, 7.0 or 7.5, configured and enabled to use ASP.NET 4.0.
Web services certificates on any server with CMG’s Free/Busy Connector Web Server components.

 

Port assignments on CMG servers

Requirements for particular components

All CMG componentsDNS port 53 (uses UDP protocol, not TCP)
Directory Connector

LDAP 389: read/write both directions

LDAP 3268: read to AD

If the SQL DB is running on a separate server, the corresponding port must be open to CMG

Mail ConnectorSMTP port 25: both directions
Free/Busy Connector

1352: outbound to GroupWise

TCP 8961: inbound from GroupWise (default port, update if modified)

TCP 8960: CMG to CMG (default port, update if modified)

SSL 443: inbound from Exchange

For Office 365 scenarios: Ports 80 and 443 out, and port 443 inbound

Port 7191: outbound to GroupWise web services