Management Console screen:QCalCon Domino Server Task | Qcalcon Settings
Gateway Mail File Name: Name of the gateway mailbox DB on the Domino server (e.g., mail.box). This should be the same as the Calendar system name.
CMN Exchange Free/Busy Connector Host Name: Name of the computer running the Exchange Free/Busy Connector Service.
CMN Exchange Free/Busy Connector Service Endpoint: This field is filled by CMN and cannot be edited. The value is derived from the Host Name value.
[Test] button: Click the Test button if you want to test the connection to the Endpoint entry. The Management Console will post a dialog box with the test results. Click OK to clear the dialog box.
Management Console screen:Notes F/B Connector | Domino Free/Busy Settings
Domino Server Name: Name of the Domino server, used to gather F/B information of Notes users. For example, NotesHost/NotesDomain or NotesHost
Domino User Fetch Interval In Minutes: Interval between requests for new users, a value from 15 to 1440 inclusive.
Domino User Smtp Domain: Name of the Domino domain. For example, domino.sitraka.com
SMTP Domain Mappings: Used when the domain specified in Notes for a Notes user's email address is different from the domain specified for the same Notes user on an Exchange system, and to enforce a match between the AD targetaddress values and users’ actual Domino email addresses. For example, if the user’s email address in Notes is JohnSmith@notesdomain.com, and his email address in Exchange is JohnSmith@exchgdomain.com, then an SMTP domain mapping would be created for exchgdomain.com=notesdomain.com. Then when Outlook does a F/B search for JohnSmith@exchgdomain.com, the CMN F/B Connector translates the Notes request to JohnSmith@notesdomain.com. SMTP Domain Mappings are used only for Exchange-to-Notes F/B queries. You can Add, Edit or Remove domain-mapped pairs in the table, as noted below.
|
• |
[Add] button: Permits the addition to the table of a new SMTP domain-mapped pair. |
|
• |
[Edit] button: Select an existing domain-mapped pair in the table and click [Edit] to change either of the domain values. |
|
• |
[Remove] button: Select an existing domain-mapped pair in the table and click [Remove] to delete it. |
Domino Id File Path: Use the Browse feature ([...] button) to select the path and filename of the ID file that will be used to request F/B data from Domino, or just enter the path and filename into the text box.
Domino Password: Password associated with the ID File entered above.
Management Console screen:Notes F/B Connector | CMN Web Services
These values configure the CMN Web services.
Web Service Prefix: The first element of the name of the web service for the Domino Free/Busy Connector component. Typically this value is autodiscover, but this field permits an alternate web service prefix, to accommodate F/B coexistence with Exchange 2013 or Office 365 (Wave 14 or 15) where the prefix is configurable.
CMN Autodiscover Host Name: Host configured in DNS to run the CMN services and return Domino F/B information.
CMN Autodiscover URL: Pre-filled by CMN with the correct value derived from the Host Name entry above. This field cannot be edited.
CMN EWS URL: The URL to the Quest Free/Busy Connector’s EWS. For example: https://<HostName>/EWS/Service.asmx
EMS command: Pre-filled by CMN. This command must be run in the Exchange Management Shell to permit Free/Busy lookups to flow from Exchange to CMN.
CMN Domino Free/Busy Connector Host Name: Name of the computer where the Domino Free/Busy Connector is installed—typically this same computer (localhost).
Domino Free/Busy Service Endpoint: Pre-filled by CMN with the correct value derived from the Host Name entry above. This field cannot be edited.
Management Console screen:Exchange F/B Connector | Exchange Free/Busy
Exchange Server Location: Select one of these three radio buttons to tell CMN’s F/B Connector how to route free/busy queries to the coexisting Exchange environment—by EWS Endpoint, by Autodiscover Endpoint, or by Autodiscover Only.
Specify your choice by selecting one of these methods:
|
• |
EWS Endpoint: Select this option if you will coexist with an on-premises Exchange 2013 or 2010 environment with a single Exchange EWS whose location (URL) is fixed relative to CMN’s Exchange FBC service. This approach typically yields the best performance of the three options, but is the least flexible since the connection will fail if the Exchange EWS is not at the specified URL. If you select this option, you must also specify: |
|
• |
Exchange EWS Host Name: Name of the Exchange server where EWS requests should be sent. |
|
• |
EWS URL: Location of Microsoft EWS web service on the Exchange server. |
|
• |
Autodiscover Endpoint: Select this option if you have an on-premises Exchange 2013 or 2010 environment with multiple Exchange EWS endpoints (for example, in a load-balanced environment) and you have an Exchange Autodiscover service that can determine which EWS endpoint to use. This can also be the best choice to coexist with Microsoft's hosted Office 365 (see the Office 365 notes below). Performance will be slower than if you direct the FBC service to a fixed-location EWS (above), but will still be faster than if neither the EWS nor the Autodiscover value is specified (below). If you select this option, you must also specify: |
|
• |
Exchange Autodiscover URL: Location of Autodiscover service on the Exchange server (or, for O365, of the MS Autodiscover URL, as noted below). |
|
NOTE: If coexisting with Microsoft’s Office 365: Select the Autodiscover Endpoint option and set the Exchange Autodiscover URL to Microsoft’s Autodiscover URL:
Note, however, that this is a Microsoft URL subject to change, in which case this connection and the Free/Busy Connector would fail. Remember this if you set the Exchange Autodiscover URL to the Microsoft URL, and CMN’s F/B Connector works fine for a time but then suddenly and consistently fails. The most likely cause is a change in Microsoft’s Autodiscover URL. Contact Microsoft to get the new URL, or select Autodiscover Only (below) instead. |
|
• |
Autodiscover Only: Select this option if you will coexist with an Exchange 2013 or 2010 environment where you don't know the location of either the EWS or Autodiscover, such as in Microsoft's Office 365. In this case, the FBC service will search the network for the connection it needs, so this is the most flexible option, but it is also somewhat slower than either alternative above. |
Regardless of your selection for Exchange Server Location, all of the fields listed below appear on this screen.
Exchange Online: Mark this checkbox only if you are configuring coexistence with Microsoft’s Office 365 hosted Exchange services. If you are configuring coexistence with a local, on-premises Exchange server, make sure this checkbox is unmarked.
Exchange Username: Admin account the F/B Connector should use to access data and features in a hosted Exchange environment. Leave this field empty unless you are connecting to a hosted Exchange, or to a local on-premises Exchange that isn't in the same domain as the CMN admin server. In those cases an entry here is mandatory.
Exchange Password: Password associated with the Exchange Username entered above—again, enter this value only if connecting to a hosted Exchange, or to a local on-premises Exchange that isn't in the same domain as the CMN admin server. In those cases an entry here is mandatory.
Show Tentative As Busy: Select Yes or No to indicate whether Tentative F/B status in Outlook should appear as Busy in Notes.
Azure Cloud Instance: Use the drop-down list to specify the Office 365 environment you want to use—again, select a value only if connecting to a hosted Exchange. The options are as follows: