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.
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.
Eliminate the need to set up, control access of and perform maintenance on additional Domino databases during the coexistence period.
Deploy multiple instances of Coexistence Manager for Notes to increase scalability, as well as improve load balancing and failover.
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.
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.
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.
Ensure that embedded email links to Notes documents continue to be routed correctly throughout the coexistence period, preserving business productivity.
For Domino® 6.5.x (only), constraint checking on LDAP writes must be disabled.
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's Free/Busy Connector does not support Exchange 2010 running in hosted mode.
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.
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.)
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.
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 Web Access 2007, 2010 or 2013.
Directory Connector:
Mail Connector:
Free/Busy Connector:
Windows Server 2008
Windows Server 2012
Windows Server 2016
Windows Server 2019
Important: Admin CMN servers must be separate machines from the Exchange and Notes servers.
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.
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.
Active mail processing requires Lotus Notes 7.0.3 or 7.0.4, or Lotus Notes Basic (not Eclipse) 8.0.0.
Ensure the accuracy of email, calendar data and active mail
Reduce backup recovery time and costs to reduce user impact
Ensure a ZeroIMPACT migration from Lotus Notes to Office 365 and Exchange.
This white paper details the seven key steps you need to follow for migrating Notes email to Exchange and Office 365.
Amway migrated its 19,000 Notes mailboxes and calendar data on time and under budget — earning the team prestigious awards — with help from Quest Professional Services and migration software.
In this eBook, learn the five keys to a successful Office 365 (O365) tenant-to-tenant migration and how Quest solutions will ensure you're prepared.
Looking to migrate from Lotus Notes to SharePoint? There’s no better way to get the inside scoop on what’s involved than by asking the experts — that is, IT pros who’ve already completed a Lotus Notes to SharePoint migration. Luckily, you don’t have to do all that legwo
What can go wrong with an Office 365 migration? More than you would expect. But with the appropriate steps, you can avoid many of the common pitfalls. Let this whitepaper answer your questions.
Ensure a ZeroIMPACT migration from Lotus Notes to Office 365 and Exchange.
Migrate Lotus Notes, QuickPlace/Quickr and Domino.Doc applications to SharePoint
Capture, analyze and act on information about workforce activities and business processes.
Self-service tools will help you to install, configure and troubleshoot your product.
Find the right level of support to accommodate the unique needs of your organization.