Chatta subito con l'assistenza
Chat con il supporto

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

QCalCon Domino Server Task | Qcalcon Settings

| 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.

Quest Exchange Free/Busy Connector Host Name: Name of the computer running the Exchange Free/Busy Connector Service.

Notes F/B Connector | Domino Free/Busy Settings

| 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 Smtp Domain: Name of the Domino domain. For example, domino.sitraka.com

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.

Notes F/B Connector | Quest Web Services

| Quest 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.

Quest Autodiscover Host Name: Host configured in DNS to run the CMN services and return Domino F/B information.

Quest EWS URL: The URL to the Quest Free/Busy Connector’s EWS. For example: https://<HostName>/EWS/Service.asmx

Quest Domino Free/Busy Connector Host Name: Name of the computer where the Domino Free/Busy Connector is installed—typically this same computer (localhost).

Exchange F/B Connector | Exchange Free/Busy

| Exchange Free/Busy

Exchange Server Location: How should CMN’s F/B Connector route free/busy queries to the coexisting Exchange environment? Mark (or circle) one of these, and collect the information associated with that option:

•
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.
 
* 
NOTE: All queries for Exchange users' F/B information must pass through an Exchange EWS, which facilitates communications between Exchange and the CMN Exchange FBC service.

In an Exchange environment with a single EWS at a known fixed location (URL), you can point the FBC service directly to the E‘WS by specifying the EWS URL and host name. If there is no single Exchange EWS with a known fixed location, the FBC service can query the Exchange Autodiscover service, which tracks and reports the current location of an available EWS.

If you will coexist with an Exchange environment where you don't know the location of either the EWS or the Autodiscover endpoint, CMN service will have to search the network for the connection.

•
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:
https://autodiscover-s.outlook.com/autodiscover/autodiscover.svc

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.

Exchange Username: Admin account the F/B Connector should use to access data and features in Office 365. Leave this field empty unless you are connecting to Office 365, 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.

 

Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione