Datasheet
Learn how to keep your end users working and productive during a GroupWise migration with Coexistence Manager for GroupWise.
Learn more »
Tech Brief
Learn about the various levels of coexistence available during migration and different options for achieving your desired level of coexistence.
Read now »
Ensure GroupWise Coexistence with Exchange
Discover a new way to ensure GroupWise and Exchange Coexistence that significantly mitigates the impact on end-user productivity.
Watch webcast on demand »

Coexistence Manager for GroupWise

GroupWise and Exchange Coexistence with Minimal Risk

Quest Coexistence Manager for GroupWise helps you maintain business productivity by ensuring interoperability between GroupWise and Exchange, Exchange Online and hosted Exchange. Coexistence Manager for GroupWise mitigates the risk of disrupted messaging and communication between end users by:

  • Providing free/busy lookups
  • Ensuring accurate calendar scheduling
  • Synchronizing directories between platforms

Features

  • Free/Busy Connect – Provides free/busy lookups between GroupWise and Exchange, enabling users to view availability and schedule meetings with other users, no matter where their mailbox resides
  • Direct Connect – Synchronizes directories between GroupWise and Exchange, enabling end users on both platforms to view a common list of users, groups and resources
  • Calendar Guard – Ensures the accuracy of calendar appointments, including custom recurring meetings, reschedules and cancellations, when sent between platforms. This enables GroupWise and Exchange users to collaborate and schedule meetings with each other throughout the coexistence period
  • Smart Scale – Deploy multiple instances of Coexistence Manager for GroupWise to increase scalability as well as load balancing and failover

Sys Reqs

GroupWise EnvironmentGroupWise Server(s)GroupWise Client on
End-User Workstations
7.0.2–7.0.48.0.0–8.0.27.0.2–7.0.48.0.0–8.0.2
Directory Connector••(not applicable)(not applicable)
Mail Connector••••
F/B Connector••••

Note: It is possible to configure CMG for a mixed GroupWise 7 and GroupWise 8 environment, but only if the GroupWise 8 domain is the primary domain, GroupWise 7 and the API Gateway are a secondary domain, and GroupWise 7 serves as the bridgehead between CMG and the GroupWise environment.

GroupWise 7 support requires: the GroupWise API Gateway and GroupWise Proxy. 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. (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 non-GroupWise domain and non-GroupWise post office must be defined.
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. (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.
  • If you want to create 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.
Exchange Server(s)Exchange 2007Exchange 2010Hosted Exchange
RTMSP1SP2SP3RTMSP1CAS Array
(RTM or SP1)		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.)
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.
Outlook End-User WorkstationsSupported Outlook Client Versions
Outlook
2003		Outlook 2007Outlook 2010
RTMSP1SP232-bit64-bit
Mail Connector••••••
F/B Connector•••
Outlook Web Access Host Server:  Outlook Web Access 2007 or 2010.
Admin CMG Servers (running CMG components)Supported Operating Systems
Hardware Specifications
Win Server 2003Windows Server
2003 R2		Win Server 2008Win Server
2008 R2
32-Bit64-Bit32-Bit64-Bit
Minimum
Recommended
SP1SP2SP232-bit64-bitSP1SP2SP1SP2RTMSP1
Directory
Connector		500MB disk space,
2GHz processor,
4GB memory.
1+GB disk space,
2- or 4-core proc,
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.
••••••••••
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 8.0.0–8.0.2 (to match a supported 8.0.x server).
  • Novell NetWare Client must be installed: ver 4.91 SP2 for any Win 2003, or Vista client ver 2 SP2 (IR2A) for any Win 2008.
  • If running under Win Server 2008, Data Execution Protection (DEP) must be disabled in Windows system settings.
  • 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.

Docs

Support Docs, Notes and Guides

Release Notes and User Guides back to top
 

Learn More

Related Products

Support for This Product