Chat now with support
Chat mit Support

Coexistence Manager for Notes 3.9.1 - FBC Scenarios Guide

About the CMN Documentation Introduction On-premises Exchange or hybrid O365 using shared (single) namespace On-premises Exchange or hybrid O365 using separate namespaces Non-hybrid O365 using shared (single) namespace Non-hybrid O365 using separate namespaces Appendix: FBC Planning Worksheet Appendix: Troubleshooting the FBC

4-5 (conditional): Configuring CMN's FBC for Domino clusters

CMN supports Domino server clusters (ClusterNode1 and ClusterNode2) that provide Lotus Notes mail service in an active/standby redundancy configuration. In this case, a single CMN Web Server is required to support both Domino Servers. Follow the procedures below to set up this configuration. Initially, ClusterNode1 is the active Domino server.

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, O365 and CMN's FBC Web Server

Before running any of CMN’s F/B Connector subcomponents, you must synchronize Notes/Domino users as Office 365 contacts, and O365 users to Domino. CMN’s Directory Connector does not support directory synchronizations directly between Domino and Office 365. In this non-hybrid O365 scenario, however, you can configure Microsoft’s Azure AD Sync synchronization tool to synchronize a local AD with Office 365 for this purpose. See Microsoft’s Azure documentation for instructions and guidance in this synchronization.

Configure and verify the link from Offi ce 365 to the domains/subdomains supported by the Domino Server. This procedure tests whether the certificate on the CMN Web Server is trusted by O365

For FBC coexistence with Office 365, run Enable-OrganizationCustomization, and then create the availability address space by opening a PowerShell session and using the following commands:

New-AvailabilityConfig –OrgWideAccount <username@domain.onmicrosoft.com>
[replace <username@domain.onmicrosoft.com> with your O365 admin account]
$domain = "<domain.onmicrosoft.com>"
[replace <domain.onmicrosoft.com> with your SMTP domain name in Office 365]
$adminUserId = "<username@domain.onmicrosoft.com>"
[replace <username@domain.onmicrosoft.com> with your O365 admin account]
$adminCredsId = "<username@domain.onmicrosoft.com>"
[replace <username@domain.onmicrosoft.com> with your O365 admin account]
$adminCredsPassword = "<YourPassword>"
[replace <YourPassword> with your Office 365 admin password]

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, Office 365 connects to predefined Autodiscover URLs using DNS host entries.

For Office 365 to get free/busy information from the domain supported by a Domino server, through the CMN Free/Busy Connector, you must make the CMN Autodiscover Web Service resolvable to this URL:

 

Appendix: FBC Planning Worksheet

Use this worksheet to gather and organize the information you will need to enter into CMN’s Management Console application to configure the Free/Busy Connector (FBC).

Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen