Chatee ahora con Soporte
Chat con el soporte

Coexistence Manager for Notes 3.9.2 - 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

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.

To install and configure CMN’s FBC for the active Domino server in a cluster:
1
Ensure that the Domino Admin client installed in the CMN Web Server is able to connect to both Domino servers.
2
Install and configure CMN to support ClusterNode1, as per normal procedures.
3
Ensure that Free/Busy information is retrieved correctly in both directions using ClusterNode1.
To enable the second Domino server in a cluster to support retrieval of Domino F/B information by Exchange:
1
Failover to the standby server in the Domino Server cluster. (ClusterNode2 is now active.)
2
Ensure the Domino Admin client is connected to ClusterNode2.
3
At the CMN Web Server, stop the CMN Domino F/B Connector service.
4
At the CMN Web Server, open the PowerShell and type:
Set-CmnDominoFreeBusyConfig -DominoServerName <ClusterNode2ServerName>
5
Restart the CMN Domino Free/Busy Connector service.
6
Ensure that Domino Free/Busy information is retrieved correctly by Exchange users (using ClusterNode2).
7
Failover to the standby server in the Domino Server cluster. ClusterNode1 is now active.
8
Ensure that Domino Free/Busy information continues to be retrieved correctly by Exchange users (using ClusterNode1).
To enable the second Domino server in a cluster to retrieve Exchange free/busy information:
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.)
2
Configure QCalCon in ClusterNode2 to point to the CMN Exchange Server (where the CMN Exchange F/B Connector Service is installed).
3
Failover to the Standby server in the Domino Server cluster to make ClusterNode2 the active server (if it is not already the active server).
4
Ensure that free/busy information from Exchange is retrieved correctly by Domino users (using ClusterNode2).
5
Perform final tests to ensure that free/busy information from Exchange is successfully retrieved using either Domino server in the cluster.

4-6: Run CMN's Management Console to configure FBC components

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.

 
* 
IMPORTANT: For a hybrid Office 365, be sure to specify the EWS endpoint in the CMN F/B Connector Management Console.
•
If the EWS URL points to the on-premises environment, clear the Exchange Online check box, and fill in the Exchange Username and Exchange Password boxes with the coexistence admin's credentials for the on-prem Active Directory.
•
If the EWS URL points to the Exchange Online, select the Exchange Online check box, fill details in the Tenant ID, Client ID and Client Secret fields with the coexistence admin's credentials for the Cloud.
* 
NOTE: You may use PowerShell commands to configure CMN Free/Busy Connector components, instead of CMN’s Management Console as described here. For information about using PowerShell to configure the Free/Busy Connector, see Configuring and troubleshooting the F/B Connector with PowerShell in chapter 1 of this Scenarios Guide.

Step 5: Configure and test connections among Notes/Domino, Exchange and CMN's FBC Web Server

Step 5: Configure and test connections among Notes/Domino, Exchange and CMN’s FBC Web Server
5-1: Synchronize Exchange and Domino directories

Before using CMN’s Free/Busy Connector, both directories should be updated to include representative objects for users in both systems. For best results, Quest recommends the CMN Directory Connector for this purpose. The Directory Connector is another CMN component that may already be installed and configured. For more information about the CMN Directory Connector, see User Guide chapter 2.

Use CMN’s Directory Connector to define a bidirectional update (a pair of single-direction updates, in opposite directions, run sequentially)—if you do not have such a pair already defined.

Schedule the DC connector to run automatically at a frequency to keep both directories current throughout the coexistence period.

You may choose instead to perform a directory synchronization manually, in which case you may follow the two procedures below.

To synchronize Domino mail users to Exchange contacts:

1
Using the Exchange Management Console, create a mail contact for a Domino user account.
2
Ensure that the Exchange contact has a primary external SMTP address set to the same value as the InternetAddress property for the Lotus Notes mail user account.
3
Repeat the above steps for each Lotus Notes mail user account.

