About the CMN Documentation Suite
Introduction
Welcome to Quest Coexistence Manager for Notes
The CMN Management Console
CMN Performance Counters for Windows' System Monitor
CMN Directory Connector
Directory Connector overview
Installation and configuration
CMN Mail Connector
Configuring the CMN Directory Connector
DC Management Console
Connector Creation Wizard
Step 1: Devise a strategy for your directory updates
Step 2: Configure LDAP to permit Domino read and write access for CMN's Directory Connector
Step 3: Make the showInAddressBook attribute visible in GC
Step 4: Run the DC Management Console and Connector Creation Wizard to create connector(s)
Step 5 (conditional): Change communications port
Step 6 (conditional): Preempt object collisions in environments with multiple source SMTP domains
Step 7 (recommended): Configure LDAP to write to a secondary address book
Step 8 (if necessary): Verify Exchange DL configuration
Step 9 (optional): Configure CMN logging
To synchronize dynamic distribution lists
Starting the Connector Creation Wizard
Screens for an Exchange-to-Notes ("E-to-N") connector
Connector Advanced Settings
E-to-N: Connector Information
E-to-N: Source Server Information
E-to-N: Source Object Selection
E-to-N: Target Server Information
E-to-N: Target Location Information
E-to-N: Connector Order Management
E-to-N: Connector Scheduling
Screens for a Notes-to-Exchange ("N-to-E") connector
Viewing Directory Connector Advanced Settings
Advanced Settings tab: General
Advanced Settings tabs for object types
Starting and stopping the Directory Connector service
Mail Connector features overview
CMN Free/Busy Connector
CMN notifications and "friendly bounces"
CMN active mail processing
About Notes 8.5 Compatibility Mode
Mail Connector Performance Counters
Coexistence mail routing basics
Deployment of CMN Mail Connector
Installation
Configuration
Step 1 (conditional): Create the Notes resource mapping file
Step 2 (conditional): Configure DNS
Step 3: Run the Mail Connector Management Console
Step 4 (optional): Review/update Other Mail Connector configuration options
Step 5: Start the Mail Connector
Step 6: Reconfigure mail servers for CMN
Step 7 (optional): Configure TLS/SSL encryption
Step 8 (optional): Have an administrator sign the CMN.ntf template file
Mail Connector Management Console
Management Console screen:Mail Connector | Inbound Servers
Management Console screen: Mail Connector | Outbound Servers
Management Console screen: Mail Connector | Notes Doc Links
Management Console screen: Mail Connector | Network Settings
Management Console screen: Mail Connector | TLS Settings
Management Console screen: Mail Connector | Advanced Message Settings
Management Console screen: Mail Connector | Address Rewriting
Management Console screen: Mail Connector | Message Content Limits
Management Console screen: Mail Connector | Active Mail
Management Console screen: Mail Connector | Notification Messages
Management Console screen: Mail Connector | Resource Mapping
Free/Busy Connector overview
The Log Viewer
Appendix A: Known limitations
Appendix B: Troubleshooting
Appendix C: CMN Logs
Outlook user retrieves F/B data for a Lotus Notes user
Notes user retrieves F/B data for an Outlook user
FBC installation and configuration
F/B Connector Performance Counters
F/B Connector Management Console
E-to-N: Connector Information
This first screen asks you to name the connector and specify the direction:
|
• |
Connector Name: The name of the connector, as you want it to appear in the table on the Connector Settings screen. Note that the connector name cannot include any characters that are disallowed for a Windows file or folder name, such as \ / : * ? " < > | |
|
• |
Direction: Select the Exchange to Notes option to designate the direction of this connector’s update (as [source] to [target]). |
Click Next to proceed to the next screen.
E-to-N: Source Server Information
Enter this identifying information and access credentials for the source server:
|
• |
Domain: Name of the source (Active Directory) domain, in a form sufficiently qualified that it can be identified from the CMN Directory Connector server. For example: jones.domain1.com |
|
• |
Domain Controller / Domain / Forest (radio buttons): A set of three radio buttons (to the right of the Domain field) to characterize the data source for this connector. |
|
• |
Domain Controller: CMN DC queries the specified DC for existing users. |
|
• |
Domain: CMN DC queries one DC in the Domain specified for existing users. Ensure the CMN DC is added into one of the domains within the forest containing the specified domain. |
|
• |
Forest: CMN DC queries one DC of the root domain specified for existing users throughout the whole Forest. Ensure the CMN DC is added in one of the Domains within the Forest specified. You must ensure that the Domain name in the Domain field is the root domain name of the Forest. |
|
• |
Username: Username by whose authority the Directory Connector will access the source server. |
|
NOTE: Access may fail in some environments even if you enter the correct credentials, since the Username can be expressed differently in different contexts. To solve this problem, see Domino or Exchange server denies access to Directory Connector account, in the Troubleshooting Appendix. |
|
• |
Password: Password associated with the Username above. |
|
• |
Port: Port number that the source server will use to communicate with CMN’s Directory Connector. Leave this value set to its default unless there is some particular reason to designate some other port. |
When these fields are filled as you want them, click Next (or you can click Back to revisit the preceding screen in the sequence).
E-to-N: Source Object Selection
The fields on this screen specify the objects in the source server to be processed.
|
• |
Domain: Name of the source (AD) domain. CMN prefills this field with the value entered for Domain on the Source Server Information screen. |
|
• |
Source OU: In the adjacent container subtree display box, select one or more checkboxes corresponding to the OU(s) containing the objects this connector will copy to the target directory. Note that each container must be explicitly selected to be included with this connector's source OUs. Selecting a higher-level OU includes all of its lower-level OUs. Be sure to select the most inclusive OU(s). |
|
NOTE: For an Exchange-to-Notes connector: The name of the source container for an Exchange-to-Notes connector cannot begin with the letters CMN. If the source container name begins with CMN the connector will generate an Empty Recipient List error. |
|
• |
OUs To Exclude: Enter the path of a Source OUs container that you want to exclude. This field is optional. Separate the paths of multiple source OUs to exclude with a pipe character ("|"), For example: OU=Contoso,O=Cubasic|OU=Quest,O=Cubasic. |
When these fields are filled with the correct information, click Next to advance to the next screen (or click Back to revisit an earlier screen in the sequence).
E-to-N: Target Server Information
Enter this identifying information and access credentials for the target server:
|
• |
Target Server: Enter the name of the target server, in a form sufficiently qualified that it can be identified from the CMN Directory Connector server. For example: smith.domain2.com |
|
• |
Username: The username by whose authority the Directory Connector will access the target server. This must be a domain administrator account with sufficient rights/permissions to access the target server. |
|
NOTE: Access may fail in some environments even if you enter the correct credentials, since the Username can be expressed differently in different contexts. To solve this problem, see Domino or Exchange server denies access to Directory Connector account, in the Troubleshooting Appendix. |
|
• |
Password: Enter the password associated with the Username above. |
|
• |
Port: Enter the port number that the target server will use to communicate with CMN’s Directory Connector. Quest recommends you leave this value set to its default, unless there is some particular circumstance that requires designating some other port. |
When these fields are filled with the correct information, click Next to advance to the next screen (or click Back to revisit an earlier screen in the sequence).