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

GroupWise
environment

GroupWise servers

7.0.2–7.0.4*

8.0.0–8.0.3

GroupWise 2012 RTM, SP1 or SP2

Directory Connector

Mail Connector

F/B Connector

Note: CMG also supports a mixed GroupWise 7 and GroupWise 8 environment. If CMG's Free/Busy Connector is configured, then 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.

*GroupWise 7 support requires: the GroupWise API Gateway and GroupWise Proxy GWIA. These components must be installed to support the newer router/postoffice configuration option, which is required for connection to GroupWise 7. GroupWise 8 admins may choose between the router/postoffice configuration and the original shared-address-book configuration.

CMG Directory Connector requires:

  • For GroupWise 8.0.x (only):
    • The GroupWise SOAP web service must be enabled on the GroupWise Post Office where the CMG service account resides. (For more information, see this Novell article, and this one too.)
    • A GroupWise admin account with valid Internet Address and Name attributes, and sufficient permissions to:
      • 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 multiple GroupWise servers, CMG DC requires one such account for each server.)

  • For GroupWise 7.0.x (only):
    • A defined 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.

CMG Mail Connector requires:

  • Smart hosts must be configured, if not using internal routing domains. (If necessary, see Email Coexistence Before and After CMG in chapter 3 of the CMG User Guide.)
  • 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 must be enabled in the GWIA.
  • For GroupWise 7.0.x (only):
    • A non-GroupWise domain and non-GroupWise post office must be defined.
    • A Novell Netware server version 6.0–6.5 running the API Gateway version 4.1v2.

CMG Free/Busy Connector requires:

  • The GroupWise SOAP web service must be enabled on the GroupWise Post Office where the CMG service account resides. (For more information, see this Novell article, and this one too.)
  • For GroupWise 7.0.x (only):
    • A non-GroupWise domain and non-GroupWise post office must be defined.
    • A Novell Netware server version 6.0–6.5 running the API Gateway version 4.1v2.
    • 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

GroupWise
7.0.2–7.0.4

GroupWise
8.0.0–8.0.3

GroupWise 2012
RTM, SP1 or SP2

 

Note:
CMG does not support GroupWise Web Access.

Mail Connector

F/B Connector

Exchange Server(s)

Exchange 2003

Exchange 2007

Exchange 2010

Exchange 2013

Hosted Exchange

 

RTM

SP1, SP2 or SP3

RTM, SP1, SP2 or SP3

CAS Array
(RTM or SP1)

RTM

Microsoft
Office 365,Microsoft Live@edu,Microsoft BPOS-S

Directory Connector

 

Mail Connector

F/B Connector

 

CMG Directory Connector requires:

  • An Exchange user account granted membership in Exchange View-Only Administrators (for Exchange 2007) or Organization Management (for Exchange 2010). 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).

CMG Mail Connector requires:

  • Smart hosts must be configured, if not using internal routing domains. (If necessary, see Email Coexistence Before and After CMG in chapter 3 of the CMG User Guide.)

CMG Free/Busy Connector with Exchange 2003 requires:

A special configuration, as described in User Guide chapter 4.

Active Directory Server

CMG Directory Connector requires:

  • Target Active Directory server must have the Exchange schema extensions.
  • Account configured to run the DC service must have read/write access rights. At a minimum, the target OU must be delegated to this account.

SQL Server

CMG's Directory Connector requires 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 or 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.
  • Note that CMG running with SQL Server 2008 requires the SQL 2005 Native Client on the admin's workstation to communicate with SQL. The SQL 2008 Native Client is not supported at this time.
  • 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.
  • 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

 

Supported Outlook client versions

Outlook
2003

 

Outlook 2007

 

Outlook 2010

 

Outlook 2013

RTM

SP1

SP2

32- or 64-bit

32- or 64-bit, RTM

Mail Connector

F/B Connector

•*  

* See User Guide chapter 4 for special F/B Connector configuration required to support Outlook 2003 clients.

Outlook Web App host server: Outlook Web App 2007, 2010 or 2013.

Admin CMG servers (running CMG components)

 

Hardware Specifications

Minimum

Recommended

Directory
Connector

500MB disk space,
2GHz processor,
4GB memory.

1+GB disk space,
2- or 4-core processor,
8GB memory.

Mail
Connector

20GB disk space,
4-core 3+GHz
processor,
4GB memory.

20GB disk space,
4-core 3+GHz
processor,
8-16GB memory.

Free/Busy
Connector

20GB disk space,
4-core 3+GHz
processor,
4GB memory.

20GB disk space,
4-core 3+GHz
processor,
8-16GB memory.

Supported operating systems

Win Server 2003

Windows Server
2003 R2

Win Server 2008

Win Server
2008 R2

Win Server
2012

32-Bit

64-Bit

32-Bit

64-Bit

SP1

SP2

SP2

32-bit

64-bit

SP1

SP2

SP1

SP2

RTM

SP1

 

 

 

 
 

Important:Admin CMG servers must be separate machines from the Exchange and GroupWise servers.

Required for every server hosting a CMG component:

  • Microsoft .NET Framework 2.0, and 4.0 Full Framework. (The CMG Installer provides a link to these, as a convenience, if they are not already installed.)

CMG Directory Connector also requires:

  • GroupWise client must be installed, version 7.0.4 (for any supported 7.0.x server), or version 8.0.x or GroupWise 2012 (to match the version of the installed GroupWise server).
  • Novell NetWare Client must be installed: version 4.91 SP2 for any Win XP or Win 2003, or NetWare Vista client ver 2 SP2 (IR2A) for Windows 7, Vista or 2008. CMG does not support NetWare client version 1.0 for Vista.
  • If running under Win Server 2008, Data Execution Protection (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.)

CMG F/B Connector server also requires:

  • Microsoft PowerShell 2.0, 32- or 64-bit (a component of Windows Management Framework, downloadable at this Microsoft link).
  • 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.