To synchronize Exchange mail users to Domino contacts:

1
Ensure that a Foreign Domain document has been created. To create a Foreign Domain document:
a
As a Domino Administrator, select the Configuration tab.
b
Select Messaging | Domains, then click Add Domain.
c
Select the Basics tab. In the Foreign domain name box, enter a fictitious domain name (for example, CMNFreeBusy). This forces Domino to direct queries to QCalCon rather than to internal queues. Quest recommends using subdomains with the F/B Connector if feasible.
The name of the foreign SMTP domain must be prepended by an asterisk, for example: *Exchange.sitraka.com. This forces Domino to direct queries to QCalCon rather than to internal queues. Quest recommends using subdomains with the F/B Connector if feasible.
d
Select the Mail Information tab. Enter the Gateway server name where the QCalCon Domino Server Task is installed.
e
Enter the Gateway mail file name: mail.box
f
Click the Calendar Information tab, and enter the Calendar server name of the server running QCalCon Domino Server Task.
g
In the Calendar system, enter: mail.box
2
Create a new Person Document using Lotus Notes.
3
Set the mail type to Other Internet Mail.
4
Set the CalendarDomain property to the same value as the CalendarSystem property of the Foreign Domain document. (This permits configuration of CMN’s Free/Busy Domino server task, QCalCon.)
5
Set the InternetAddress property of the Person Document to the Exchange SMTP email address.

5-1: Synchronize Exchange and Domino directories

Step 5: Configure and test connections among Notes/Domino, Exchange and CMN’s FBC Web Server

Before using CMN’s Free/Busy Connector, both directories should be updated to include representative objects for users in both systems. For best results, Quest recommends the CMN Directory Connector for this purpose. The Directory Connector is another CMN component that may already be installed and configured. For more information about the CMN Directory Connector, see User Guide chapter 2.

Use CMN’s Directory Connector to define a bidirectional update (a pair of single-direction updates, in opposite directions, run sequentially)—if you do not have such a pair already defined.

Schedule the DC connector to run automatically at a frequency to keep both directories current throughout the coexistence period.

You may choose instead to perform a directory synchronization manually, in which case you may follow the two procedures below.

To synchronize Domino mail users to Exchange contacts:

1
Using the Exchange Management Console, create a mail contact for a Domino user account.
2
Ensure that the Exchange contact has a primary external SMTP address set to the same value as the InternetAddress property for the Lotus Notes mail user account.
3
Repeat the above steps for each Lotus Notes mail user account.

To synchronize Exchange mail users to Domino contacts:

1
Ensure that a Foreign Domain document has been created. To create a Foreign Domain document:
a
As a Domino Administrator, select the Configuration tab.
b
Select Messaging | Domains, then click Add Domain.
c
Select the Basics tab. In the Foreign domain name box, enter a fictitious domain name (for example, CMNFreeBusy). This forces Domino to direct queries to QCalCon rather than to internal queues. Quest recommends using subdomains with the F/B Connector if feasible.
The name of the foreign SMTP domain must be prepended by an asterisk, for example: *Exchange.sitraka.com. This forces Domino to direct queries to QCalCon rather than to internal queues. Quest recommends using subdomains with the F/B Connector if feasible.
d
Select the Mail Information tab. Enter the Gateway server name where the QCalCon Domino Server Task is installed.
e
Enter the Gateway mail file name: mail.box
f
Click the Calendar Information tab, and enter the Calendar server name of the server running QCalCon Domino Server Task.
g
In the Calendar system, enter: mail.box
2
Create a new Person Document using Lotus Notes.
3
Set the mail type to Other Internet Mail.
4
Set the CalendarDomain property to the same value as the CalendarSystem property of the Foreign Domain document. (This permits configuration of CMN’s Free/Busy Domino server task, QCalCon.)
5
Set the InternetAddress property of the Person Document to the Exchange SMTP email address.
Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación