For the best web experience, please use IE11+, Chrome, Firefox, or Safari
Free Trials Request Pricing
Home / Products / Coexistence Manager for Notes

Coexistence Manager for Notes

Simplify your migration with seamless, secure user collaboration. Coexistence Manager for Notes ensures seamless collaboration between IBM® Lotus Notes® and Microsoft® Exchange in order to maintain business productivity throughout the coexistence period. You’ll be able to sync Notes and Exchange directories (users, groups and resources) to preserve user collaboration while also enabling free/busy queries between platforms. You can also maintain the fidelity of your email and calendar data, including recurring meetings and active mail, in order to mitigate the risk of lost or delayed operations.

New — Coexistence Manager for Notes now supports Exchange Server 2016.
Coexistence Manager for Notes
Download Free Trial Request Pricing

Nav Menu

Coexistence Manager for Notes

Features

Active mail processing

Provide Exchange users with access to advanced formatting and live Notes content from within their Outlook client. This functionality includes encryption, embedded buttons, hotspots, collapsible sections and tabbed tables. Without Coexistence Manager for Notes, active mail features are not viewable or actionable in Outlook, prohibiting true coexistence.

No need for IBM Domino® databases

Eliminate the need to set up, control access of and perform maintenance on additional Domino databases during the coexistence period.

Scalability

Deploy multiple instances of Coexistence Manager for Notes to increase scalability, as well as improve load balancing and failover.

Directory synchronization

Synchronize directories between Notes and Exchange 2003/2007/2010/2013/2016, enabling users to view a common list of users, groups and resources, no matter where their mailbox resides.

Free/busy connection

Provide free/busy queries between Notes and Exchange 2003/2007/2010/2013/2016, Office 365 and hosted Exchange, enabling users to schedule meetings and view co-workers’ availability, no matter where their mailboxes reside.

Calendar sharing

Ensure that custom and recurring calendar invitations process accurately when sent between platforms. This enables Notes and Exchange users to collaborate and schedule meetings no matter where their mailbox resides.

Link tracking

Ensure that embedded email links to Notes documents continue to be routed correctly throughout the coexistence period, preserving business productivity.

Specifications

Notes/Domino Environment

Supported Domino Server Versions
  • Directory Connector: 6.5.1 –6.5.6, 7.0.0 –7.0.4, 8.0.0 –8.0.2, 8.5.0 –8.5.3, 9.0.1, 10.0.1, 11.0.1
  • Mail Connector: 6.5.1 –6.5.6, 7.0.0 –7.0.4, 8.0.0 –8.0.2, 8.5.0 –8.5.3, 9.0.1, 10.0.1, 11.0.1
  • F/B Connector: 6.5.1 –6.5.6, 7.0.0 –7.0.4, 8.0.0 –8.0.2, 8.5.0 –8.5.3, 9.0.1, 10.0.1, 11.0.1
Supported Notes Client Versions (End User Workstations)
  • Directory Connector: (NA)
  • Mail Connector: 6.5.1 –6.5.6, 7.0.0 –7.0.4, 8.0.0 –8.0.2, 8.5.0 –8.5.3, 9.0.1, 10.0.1, 11.0.1
  • F/B Connector: 6.5.1 –6.5.6, 7.0.0 –7.0.4, 8.0.0 –8.0.2, 8.5.0 –8.5.3, 9.0.1, 10.0.1, 11.0.1
Directory Connector requires:

For Domino® 6.5.x (only), constraint checking on LDAP writes must be disabled.

CMN Mail Connector requires:

For Domino 6.5.1–6.5.6 systems (only): Communications between Domino and the CMN Mail Connector are improved by configuring a Domino 7 or 8 server to act as a bridgehead between CMN and the existing Domino 6 environment.

CMN Free/Busy Connector requires one Domino server hosting QCalCon server task:
  • QCalCon must run on a Domino server running on a Windows OS.
  • No firewall is permitted on any Notes server hosting QCalCon.
  • Microsoft® PowerShell 2.0, 32- or 64-bit (a component of Windows® Management Framework). Also: In some environments this command may be necessary to enable the PowerShell layer using remote PowerShell:  
    • get-execution policy unrestricted 
  • We recommend 4GB memory with a two-core (or more) processor.
Exchange Server(s)
  • Directory Connector: Exchange 2010 (RTM SP1 SP2 or SP3), Exchange 2013 (RTM or SP1), CAS Array (Exchange 2013 RTM or 2010 RTM, SP1, SP2 or SP3), Exchange 2016 (RTM) , Exchange 2019 (RTM)
  • Mail Connector: Exchange 2010 (RTM SP1 SP2 or SP3), Exchange 2013 (RTM or SP1), CAS Array (Exchange 2013 RTM or 2010 RTM, SP1, SP2 or SP3), Exchange 2016 (RTM), Hosted Exchange (Office 365) , Exchange 2019 (RTM)
  • F/B Connector: Exchange 2010 (RTM SP1 SP2 or SP3)*, Exchange 2013 (RTM or Sp1), CAS Array (Exchange 2013 RTM or 2010 RTM, SP1, SP2 or SP3), Exchange 2016 (RTM), Hosted Exchange (Office 365), Exchange 2019 (RTM)

* CMN's Free/Busy Connector does not support Exchange 2010 running in hosted mode.

CMN Directory Connector requires:

An Exchange user account granted membership in Exchange View-Only Administrators (for Exchange 2007) or Organization Management (for Exchange 2013 or 2010). This user must be added to the ACL for the Windows domain, and must have permission to create and delete all child objects applied onto This object and all descendant objects (domain object properties | security tab | advanced security settings | edit).

The Exchange server OS must be the English-language edition —OR— the CMN Directory Connector mapping files must be manually edited to replace hard-coded English elements with their native-language equivalents.

For example, when the CMN log for a French enterprise shows an error message like: problem 1005 (CONSTRAINT_ATT_TYPE), data 0, Att 90284 (showInAddressBook) ... then "All Users" (the hard-coded portion of the string) must be replaced by its French equivalent "Tous les utilisateurs" in every mapping file where the "showInAddressBook" entry occurs. The Directory Connector mapping files are in C:\Program Files\Quest Software\Quest Coexistence Manager for Notes\Directory Connector\Tools\Global\map.

CMN Mail Connector requires:

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

CMN Directory Connector requires:

Target Active Directory server must have the Exchange schema extensions.

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

CMN's Directory Connector requires:

access to a Microsoft SQL Server®, installed on the CMN 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 CMN AutoRun installer.

Note that CMN 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, we recommend 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
  • Mail Connector: Outlook® 2003, Outlook 2007 (RTM, SP1, SP2), Outlook 2010 (32-bit, 64-bit), Outlook 2013 (32- or 64-bit), Outlook 2016 (RTM)
  • F/B Connector: Outlook 2003, Outlook 2007 (SP2), Outlook 2010 (32-bit, 64-bit), Outlook 2013 (32- or 64-bit), Outlook 2016 (RTM)
For Mail Connector, note also:
  • Decryption of Notes-encrypted mail requires a valid Notes certificate.
  • Active Mail processing requires a Notes client, which must connect to a Lotus Domino server.
Outlook Web Access Host Server:

Outlook Web Access 2007, 2010 or 2013.

Hardware Specifications:

Directory Connector:

  • Minimum: 500MB disk space, 2GHz processor, 4GB memory
  • Recommended: 1+GB disk space, 2- or 4-core processor, 8GB memory

Mail Connector:

  • Recommended: 20GB disk space, 4-core 3+GHz processor, 8-16GB memory
  • Minimum: 20GB disk space, 4-core 3+GHz processor, 4GB memory

Free/Busy Connector:

  • Minimum: 20GB disk space/server, 4-core 3+GHz processor, 4GB memory
  • Recommended: 20GB disk space/server, 4-core 3+GHz processor, 8-16GB memory
Supported Operating Systems:

