-
Resources
- Forums
-
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 2019.
Features
Active mail processing
No need for IBM Domino® databases
Scalability
Directory synchronization
Free/busy connection
Calendar sharing
Link tracking
Specifications
- 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.0 –9.0.1, 10.0.0 –10.0.1, 11.0.0–11.0.1 –11.0.1, 12.0.0 –12.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.0–9.0.1, 10.0.0 –10.0.1, 11.0.0 –11.0.1, 12.0.0 –12.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.0 –9.0.1, 10.0.0 –10.0.1,11.0.0 – 11.0.1, 12.0.0-12.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.0 –9.0.1, 10.0.0 –10.0.1, 11.0.0 –11.0.1, 12.0.0-12.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.0 –9.0.1, 10.0.0 –10.0.1, 11.0.0 –11.0.1, 12.0.0 –12.0.1
- Directory Connector requires:
- LDAP read and write access to the Domino server, to enable its connectors’ queries and data transmissions. The account used to access Domino must have Add and Delete access to the names.nsf database on the Domino server. To configure this, see CMN User Guide chapter 2, step 2 of the DC's configuration instructions.
- LDAP configuration to write to a secondary address book. You can use Notes Directory Assistance (DA) to direct LDAP writes to a selected address book. Many organizations prefer this approach to isolate the updates and eliminate direct updates to the production NAB. To configure Notes for this, see CMN User Guide chapter 2 (the DC's configuration instructions).
- For Domino 6.5.x (only): Must disable constraint checking on LDAP writes
- 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.
- Microsoft® PowerShell 2.0 or later, 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:
- Outlook End-User Workstations: Supported Outlook Client Versions
- Mail Connector: Outlook 2010 (32-bit, 64-bit), Outlook 2013 (32- or 64-bit) (RTM), Outlook 2016 (RTM)
- F/B Connector: Outlook 2010 (32-bit, 64-bit), Outlook 2013 (32- or 64-bit) (RTM), 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 2010 or 2013.
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.
- 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
Windows Server 2022
- Directory Connector: Win Server 2022
- Mail Connector: Win Server 2022
- Free/Busy Connector: Win Server 2022
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 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 v11.01 notes client is also supported by CMN, 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 at this Microsoft link).
Microsoft .NET Framework 4.7.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:
.NET Framework 4.7. is required to support TLS 1.2. It can be downloaded from this Microsoft link.
Microsoft PowerShell 2.0 or later, 64-bit (a component of Windows Management Framework, which comes with any supported operating system, or can be downloaded).
CMN servers can reside anywhere (no domain membership requirement).
- Free/Busy Connector also requires
.NET Framework 4.7. is required to support TLS 1.2. It can be downloaded from this Microsoft link.
Microsoft PowerShell 2.0 or later, 64-bit (a component of Windows Management Framework, which comes with any supported operating system, or can be downloaded). Also: In some environments this command is necessary to enable the PowerShell layer using remote PowerShell:
get-executionpolicy unrestricted
Lotus Notes Client 7.0.x to 9.0.1, installed and configured in single-user mode. The Notes user used for the Free/Busy administration server requires a mail file since the user must be able to natively look up a Notes user’s Free/Busy.
CMN’s Autodiscover and EWS require Microsoft IIS 6.0, 7.0, 7.5 or 8.5, 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.7.