4-4 (optional): Configure logging for F/B components
By default, CMN is installed with the log4net utility to generate log files of CMN components’ activity. This information is critical to diagnosing any configuration issues that may arise. Logging is enabled by default for all CMN components.
The default configurations will be suitable for most organizations and circumstances, but you can customize logging features. The log4net utility may be configured to work a particular way with each CMN component. Configuration instructions are nearly identical for all components, so we present the instructions separately, in Appendix C of the User Guide.
4-5 (conditional): Configuring CMN's FBC for Domino clusters
|
1 |
Install QCalCon in ClusterNode2. See 2-1: Physically install the CMN QCalCon task. (QCalCon was installed in ClusterNode1 during step 2 of the initial procedure of this series.) |
4-6: Run CMN's Management Console to configure FBC components
Use CMN’s Management Console to configure the Free/Busy Connector’s components—to identify the participating servers and their locations, register the necessary account access credentials, and set other operating parameters and preferences. See chapter 4 of the CMN User Guide for field notes and application notes for each screen in the F/B Connector Management Console.
Step 5: Configure and test connections among Notes/Domino, M365 and CMN's FBC Web Server
Before running any of CMN’s F/B Connector subcomponents, you must synchronize Notes/Domino users as Microsoft 365 contacts, and M365 users to Domino. CMN’s Directory Connector does not support directory synchronizations directly between Domino and Microsoft 365. In this non-hybrid M365 scenario, however, you can configure Microsoft’s Azure AD Sync synchronization tool to synchronize a local AD with Microsoft 365 for this purpose. See Microsoft’s Azure documentation for instructions and guidance in this synchronization.
For FBC coexistence with Microsoft 365, run Enable-OrganizationCustomization, and then create the availability address space by opening a PowerShell session and using the following commands:
[replace <username@domain.onmicrosoft.com> with your M365 admin account]
[replace <domain.onmicrosoft.com> with your SMTP domain name in Microsoft 365]
[replace <username@domain.onmicrosoft.com> with your M365 admin account]
[replace <username@domain.onmicrosoft.com> with your M365 admin account]
[replace <YourPassword> with your Microsoft 365 admin password]
[replace <domain.com> with your SMTP domain name]
You can use Network Load Balancing to permit multiple web servers to handle Autodiscover requests. This is optional, not required to deploy CMN. For more information, see this Microsoft article.
Configure DNS to point autodiscover.<smtpdomain.com> to the computer where CMN’s Autodiscover service is installed. For each domain, Microsoft 365 connects to predefined Autodiscover URLs using DNS host entries.