Windows Server 2008

  • Directory Connector: Win Server 2008 R2 (SP1)
  • Mail Connector: Win Server 2008 R2 (SP1)
  • Free/Busy Connector: Win Server 2008 R2 (SP1)

Windows Server 2012

  • Directory Connector: Win Server 2012 RTM or R2
  • Mail Connector: Win Server 2012 RTM or R2
  • Free/Busy Connector: Win Server 2012 RTM or R2

Windows Server 2016

  • Directory Connector: Win Server 2016
  • Mail Connector: Win Server 2016
  • Free/Busy Connector: Win Server 2016

Windows Server 2019

  • Directory Connector: Win Server 2019
  • Mail Connector: Win Server 2019
  • Free/Busy Connector: Win Server 2019

Important:Admin CMN servers must be separate machines from the Exchange and Notes servers.

Required on every computer hosting a CMN component:

Microsoft .NET Framework 2.0, 3.51, and 4.0 Full Framework.

(The CMN Installer provides a link to these, as a convenience, if they are not already installed.)

Active mail processing requires Lotus Notes client 7.0.3 or 7.0.4, or 9.0.1, or Lotus Notes Basic (not Eclipse) 8.0.0.

Directory Connector also requires:

Microsoft PowerShell 3.0 or later, 64-bit (a component of Windows Management Framework 3.0, which comes with Windows 2012 or 2012 R2, or can be downloaded).

Microsoft .NET Framework 4.5.2 (in addition to versions 2.0, 3.51, and 4.0 Full Framework as noted above).

Quest recommends that CMN servers reside in the same domain as Exchange.

Mail Connector also requires:

Active mail processing requires Lotus Notes 7.0.3 or 7.0.4, or Lotus Notes Basic (not Eclipse) 8.0.0.

Free/Busy Connector also requires:
  • No firewall is permitted on any server hosting a Free/Busy Connector component.
  • Microsoft PowerShell 2.0, 32- or 64-bit (a component of Windows Management Framework).
  • CMN F/B Connector servers must reside in the same domain as Exchange.
  • Lotus Notes Client 7.0.x to 9.0.1 installed in single-user mode.
  • For CMN’s Autodiscover and EWS: Microsoft IIS 6.0, 7.0, 7.5 or 8.5, configured and:
    • If IIS 6.0, 7.0 or 7.5: IIS must be configured and enabled to use ASP.NET 4.0.
    • If IIS 8.5: IIS must be configured and enabled to use ASP.NET 3.5 and 4.5.

Resources

View All
Datasheet

Coexistence Manager for Notes

Ensure the accuracy of email, calendar data and active mail
Datasheet

ZeroIMPACT Migrations

Reduce backup recovery time and costs to reduce user impact
Datasheet

Lotus Notes-to-Microsoft migration solutions

Ensure a ZeroIMPACT migration from Lotus Notes to Office 365 and Exchange.
White Paper

Best Practices for Migrating Notes Email to Exchange and Office 365

This white paper details the seven key steps you need to follow for migrating Notes email to Exchange and Office 365.
Case Study

Amway: Office 365 migration team earns prestigious award

Amway migrated its 19,000 Notes mailboxes and calendar data on time and under budget — earning the team prestigious awards — wi...
E-book

ebook: Top Five Ways to Prepare for Your Next Office 365 Tenant Migration

In this eBook, learn the five keys to a successful Office 365 (O365) tenant-to-tenant migration and how Quest solutions will en...
E-book

Speaking from Experience: Migrating from Lotus Notes to SharePoint

Looking to migrate from Lotus Notes to SharePoint? There’s no better way to get the inside scoop on what’s involved...
White Paper

Office 365 Migration: It's just a migration – what could possibly go wrong?

What can go wrong with an Office 365 migration? More than you would expect. But with the appropriate steps, you can avoid many ...

Support & Services

Product Support
Self-service tools will help you to install, configure and troubleshoot your product.

Support Offerings
Find the right level of support to accommodate the unique needs of your organization.