Free Busy Connector User Guide 103

Coexistence Manager for Notes
Free/Busy Connector 1.0.3

User Guide
Quest CMN Free/Busy Connector User Guide
Updated - February 2011 (Doc ID 056)
Software Version - 1.0.3 (within Quest CMN 3.0.2)
©
2011 Quest Software, Inc.
ALL RIGHTS RESERVED.
This document contains proprietary information protected by copyright. The software
described in this document is furnished under a software license or nondisclosure
agreement. This software may be used or copied only in accordance with the terms of the
applicable agreement. No part of this document may be reproduced or transmitted in any
form or by any means, electronic or mechanical, including photocopying and recording for
any purpose other than the purchaser's personal use without the written permission of
Quest Software, Inc.
If you have any questions regarding your potential use of this material, contact:
Quest Software World Headquarters

LEGAL Dept.
5 Polaris Way
Aliso Viejo, CA 92656 USA
email: legal@quest.com
Refer to our Web site (www.quest.com) for regional and international office information.
TRADEMARKS
Quest, Quest Software, and the Quest Software logo are trademarks and registered
trademarks of Quest Software, Inc. in the United States of America and other countries.
For a complete list of Quest Software’s trademarks, please see
http://www.quest.com/legal/trademark-information.aspx. Other trademarks and
registered trademarks used in this guide are property of their respective owners.
DISCLAIMER
The information in this document is provided in connection with Quest products. No
license, express or implied, by estoppel or otherwise, to any intellectual property right is
granted by this document or in connection with the sale of Quest products. EXCEPT AS SET
FORTH IN QUEST'S TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT
FOR THIS PRODUCT, QUEST ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY
EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING,
BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A
PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL QUEST BE LIABLE
FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL
DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS,
BUSINESS INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR
INABILITY TO USE THIS DOCUMENT, EVEN IF QUEST HAS BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES. Quest makes no representations or warranties with
respect to the accuracy or completeness of the contents of this document and reserves the
right to make changes to specifications and product descriptions at any time without
notice. Quest does not make any commitment to update the information contained in this
document.
About the CMN
Documentation Suite
The documentation for Quest Coexistence Manager for Notes (CMN) includes:
• Release Notes (HTML): Describes the current CMN release—any new and
enhanced features, resolved issues, and known issues. Also documents minimum
installation requirements, and provides Quest contact information.
• Quick-Start Guide (printable PDF): An orientation to the product's basic
purposes and features, with brief case studies showing how its primary
components are most commonly used within a typical coexistence scenario. Also
documents System Requirements, and explains how to download and install the
software.
• CMN User Guide (printable PDF): Summary of CMN primary components and
features, and process instructions and application notes for configuring, starting
and running the CMN Mail Connector, Free/Busy Connector and Directory
Connector. Also explains how to configure the Domino, Exchange and Active
Directory servers to work with CMN.
• Online Help (compiled Windows Help file): Context-sensitive instructions and
application notes for the various screens and features of CMN’s Configuration
Editor utility.
• CMN Free/Busy Connector Release Notes (HTML): Documents system
requirements for the current release of the Free/Busy Connector (only), and any
new and enhanced features, resolved issues, and known issues pertaining to that
component.
• CMN Free/Busy Connector User Guide (printable PDF): Orientation to the
Free/Busy Connector component of CMN, and process instructions and
application notes for its configuration and administration.
• CMN Free/Busy Connector PowerShell Administration Guide (printable
PDF): Instructions and application notes for using Windows PowerShell cmdlets.
All CMN documentation is intended for network administrators, consultants,

analysts, and any other IT professionals who will install or use the product
components, or who may help plan for their use in a coexistence scenario. All of
these documents, including the online Help, are bundled and installed with the
product, and all except the Help file are available separately at Quest’s
SupportLink for Coexistence Manager for Notes:
https://support.quest.com/SUPPORT/index?page=productInformation
iii
Quest Coexistence Manager for Notes
iv
CONTENTS
ABOUT THE CMN DOCUMENTATION SUITE . . . . . . . . . . . . . . . . . .III
CHAPTER 1
INTRODUCING THE CMN FREE/BUSY CONNECTOR . . . . . . . . . . . . 9
ABOUT CMN’S FREE/BUSY CONNECTOR . . . . . . . . . . . . . . . . .10
HOW THE FREE/BUSY CONNECTOR WORKS . . . . . . . . . . . . . . .10
OUTLOOK USER RETRIEVES
F/B DATA FOR A LOTUS NOTES USER . . . . . . . . . . . . . . .11
NOTES USER RETRIEVES F/B DATA FOR AN OUTLOOK USER . .13
DEPLOYMENT OF F/B CONNECTOR SUBCOMPONENTS . . . . . . . . . .14
INSTALLATION AND CONFIGURATION OVERVIEW . . . . . . . . . .15
CHAPTER 2
INSTALLING AND CONFIGURING THE
F/B CONNECTOR AND ITS HOST ENVIRONMENT . . . . . . . . . . . . . 17
STEP 1:
PLAN YOUR FBC INSTALLATION AND CONFIGURATION . . . . . . . . .18
STEP 2:
INSTALL SUBCOMPONENT SOFTWARE . . . . . . . . . . . . . . . . . . .18
INSTALLATION CHECKLIST . . . . . . . . . . . . . . . . . . . . . . .20
STEP 3:
SYNCHRONIZE EXCHANGE AND DOMINO DIRECTORIES . . . . . . . . .22
STEP 4:
PREPARE YOUR SERVERS FOR CMN’S F/B CONNECTOR . . . . . . . .23
NETWORK LOAD BALANCING . . . . . . . . . . . . . . . . . . . . .23
DOMAIN NAME SYSTEM (DNS) CONFIGURATION . . . . . . . . .23
WEB SERVICES CERTIFICATES . . . . . . . . . . . . . . . . . . . .25
EXCHANGE SERVER CONFIGURATION . . . . . . . . . . . . . . . .28
DOMINO SERVER CONFIGURATION . . . . . . . . . . . . . . . . . .29
STEP 5:
CONFIGURE F/B SUBCOMPONENTS . . . . . . . . . . . . . . . . . . . . .29
STEP 5-1: OPEN POWERGUI. . . . . . . . . . . . . . . . . . . . .29
STEP 5-2: CONFIGURE WEB SERVER AND
LOTUS NOTES COMPONENTS ON THE CMN WEB SERVER . . . .30
v
Quest Coexistence Manager for Notes - Free/Busy Connector
STEP 5-3: CONFIGURE THE EXCHANGE FBC

SERVICE COMPONENT ON THE CMN EXCHANGE SERVER . . . . .32
STEP 5-4: CONFIGURE QCALCON
(THE DOMINO SERVER TASK) ON THE DOMINO SERVER . . . . .33
STEP 5-5: CONFIGURE LOGGING
FOR CMN FBC SUBCOMPONENTS . . . . . . . . . . . . . . . . . .34
VARIATIONS TO BASIC CONFIGURATION . . . . . . . . . . . . . . . . .36
MULTI-DOMAIN SUPPORT . . . . . . . . . . . . . . . . . . . . . . .36
EQUIVALENT DOMAINS . . . . . . . . . . . . . . . . . . . . . . . . .36
MULTIPLE DOMINO SERVER CONFIGURATIONS . . . . . . . . . . .37
DOMINO CLUSTERS . . . . . . . . . . . . . . . . . . . . . . . . . . .37
AN ALTERNATE CONFIGURATION . . . . . . . . . . . . . . . . . . .39
CHAPTER 3
TROUBLESHOOTING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
LOTUS NOTES USERS CANNOT SEE
FREE/BUSY INFORMATION FOR EXCHANGE USERS. . . . . . . . . . . .42
LOTUS USERS CANNOT SEE
FREE/BUSY INFORMATION FOR A LARGE NUMBER OF USERS . .43
OUTLOOK/OWA USERS CANNOT SEE
FREE/BUSY INFORMATION FOR DOMINO USERS . . . . . . . . . . . . .44
OUTLOOK/OWA USERS CANNOT SEE
FREE/BUSY INFORMATION FOR A LARGE NUMBER OF USERS . .46
TROUBLESHOOTING FOREIGN DOMAIN ISSUES . . . . . . . . . . . . . .46
FREE/BUSY REQUESTS DO NOT
ROUTE TO REGISTERED FOREIGN DOMAIN . . . . . . . . . . . . .47
TROUBLESHOOTING EXCHANGE FREE/BUSY ERRORS . . . . . . . . . .47

TROUBLESHOOTING DOMINO FREE/BUSY ERRORS. . . . . . . . . . . .48
TROUBLESHOOTING USING POWERGUI . . . . . . . . . . . . . . . . . .48
TROUBLESHOOTING WEB SERVICES . . . . . . . . . . . . . . . . .48
TROUBLESHOOTING FREE/BUSY FOR DOMINO USERS . . . . . . .49
TROUBLESHOOTING FREE/BUSY FOR EXCHANGE USERS . . . . . .49
ACCESSING SUPPORTLINK KNOWLEDGEBASE . . . . . . . . . . . . . . .50
vi
APPENDIX A:
CONFIGURING CMN F/B CONNECTOR USING CMDLETS . . . . . . . . 51
RUNNING CMDLETS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52
CONFIGURING THE WEB SERVER COMPONENTS . . . . . . . . . . . . .52
CONFIGURING THE AUTODISCOVER WEB SERVICE . . . . . . . .52
CONFIGURING THE FBC EWS . . . . . . . . . . . . . . . . . . . .53
CONFIGURING THE LOTUS NOTES COMPONENT . . . . . . . . . . . . .53
CONFIGURING THE EXCHANGE SERVER COMPONENT . . . . . . . . . .55
CONFIGURING THE DOMINO SERVER COMPONENT . . . . . . . . . . . .56
GLOSSARY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
INDEX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
ABOUT QUEST SOFTWARE . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
CONTACTING QUEST SOFTWARE . . . . . . . . . . . . . . . . . . . . . .63
CONTACTING QUEST SUPPORT . . . . . . . . . . . . . . . . . . . . . . .63
vii
viii
1
Introducing the CMN
Free/Busy Connector
• About CMN’s Free/Busy Connector
• How the Free/Busy Connector Works
• Deployment of F/B Connector
Subcomponents
About CMN’s Free/Busy Connector

The Notes and Exchange environments implement calendar free/busy queries
differently, making each side blind to the availability status of users on the other
system. For full calendar functionality, the calendar applications on both sides
need some mechanism to determine the free/busy status of users within the
other environment.
CMN’s Free/Busy (F/B) Connector is a coordinated set of applications that

together let Exchange and Domino query the calendar availability of each other's
users. This sharing of free/busy data between Notes and Exchange makes
possible automatic calendar updates when accepting a meeting invitation, or
changing the day/time or canceling a meeting, or making some other change to
an existing meeting or recurring series.
How the Free/Busy Connector

Works
When a user in one environment requests free/busy information about a user in
the other environment, the asking server’s query must be translated into a form
that the other server will understand. Likewise, the data reply has to be
translated into a form that the asking server will understand. This is true of
free/busy queries and replies in both directions, and a separate translation
application is required for each direction.
In addition to the query, translation and reply functions, both the Exchange and
Domino servers require a service to facilitate the data communications between
themselves and external data sources (e.g., each other). Exchange requires an
Exchange Web Service (EWS) to enable communications between Exchange and
other applications, while Domino requires a similar application for the same
purposes. And finally, Exchange also requires an Autodiscover service to track
and report the location (URL) of the EWS.
CMN’s bidirectional Free/Busy Connector therefore contains these five

subcomponents to make possible the flow of F/B queries and replies between the
Exchange and Domino servers:
• Free/Busy Autodiscover Web Service: Tracks the location of the

EWS (see below), reporting the EWS URL to Exchange upon each
outbound F/B query (which tells Exchange where to send its query).
• Free/Busy Connector EWS: Facilitates communications between
the Exchange and Domino servers, for the transmission of an
Exchange user’s F/B queries to Domino, and the receipt of F/B
information from Domino.
10
Introducing the CMN Free/Busy Connector
• Domino Free/Busy Connector Service: Translates Exchange F/B

queries into a form that Domino can understand and process, and
then translates F/B data (Domino’s reply to a query) from Domino
form into a form that Exchange can understand and process.
• QCALCON: A Domino server task that facilitates communications
between the Domino and Exchange servers (Exchange F/B queries to
Domino, and Domino’s F/B information)—performing essentially the
same function for Domino that the F/B EWS performs for Exchange.
• Exchange Free/Busy Connector Service: Translates Domino F/B
queries into a form that Exchange can understand and process, and
then translates F/B data (Exchange’s reply to a query) from Exchange
form into a form that Domino can understand and process.
For technical reasons, QCALCON must be installed on the Domino server, and
Quest strongly recommends that the other four subcomponents be distributed
as shown in the accompanying illustrations, and in the next chapter below.
The following scenario narratives and the accompanying illustrations show the
roles these subcomponents serve within the overall scope of CMN’s Free/Busy
Connector.
Outlook User Retrieves F/B Data for a

Lotus Notes User
This illustration shows how three F/B Connector subcomponents fit into the data
flow when an Outlook user requests free/busy data for a Notes user. The step
numbers in this simplified process narrative correspond to the circled numbers
in the illustration (next page).
The scenario: Sally, an Outlook user, wants to book a meeting with Joe, a Lotus
Notes user. Joe’s email address is joe@dominodomain.com. Exchange resolves
"dominodomain.com" through DNS. DNS has a zone called dominodomain.com
with a host called autodiscover.dominodomain.com. The host name must match
the common name (of the certificate you requested) where CMN is installed.
1. The Exchange server asks the F/B Autodiscover Web Service (at
https://autodiscover.dominodomain.com/autodiscover/autodiscover.
xml): "Where is the EWS that can relay my free/busy query to
Domino?"
2. The F/B Autodiscover Web Service replies with the URL for CMN’s F/B
Connector EWS.
3. The Exchange server addresses its F/B query to CMN’s F/B Connector
EWS, at the designated URL.
11
4. The F/B Connector EWS relays the query to the Domino F/B
Connector Service.
5. The Domino F/B Connector Service translates the Exchange query
into Domino form, and passes the query to the Domino server. (The
Domino FBC Service is configured with the Domino Server name,
Directory Server name, ID path, and secure password of the Domino
server.)
6. The Domino server accepts and processes the query, and replies with
Joe’s free/busy information, directed back to the Domino F/B
Connector Service.
7. The Domino F/B Connector Service translates Joe’s Domino F/B data
into Exchange form, and passes the information to the EWS.
8. The F/B Connector EWS receives the inbound F/B data for Joe and
relays it to the Exchange server, where it is passed on to Sally.
12
Notes User Retrieves F/B Data for an

Outlook User
A query-and-reply in the opposite direction, Notes-to-Exchange, is basically the
same, although the details vary somewhat because Domino’s interface to
external data is different from Exchange’s. Again, the step numbers in this
simplified process narrative correspond to the circled numbers in the illustration.
In this scenario, Joe (a Lotus Notes user) wants to book a meeting with Sally,
an Outlook user, whose email address is sally@exchangedomain.com.
1. The Domino server requests Sally’s free/busy information from the

F/B Connector’s QCALCON server task—which resides on the Domino
server and is configured to listen for Exchange calendar queries.
2. QCALCON relays the request to the CMN Exchange Free/Busy
Connector Service.
3. The Exchange F/B Connector Service translates the Domino query
into Exchange form, and passes the query to the Exchange server.
13
4. The Exchange server accepts and processes the query, and replies
with Sally’s free/busy information, directed back to the Exchange F/B
Connector Service.
5. The Exchange F/B Connector Service translates Sally’s Domino F/B
data into Exchange form, and passes the information back to the
QCALCON server task.
6. QCALCON relays the F/B information back to the Domino server,
where it is passed on to Joe.
Deployment of F/B Connector

Subcomponents
For technical reasons, QCALCON must be installed on the Domino server. For
best performance, Quest strongly recommends that the other four subcompo-
nents reside on two separate CMN servers, as shown here:
14
It is possible to configure the CMN Exchange FBC Service on the same server
with the Autodiscover, EWS, and CMN Domino FBC Service. This option is more
fully explained and illustrated in chapter 2—see An Alternate Configuration.
Caution: Quest testing indicates that overall F/B Connector performance is
likely to be diminished by this alternate configuration, but it is possible and
may be preferred in certain particular circumstances, usually in smaller
environments with fewer users and a much lighter F/B traffic load.
Installation and Configuration Overview

The next chapter (2) of this User Guide explains how to make CMN’s Free/Busy
Connector ready to run, by this five-step process:
1. Plan your FBC installation and configuration.

Review the System Requirements (in the CMN Release Notes or
Quick-Start Guide), scan through the installation and configuration
procedures in the next chapter, and think through that process as it
will proceed in your own environment. Anticipate any special
circumstances or issues, and decide now how you will handle them
when they occur.
2. Physically install the subcomponent software.
Install the five CMN F/B Connector subcomponents on the servers
where they will reside, typically (as recommended):
• Domino Server: QCALCON.
• CMN FBC Web Server: Autodiscover, EWS, and Domino FBC Service.
• CMN Exchange FBC Server: CMN Exchange FBC Service.
You must also install the Quest PowerGUI and CMN F/B Connector
PowerPack, on each server where a CMN subcomponent will run.
(Quest PowerGUI is an extensible graphical administrative console for
managing systems based on Windows PowerShell. You can run the
CMN Free/Busy Connector by using PowerGUI and Quest’s Free/Busy
Connector PowerPack.)
3. Synchronize your Exchange and Domino directories.
Quest recommends you use CMN’s Directory Connector (see the CMN
User Guide, chapter 2) to synchronize the two directories.
4. Prepare your servers for the F/B Connector.
Configure domains, permissions and other server attributes so they
will be able to work with CMN’s Free/Busy Connector.
5. Configure the subcomponents for your environment.
Specify the participating servers and their locations, register the
necessary account access credentials, set up their logging features,
and set other operational parameters.
15
16
2
Installing and Configuring
the F/B Connector and Its
Host Environment
• Step 1: Plan Your FBC Installation and
Configuration
• Step 2: Install Subcomponent Software
• Step 3: Synchronize Exchange and Domino
Directories
• Step 4: Prepare Your Servers for CMN’s F/B
Connector
• Step 5: Configure F/B Subcomponents
• Variations to Basic Configuration
Step 1:
Plan Your FBC Installation and
Configuration
Review the System Requirements (in the CMN Release Notes or Quick-Start
Guide), scan through the installation and configuration procedures in this
chapter, and think through this process as it will occur in your own environment.
Anticipate any special circumstances or issues, and decide now how you will
handle them when they occur.
If your configuration will vary from the typical, recommended configuration as

shown in the chapter 1 illustrations, sketch out your own configuration map to
show which subcomponents will reside on which computers.
Step 2:
Install Subcomponent Software
All CMN Free/BusyConnector subcomponents are installed by the AutoRun utility
that is included in the CMN product kit.
Very Important: CMN's F/B Connector contains five subcomponents that are
installed on different servers. Since the AutoRun installer must be run on the
computer where you want to install a particular component, you must run the
Autorun utility at least twice—or three times for our typical, recommended con-
figuration—on different computers.
For best performance, Quest recommends that you install the four non-
QCALCON components on two different CMN Free/Busy Connector servers,
which will require three runs of the AutoRun installer:
• On the Domino server, to install QCALCON.
• On the CMN FBC Web Server, to install Autodiscover, EWS, and Domino FBC
Service.
• On the CMN Exchange FBC Server, to install the CMN Exchange FBC Service.
About Quest PowerGUI and

Free/Busy Connector PowerPack
In addition to the primary Free/Busy Connector subcomponents described
above, a Quest PowerGUI and a F/B Connector PowerPack must also be installed
on every server that contains any piece of the CMN Free/Busy Connector. Quest
PowerGUI is an extensible graphical administrative console for managing
systems based on Windows PowerShell. You can run the CMN Free/Busy
Connector by using Quest’s PowerGUI and Free/Busy Connector PowerPack.
18
Installing and Configuring the F/B Connector and Its Host Environment
The CMN Free/Busy Connector PowerShell Administrator Guide (a separate PDF

included with this release) provides instructions and application notes for
PowerGUI and the cmdlets supported by the Free/Busy Connector. For now we
are concerned only with their installation.
In our typical, recommended configuration, Quest PowerGUI and the PowerPack

must be installed on three computers: the Domino Server, the Exchange FBC
Server, and the CMN FBC Web Server. PowerGUI and the F/B Connector
PowerPack are installed by the same AutoRun utility that installs the other CMN
F/B Connector subcomponents.
The Installation Checklist below explains how to install F/B Connector software
subcomponents server-by-server, by the servers on which they will reside. If
you like you may also install the Quest PowerGUI subcomponents at the same
time you install the other Free/Busy subcomponent(s) on each server. Or you
may revisit each server later to install Quest PowerGUI.
To install the Quest PowerGUI subcomponents at the same time as the primary
F/B Connector subcomponents, simply select them all together in the AutoRun
Custom Installation screen. Select both the Quest PowerGUI and the F/B
Connector PowerPack, in addition to whatever F/B subcomponent(s) you want
to install on a given server.
To manually install the CMN Free/Busy Connector PowerPack, on a

server that already has PowerGUI installed:
1. From the Autorun page, click the Install tab.
In the PowerGUI section, click the link to download the CMN
Free/Busy Connector PowerPack.
2. Open PowerGUI.
3. Select File | PowerPack Management, and click Import.
4. Browse to the CMN Free/Busy Connector installation CD.
5. Open the PowerGUI folder, then select CMN Free Busy Connector
Management.powerpack.
To enable the CMN cmdlets for use with the 32 bit version of PowerShell:
• Open the 32 bit version of PowerShell and type:
Add-PSSnapIn Quest.CMN.FreeBusy
– OR –
• Click the shortcut on the Start menu.
19
Installation Checklist
This section documents which CMN subcomponents should be installed on which
servers, to achieve the typical configuration recommended by Quest (as shown
in the illustrations in chapter 1).
Note: The AutoRun installer automatically checks your environment to verify
CMN prerequisites, but you can bypass the prerequisites check by running the
installer from the command line and appending "ignoreprerequisites=1" to the
command before executing.
On Domino Server: Install QCALCON

Run the AutoRun installer on the Domino Server, and follow the Installation
Instructions as documented in the CMN Release Notes or Quick-Start Guide to
install QCALCON there. QCALCON is installed from the AutoRun Custom
Installation screen, under CMN Free/Busy Connector: Select Domino Server
Components.
Quest PowerGUI subcomponents will also be required on this server, and can be
installed from the same CMN AutoRun. You may install Quest PowerGUI now,
after installing QCALCON, or return to the Domino Server later to install
PowerGUI. See About Quest PowerGUI and Free/Busy Connector PowerPack
above for more information.
On CMN FBC Web Server: Install

Autodiscover, EWS and Domino FBC Service
If your CMN FBC Web Server is not yet running, set it up now. This server should
meet the hardware and software requirements specified for Admin CMN
Servers (see the System Requirements section in the CMN Release Notes or
Quick-Start Guide).
Run the AutoRun installer on your CMN FBC Web Server, and follow the
Installation Instructions as documented in the CMN Release Notes or Quick-Start
Guide to install the Autodiscover, EWS and Domino FBC Service there. These
subcomponents are installed from the AutoRun Custom Installation screen,
under CMN Free/Busy Connector: Select Web Server Components (for
Autodiscover and EWS) and Lotus Notes Components (for Domino FBC
Service).
after installing the CMN FBC Web Server subcomponents, or return to the
Domino Server later to install PowerGUI. See About Quest PowerGUI and
Free/Busy Connector PowerPack above for more information.
20
On CMN Exchange FBC Server:

Install CMN Exchange FBC Service
If your Exchange FBC Server is not yet running, set it up now. This server should
meet the hardware and software requirements specified for Admin CMN
Servers (see the System Requirements section in the CMN Release Notes or
Quick-Start Guide).
Run the AutoRun installer on your Exchange FBC Server, and follow the
Installation Instructions as documented in the CMN Release Notes or Quick-Start
Guide to install the Exchange FBC Service there. This subcomponent is installed
from the AutoRun Custom Installation screen, under CMN Free/Busy Connector:
Select Exchange Components.
after installing the Exchange FBC Service, or return to the Domino Server later
to install PowerGUI. See About Quest PowerGUI and Free/Busy Connector
PowerPack above for more information.
If Necessary: Install Quest

PowerGUI and CMN F/B Connector PowerPack
If you have not already installed Quest PowerGUI and Free/Busy Connector
PowerPack on all servers where other Free/Busy Connector subcomponents
have been installed, do it now. (For more information, see About Quest
PowerGUI and Free/Busy Connector PowerPack above.)
If necessary: Run the AutoRun installer on each server that contains a CMN
Free/Busy Connector subcomponent, and follow the Installation Instructions as
documented in the CMN Release Notes or Quick-Start Guide to install PowerGUI
and the F/B Connector PowerPack.
If You Want to Uninstall CMN Free/Busy Connector

To uninstall CMN Free/Busy Connector subcomponents:
• From Add/Remove Programs (in Windows’ Control Panel): Select
Quest Coexistence Manager for Notes - Free Busy Connector,
and then select Remove.
Uninstalling the CMN Free/Busy connector does not uninstall PowerGUI. You
can uninstall PowerGUI separately.
21
Step 3:
Synchronize Exchange and Domino
Directories
Before running any of CMN’s Free/Busy Connector subcomponents, you must
synchronize Lotus Notes users on Domino with Exchange contacts, and Outlook
users on Exchange with Domino contacts. For best performance, Quest
recommends you use the CMN Directory Connector for this purpose. The
Directory Connector is another CMN component that you may have already
installed and configured, or that you can install at no additional expense. For
complete documentation of the CMN Directory Connector, see chapter 2 of the
CMN User Guide.
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 it 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. For more
information, see To Add a Foreign Domain Document as explained
below.
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.
22
To Add a Foreign Domain Document

To add a foreign domain document:
1. As a Domino Administrator, select the Configuration tab.

2. Select Messaging | Domains, then click Add Domain.
3. Select the Basics tab. In the Foreign domain name box, enter the
SMTP domain of the Exchange users (for example, Exchange).
4. Select the Mail Information tab. Enter the Gateway server name
where the QCALCON Domino Server Task is installed.
5. Enter the Gateway mail file name—e.g., quest.box or qcalcon.box or
cmnfb.box, etc.
6. Click the Calendar Information tab, and enter the Calendar
server name of the server running QCALCON Domino Server Task.
7. In the Calendar system, enter the value of the CalendarDomain
property of the Lotus Notes person documents for the Exchange
users (for example, Exchange).
Step 4:
Prepare Your Servers for
CMN’s F/B Connector
Configure domains, permissions and other server parameters and attributes so
they will be able to work with CMN’s Free/Busy Connector.
Network Load Balancing

You can use Network Load Balancing to permit multiple web servers to handle
requests to autodiscover.<smtpdomain> or <smtpdomain>. This is an optional
step, not required to deploy CMN. For more information, see
http://technet.microsoft.com/en-us/library/cc962172.aspx.
Domain Name System (DNS) Configuration

On the Exchange Server, you must configure your DNS host entries to point to
the computer where Autodiscover is installed. For each domain, Exchange
connects to predefined Autodiscover URLs using DNS host entries.
23
For Exchange 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:
https://[autodiscover.]<smtpdomain>/autodiscover/autodiscover.xml
The "autodiscover." part of this URL is optional, but it must be defined

consistently throughout the configuration of CMN.
If the Domino Server supports one or more subdomains, a DNS host entry is
required to resolve to the CMN Autodiscover Web Service for each subdomain
supported.
On-Premise Exchange
If your Exchange server is on-premise, you can create a host entry so your DNS
can point to the computer where the CMN Autodiscover Web Service is installed.
CREATING A ZONE
You can create a zone so your computer can return the host name when you
query the IP address. The zone must match your SMTP domain.
Use this method if you are using Microsoft DNS.
To create a zone:
1. Locate DNS in Administrative Tools.
2. Right-click Forward Lookup Zone and select New Zone.
3. Select Primary zone and de-select Store the zone in Active
Directory (available only if DNS is a domain controller)
checkbox. Click Next.
4. Enter a zone name (that is, <smtpdomain>), and click Next.
5. Accept the remaining defaults, and click Finish.
6. Repeat steps 2 through 5 for each subdomain supported by the
Domain server.
ADDING A DNS HOST

Once the zone is created, you can add a DNS host to the zone.
To add a DNS host:

1. Right-click the new zone, and select New Host.
2. Enter the name of the host and its IP address. Leave this box blank if
you are using <smtpdomain>, or enter autodiscover if you are
using <autodiscover.smtpdomain>.
3. Click Add Host.
24
Hosted Exchange
If your Exchange server is hosted, you must register each domain name and
subdomain name (in the form autodiscover.smtpdomain or smtpdomain) with a
public Internet registrar, and assign them to the IP address of the computer on
which the CMN Free/Busy Connector Service is installed. The computer must
have port 443 exposed to the Internet.
The CMN Free/Busy Connector fully supports retrieving free/busy information
for users registered in the hosted Exchange.
For your hosted Exchange users to see free/busy information for your
on-premise Domino users, run the Add-AvailabilityAddressSpace cmdlet on
the hosted Exchange server (see Exchange Server Configuration below).
For more information about registering and verifying a domain, see

http://technet.microsoft.com/en-us/library/cc742578.aspx.
Web Services Certificates

CMN Web Server components must support HTTPS to accept SSL connections.
The server on which these components are installed must have a certificate that
Exchange trusts. The single certificate must cover the primary domain and all
subdomains supported by the Domino Server. The certificate covers both web
services.
You can obtain a certificate from either of two sources:

• from a local certification authority (CA) if you are using an on-premise
Exchange server.
• from a public CA, like Verisign or Microsoft Active Directory Certificate
Services, if you are using Exchange in a hosted environment.
You can request a certificate using Web enrollment pages. For more
information, see http://support.microsoft.com/kb/931351.
Once you have received the certificate, you must install it on the appropriate
server.
Requesting and Installing a Certificate Using IIS 6.0

To request a certificate using IIS 6.0:
1. From Internet Information Services (IIS) Manager dialog box,
right-click Default Web Site, and select Properties.
2. From the Directory Security tab, select Server Certificate.
The Web Server Certificate Wizard opens.
3. Click Next.
25
4. Select Create a new certificate request, and click Next.

5. Select Prepare the request now, but send it later, and click
Next.
6. Accept the defaults. Ensure Select cryptographic service
provider (CSP) for this certificate is checked, and click Next.
7. Select Microsoft RSA SChannel Cryptographic Provider, and
click Next.
8. Select or enter your organization’s name and organizational unit, and
click Next.
9. Enter autodiscover.<smtpdomain> or <smtpdomain> as the
common name, for the primary domain and all required subdomains.
Then click Next.
10. Enter the geographical information, and click Next.
11. Specify a file name to save the certificate request, and click Next.
12. Review the information, and click Next.
13. Click Finish.
14. Request a certificate using a local CA or public CA. For more
information, see Requesting a Certificate from a Local CA or
Requesting a Certificate from a Public CA.
To install the certificate using IIS 6.0:

2. From the Directory Security tab, select Server Certificate.
The Web Server Certificate Wizard opens.
3. Click Next.
4. Select Process the pending request and install the certificate,
and click Next.
5. Browse to the location where you have saved the text file, and click
Next.
6. Leave the default port as 443, and click Next.
7. Review the certificate summary. Click Next, then click Finish.
9. From the Directory Security tab, select Edit.
10. Select the Require secure channel check box, and click OK.
26
Requesting and Installing a Certificate Using IIS 7.0

To request a certificate using IIS 7.0:
1. From Internet Information Services, click Server Certificates.
2. From the Actions Pane, select Create Certificate Request.
3. Enter autodiscover.<smtpdomain> or <smtpdomain> for the
primary domain and all required subdomains. Then click Next.
4. Accept the defaults, and click Next.
5. Specify the file name, and click Finish.
6. Request a certificate using a local CA or public CA. For more
information, see Requesting a Certificate from a Local CA or
Requesting a Certificate from a Public CA.
Installing the certificate using IIS 7.0:

1. From Internet Information Services, click Server Certificates.
2. From the Actions Pane, select Complete Certificate Request.
3. Select the saved certificate file, and enter a friendly name for the
certificate, then click OK.
To create an https binding for the web site using IIS 7.0:
1. From the Connection Pane in IIS, select Default Web Sites.
2. From the Actions Pane, select Bindings.
3. Select Add. Select https as the type for a secure site, and enter the IP
address and port number.
4. Select the SSL certificate to pass the certificate into the computer
account.
5. Click View to view any certificate information.
Requesting a Certificate from a Local CA

To request a certificate from a local CA:
1. From a web browser, enter
https://<Local_Certification_Authority_computer>/certsrv
2. Click Request a certificate, then click Advanced certificate
request.
3. Select Submit a certificate request by using a
base-64-encoded CMC or PKCS #10 file, or submit a renewal
request by using a base-64- encoded PKCS #7 file.
4. Open the text file where you save the certificate request.
5. Copy and paste the text from the certificate request into the Saved
Request box when you selected Submit a certificate request by
using a base-64-encoded CMC or PKCS #10 file, or submit a renewal
request by using a base-64-encoded PKCS #7 file.
27
6. In the Certificate Template box, select Web Server.

7. Click Submit.
8. Select Base 64 Encoded, then select Download certificate.
9. Save the file.
Requesting a Certificate from a Public CA

To get a certificate from a public CA, go to the web site of the public CA, and
follow their instructions to request a certificate.
Exchange Server Configuration

Perform the following procedure to configure and test the link from the Exchange
Server to the domain and subdomains supported by the Domino Server, through
the CMN Web Server. This procedure tests whether the certificate on the CMN
Web Server is trusted by the Exchange Server.
To configure the Exchange Server link to the CMN Web Server and verify
that certificates are trusted by Exchange:
1. At the Exchange Server, open Exchange Management Shell and enter
the following cmdlet:
Add-AvailabilityAddressSpace -ForestName <smtpdomain>
-AccessMethod OrgWideFB -UseServiceAccount $true.
... where <smtpdomain> is the name of the Domino domain.
2. Open a Web browser and enter the URL
https://[autodiscover.]<smtpdomain>/autodiscover/
autodiscover.xml to ensure that the Exchange Server resolves it to
the CMN FBC EWS without any certification errors.
3. Ensure the certificate created earlier is trusted by Exchange. If it is
not, see Web Services Certificates.
4. If Domino Server subdomains have been configured, repeat the
above steps for each subdomain.
If you created a self-signed certificate and a certification error appears in the
Web browser:
1. Click the SSL button in the Web browser.
2. Click View Certificates.
3. Right-click the certificate to open the Import Certificate Wizard dialog
box.
4. Install the certificate in Trusted Root Certification Authorities, and click
Next.
5. Click Import, then Finish.
If you requested a certificate from a public CA, the certificate is already
trusted by Exchange.
28
Domino Server Configuration

If you are using a foreign SMTP domain document to route to Exchange users,
open the domain document and verify that the name of the foreign SMTP domain
is prepended by an asterisk, for example: *Exchange.domain.com. This is
necessary to force the Free/Busy Connector to direct queries to QCALCON,
rather than letting Domino presume it can resolve the domain by itself. Quest
recommends that you use subdomains with the CMN Free/Busy Connector.
Step 5:
Configure F/B Subcomponents
Identify the participating servers and their locations, register the necessary
account access credentials, set up their logging features, and set other operating
parameters.
Wizards are available to walk you through the configuration of CMN Free/Busy
Connector subcomponents using the PowerGUI. The rest of this chapter explains
how to use the wizards to complete configuration of the F/B subcomponents.
Except where noted otherwise, these procedures assume that subcomponents
are installed as described in the Quest-recommended Deployment of F/B
Connector Subcomponents.
If you prefer, you may instead use cmdlets to configure CMN F/B Connector
subcomponents. For more information about using cmdlets, see Appendix A:
Configuring CMN F/B Connector Using cmdlets.
The CMN Free/Busy Connector subcomponents can also be installed in

configurations other than the Quest-recommended standard. The most likely
alternative is explained in a separate topic (An Alternate Configuration) below.
Step 5-1: Open PowerGUI

Go to Start | Programs | PowerGUI | PowerGUI.
For more information on PowerGUI, see the CMN Free/Busy Connector

PowerShell Administrator Guide.
29
Step 5-2: Configure Web Server and Lotus

Notes Components on the CMN Web Server
To prepare the CMN Web Server for the Autodiscover, FBC EWS, and
Lotus Notes Components:
1. From the Navigation Tree, select Configure Web Services and
Lotus Notes Components.
2. From the Actions Pane, select Configuration Wizard to open the
Configuration Wizard, and click Next.
3. Enter the SMTP domain (the name of the Domino domain), and click
Next. As you enter an SMTP domain, the dialog box is populated
with the SMTP domain in the form of <smtpdomain> or
<autodiscover.smtpdomain>. Select the form you want to use.
4. Enter the Domino Server name, Domino ID file path, and Domino
password. Click Next.
5. Click Next again to apply the changes.
The Results tab appears, showing the table populated with the values
you entered in the wizard. Also, if you select a subcomponent in the
Advanced node in the Navigation Tree, each subcomponent is
populated with the values you entered in the wizard.
To configure the Autodiscover Web Service on the CMN Web Server:

Lotus Notes Components | Advanced | Autodiscover Web
Service.
2. From the Actions Pane, select Set CMN Availability URL.
3. Enter the URL to the FBC EWS. For example:
https://<HostName>/EWS/Service.asmx
... for the CmnAvailabilityUrl parameter, where <HostName> is
autodiscover.<smptdomain> —or— <smtpdomain>.
4. Click OK.
To configure the FBC EWS on the CMN Web Server:

Lotus Notes Components | Advanced | Availability Web
Service. (Availability Web Service is another name for EWS.)
2. From the Actions Pane, select Set Domino Free Busy connector
host name.
3. Enter the name of the computer hosting the Domino Free/Busy
Connector Service, and click OK.
4. From the Actions Pane, select Set Domino Free Busy connector
port.
30
5. Enter the port number of the computer hosting the Domino

Free/Busy Connector Service, and click OK.
To configure the CMN Domino FBC Service on the CMN Web Server:
Lotus Notes Components | Advanced | Domino Free/Busy
Connector.
2. From the Actions Pane, select Set Domino server name.
3. Enter the name of your Domino Server, and click OK.
4. From the Actions Pane, select Set Domino password.
5. Enter the secure password, and click OK.
6. From the Actions Pane, select Set Domino ID file path.
7. Enter the path to your Domino ID file, and click OK.
8. From the Actions Pane, select Set Domino user SMTP domain.
9. Enter the fully qualified SMTP domain of the Domino users sharing
free/busy information, and click OK.
10. From the Actions Pane, select Set listening port.
11. Enter the TCP port the Domino Free/Busy Service Connector Service
should use, and click OK.
12. From the Actions Pane, select Set free/busy cache timeout (in
minutes). Enter the amount of time the free/busy information will
remain cached, and click OK.
13. From the Actions Pane, select Set Domino user fetch interval (in
minutes).Enter the interval to refresh the list of Domino users, and
click OK.
The following parameters are mandatory to configure the Domino Free/Busy
Connector Service:
• -DominoServerName
• -DominoPassword
• -DominoUserSmtpDomains
Lotus Notes Components | Advanced | Domino Free/Busy
Connector Service.
15. Select whether to modify the name or credentials of the connector
service, or whether to stop, start, restart, suspend, or resume the
service.
31
Step 5-3: Configure the Exchange FBC Service

Component on the CMN Exchange Server
To prepare the CMN Exchange Server for the CMN Exchange FBC Service:
1. From the Navigation Tree, select Configure Domino Server and
Exchange Components.
2. From the Actions Pane, select Configuration Wizard.
The Configuration Wizard opens.
3. Click Next.
4. Enter your preferred Exchange server. Click Next.
The Exchange Web Services URL is automatically populated using the
name of your Exchange server in this form:
https://<preferred Exchange Server name>/EWS/Exchange.asmx
5. Enter the logon credentials needed for the Quest CMN Exchange
Free/Busy Connector Service, and click Next.
6. Review the summary of what you have configured, and click Next
again to apply the changes.
To configure the Exchange FBC Service in the CMN Exchange Server:

Exchange Components | Advanced | Exchange Free/Busy
Connector.
2. From the Actions Pane, select Set EWS URL.
3. Enter your email address and click OK.
4. From the Actions Pane, select Set Exchange credentials.
5. Enter your credentials, and click OK.
6. From the Actions Pane, select Set free/busy cache timeout (in
minutes).
7. Enter the amount of time the free/busy information will remain
cached, and click OK.
8. From the Actions Pane, select Set listening port.
9. Enter the TCP port the Exchange Free/Busy Service Connector
Service should use, and click OK.
32
10. From the Actions Pane, select Show tentative status as busy or
Show tentative status as free to determine how tentative status
from Outlook is shown in Lotus Notes.
The default is to show tentative status as free.
11. If your Exchange is hosted and your domain is registered (see
Hosted Exchange), you must complete the following sub-steps, using
PowerShell cmdlets.
If you are using Microsoft Online Services, sign into Microsoft Online Services
Sign-In before running the Get-CmnExchangeWebServicesUrl cmdlet.
a) Open the PowerShell and type

$credential = get-credential.
b) In the dialog, enter the email address and password for a hosted
Exchange enabled user.
c) To retrieve the Exchange Web Services URL and assign it to the
$ewsUrl variable, type
$ewsUrl = Get-CmnExchangeWebServicesUrl -EmailAddress
<emailAddress> -Credentials $credential.
... where <emailAddress> is for a hosted Exchange enabled user.
d) Type
Set-CmnExchangeFreeBusyConfig -EwsUrl $ewsUrl -Credentials $credential
Step 5-4: Configure QCALCON (the Domino

Server Task) on the Domino Server
To prepare the Domino Server for QCALCON:
2. From the Actions Pane, select Configuration Wizard.
The Configuration Wizard opens.
3. Click Next.
4. Enter the name of the Foreign Domain, and the name of the
computer running the CMN Exchange Free/Busy Connector Service.
Click Next, and a summary of your configuration entries appears.
The Results tab appears, showing the table populated with the
values you entered in the wizard. Also, if you select a subcomponent
in the Advanced node in the Navigation Tree, each subcomponent is
33
To configure QCALCON in the Domino Server:

Exchange Components | Advanced | Domino Task Server
(QCALCON).
2. Enter the full UNC path to the QCALCON.exe.config file on the
Domino Server, and click OK.
3. From the Actions Pane, select Set Foreign Domain name.
4. Enter the name of the foreign domain associated with the Notes
Documents for Exchange users, and click OK.
5. From the Actions Pane, select Set Exchange Free/Busy
Connector host name.
6. Enter the name of the computer running the Exchange Free/Busy
Connector Service, and click OK.
7. From the Actions Pane, select Set Exchange Free/Busy
Connector port.
8. Enter the port number used by the Exchange Free/Busy Connector
Service, and click OK.
Step 5-5: Configure Logging

for CMN FBC Subcomponents
By default, CMN is installed with the log4net utility to generate log files of CMN
Mail Connector system activity. This information is critical to diagnosing any
problems that may arise.
CMN logging for all components is enabled by default, but you may want to
change the location of the log file and/or change the level of detail in the logs.
Logging options are set in a log4net.config configuration file in the F/B Connector
installation directory. The log4net.config file is an XML file that can be opened
and edited with any XML editor.
The level of logging detail is specified by one of these single words:
OFF FATAL ERROR WARN INFO DEBUG ALL
The values are listed here in ascending order of detail (left to right).
The CMN Free/Busy Connector generates as many as five log files, one for each
of its subcomponents:
34
Log Output File Name Log Configuration File Name

QCalCon.exe.log QCalCon.log.config
ExchangeFreeBusyService.exe.log ExchangeFreeBusyService.log.config
DominoFreeBusyService.exe.log DominoFreeBusyService.log.config
EWS.log [for EWS] EWS.log.config
EWS.log [for AutoDiscover] EWS.log.config
For more detailed information about the log4net utility and how its log files can
be configured, see the log4net Config Examples at the Apache.org web site.
How to Change Configuration Values in log4net.config

The default configuration in the log4net.config configuration file will be suitable
for almost all organizations and circumstances. Some operational details can be
configured by changing default parameter values in the log4net.config file in the
CMN installation directory. The log4net.config file is an XML file that can be
opened and edited with any XML editor.
Note: Any changes to the log4net.config file are immediately applied by the
CMN service when the configuration file is saved.
To edit configuration values in log4net.config:
1. Open the file log4net.config (in the log4net folder) with an XML editor.
2. Find the section <SectionName>, that contains the parameter(s) you
want to edit.
3. Make any desired changes. Values must be enclosed in double
quotation marks and followed by a trailing space and slash character,
like this: <ParameterName="value" />
4. Repeat steps 2 and 3 as often as necessary to make additional
parameter changes.
5. Close and Save the configuration file under the same log4net.config
filename.
35
Variations to Basic Configuration
Multi-Domain Support
The CMN can facilitate the exchange of free/busy information between multiple
subdomains supported by both the Exchange and Domino Servers. Specific steps
are required to support subdomains on the Domino side, as noted within the
procedures documented here. Use this checklist to ensure configuration is
complete.
To configure CMN for Domino SMTP multi-domain support

• Ensure that autodiscover records exist in DNS for the number of SMTP
Domains used by Domino. See Domain Name System (DNS)
Configuration.
• Ensure that the certificate used in the CMN Web Server has subject
alternate names for all of the autodiscover host names above. See
Web Services Certificates.
• On the Exchange Server, ensure that the cmdlet
Add-AvailabilityAddressSpace has been run for the number of Domino
SMTP domains supported. See Exchange Server Configuration.
Equivalent Domains
CMN supports equivalent domain names for Express mail users and Domino mail
users. Equivalent domains are mapped to the primary domain in the Express
Server or Domino Server. The following procedures use cmdlets in the CMN
PowerPack to perform this mapping.
To map an equivalent domain to a domain supported by a Domino Server

(repeat for each equivalent domain):
• At the CMN Web Server, open the PowerShell and type:
Set-CmnDominoFreeBusyConfig -DominoServerName <Server Name>
-DominoPassword <password> -SmtpDomainMappings
<equivalentDomain>=<primaryDomain>
To map an equivalent domain to a domain supported by an Exchange

Server (repeat for each equivalent domain):
• At the CMN Exchange Server, open the PowerShell and type:
Set-CmnExchangeFreeBusyConfig -EwsUrl <URL> -Credentials
<PWCredential> -SmtpDomainMappings
<equivalentDomain>=<primaryDomain>
36
Multiple Domino Server Configurations

CMN supports the exchange of free/busy information between multiple Domino
Servers and a single Exchange Server. To deliver Domino user information to the
Exchange Server, a separate CMN Web Server is required to service each
Domino Server. QCALCON must be installed in each Domino Server.
To deliver Exchange User information to Domino servers, only one CMN

Exchange Server is required, and if server loading allows, this can be one of the
CMN Web Servers. The diagram below (see next page) shows a typical
configuration. Configuration procedures are unchanged.
Domino Clusters
CMN supports a cluster of two Domino Servers (ClusterNode1 and ClusterNode2)
that provide Lotus Notes mail service in an active/standby redundancy
configuration. In this case, only 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.
37
2. Install and configure CMN to support ClusterNode1, as per normal

procedures (see Deployment of F/B Connector Subcomponents).
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 Free/Busy 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 On Domino Server: Install
QCALCON. (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 Free/Busy Connector Service is
installed). See Step 5-4: Configure QCALCON (the Domino Server
Task) on the Domino Server.
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 retrieved successfully using either of the Domino servers
in the cluster.
38
An Alternate Configuration
The installation and configuration instructions in this chapter are written for the
typical, recommended configuration as summarized in chapter 1 (see
Deployment of F/B Connector Subcomponents). But it is also possible to
configure the CMN Exchange FBC Service on the same server with the
Autodiscover, EWS, and CMN Domino FBC Service, as shown here:
In this case, the CMN Exchange Server is not required. The configuration wizard
customizes the steps required, based on the CMN Free/Busy Connector
subcomponents it detects on the Domino server.
Caution: Quest testing indicates that overall F/B Connector performance is
likely to be diminished by this alternate configuration, but it is possible and
may be preferred in certain particular circumstances, usually in smaller
environments with fewer users and a much lighter F/B traffic load.
To use cmdlets for configuration, see Appendix A: Configuring CMN F/B

Connector Using cmdlets.
39
To configure both the Exchange and Domino Server components

2. From the Actions Pane, select Configuration Wizard to open the
Configuration Wizard.
3. Click Next.
4. Enter the name of the Foreign Domain, and click Next.
5. Enter your preferred Exchange server.
The Exchange Web Services URL is automatically populated using the
name of your Exchange server in the form:
https://<preferred Exchange Server name>/EWS/Exchange.asmx
6. Enter the logon credentials needed for the Quest CMN Exchange
Free/Busy Connector Service, and click Next.
A summary of what you have configured appears.

To configure the CMN Exchange FBC Service, see: On CMN Exchange FBC
Server: Install CMN Exchange FBC Service.
To configure QCALCON, see: On Domino Server: Install QCALCON.
40
3
Troubleshooting
• Lotus Notes Users Cannot See Free/Busy
Information for Exchange Users
• Outlook/OWA Users Cannot See Free/Busy
Information for Domino Users
• Troubleshooting Foreign Domain Issues
• Troubleshooting Exchange Free/Busy Errors
• Troubleshooting Domino Free/Busy Errors
• Troubleshooting using PowerGUI
• Accessing SupportLink Knowledgebase
Lotus Notes Users Cannot See

Free/Busy Information for
Exchange Users
On the Domino Server:
•) Ensure the Person documents created for the Exchange users have the
proper CalendarDomain property set. To do this:
1. Open the Domino Directory in Lotus Notes.
2. Right-click the Person Document for the Exchange user and click
Document Properties
3. Ensure the CalendarDomain property matches the Calendar System
specified in the Foreign Domain document.
•) Ensure the Foreign Domain Document has been created. To do this:
1. See To Add a Foreign Domain Document.
2. After making changes to the Foreign Domain Document, restart the
Domino server.
•) Check connectivity between the Domino server and the computer run-
ning the CMN Free/Busy Connector.
•) Make sure the QCALCON Domino Server task is running. To do this:
• From the Domino Console, type Show Tasks.
On the Computer hosting the Exchange Free/Busy Connector:

•) Ensure the Exchange Free/Busy connector service is running as a
domain user with access to the Exchange server.
Try one of the following options:
• Set the service logon credentials for the Quest CMN Exchange
Free/Busy Connector service (see Step 5-3: Configure the Exchange
FBC Service Component on the CMN Exchange Server).
• Set the exchange credentials using the
Set-CmnExchangeFreeBusyConfig cmdlet.
Try each of these methods if you are seeing errors in your event log
when testing free/busy.
•) Ensure the EwsUrl is properly configured to the Exchange Web Services

URL for your Exchange server. If you are using a hosted Exchange or do
not know what the Exchange Web Services URL is, use
Get-CmnExchangeWebServicesUrl cmdlet. (See Hosted Exchange)
•) After verifying the EwsUrl is correct, navigate to the URL using a Web
Browser such as Internet Explorer. Verify that you can access the URL
42
Troubleshooting
using the same credentials used by the Exchange service without any
additional credential prompts and without any certificate errors.
•) Ensure the appropriate port is open on the Exchange Free/Busy Connec-
tor service computer for TCP/IP communication.
•) If you see the following error message in the event log:
The underlying connection was closed: Could not establish
trust relationship for the SSL/TLS secure channel.
On the computer running CMN Exchange Free/Busy Connector

service, perform the following:
1. Open CMN Free/Busy Connector Management Shell.

2. Type get-CmnExchangeFreeBusyConfig.
3. Ensure the URL specified by the EwsUrl property resolves properly in
Internet Explorer with no certificate errors.
If a certificate error is found, add the Exchange certificate to the
Trusted Root Certification Authorities folder.
Lotus Users Cannot See Free/Busy

Information for a Large Number of Users
If you see the following error message: "The maximum message size quota for
incoming messages (65536) has been exceeded", you must increase the quota
by using the MaxReceivedMessageSize property on the appropriate binding
element.
If you are using Lotus Notes and querying Free/Busy information for an
Exchange user, edit QCALCON.exe.Config file on the Domino server:
1. Increase the maxReceivedMessageSize property to a larger value.

<netTcpBinding>
binding name="CMNFreeBusyClientSettings"
openTimeout="00:01:00"
receiveTimeout="00:01:00"
sendTimeout="00:01:00"
closeTimeout="00:01:00"
maxReceivedMessageSize="655360">
<security mode="None"/>
</binding>
</netTcpBinding>
2. Restart QCALCON.
43
Outlook/OWA Users Cannot See

Free/Busy Information for Domino
Users
On the Exchange Server:
•) Verify that Add-AvailabilityAddressSpace has been executed on the
Exchange server (for example, Add-AvailabilityAddressSpace -Forest-
Name <smtpdomain> -AccessMethod OrgWideFB -UseServiceAccount
$true).
• To verify that the cmdlet has run, type
Get-AvailabilityAddressSpace on the Exchange Management
Console.
•) Ensure you can ping <smtpdomain> or autodiscover.<smtpdomain>
and that it resolves to the computer running the CMN free/busy connec-
tor.
•) Open a web browser such as Internet Explorer and type
https://<host>/autodiscover/autodiscover.xml (where <host> is
either <smtpdomain> or autodiscover.<smtpdomain>, and ensure a
.xml file appears and that you do not have any certificate errors.
• If the .xml file displayed has the text "this is a placeholder file",
then IIS is not properly configured with an XML Handler.
To configure IIS 6.0 with an xml extension handler
1. Open IIS Manager for IIS 6.0. Expand the Web Site where the CMN
Web services are installed.
2. Right-click Autodiscover and click Properties.
3. On the Virtual Directory tab, click Configuration.
4. On the Mappings tab, click Add.
5. If you are using 32 bit IIS, click the Browse button and locate
%windir%\Microsoft.Net\Framework\v2.0.50727\aspnet_isapi.dll.
– OR –
If you are using 64 bit IIS, click the Browse button and locate
%windir%\Microsoft.Net\Framework64\v2.0.50727\aspnet_isapi.dll
6. Enter .xml for the extension.

7. Click OK on all dialog boxes.
44
Troubleshooting
To configure IIS 7.0 with Integrated Application pools

1. Open IIS Manager for IIS 7.0. Expand the root node and click
Application Pools.
2. Ensure the Managed Pipeline mode for QuestAutodiscoverAppPool
and QuestEWSAppPool are both set to Integrated.
3. Access https://<host>/autodiscover/autodiscover.xml, and ensure
you do not see the error message "this is a placeholder file".
4. From the Exchange server, open a web browser such as Internet
Explorer, and type https://<host>/EWS/Service.asmx (where
<host> is either <smtpdomain> or autodiscover.<smtpdomain>),
and ensure a .xml file appears and that you do not have any
certificate errors.
On the DNS server:

•) Ensure that the appropriate DNS entries have been made to route
<smtpdomain> or autodiscover.<smtpdomain> to the computer run-
ning the CMN Free/Busy Connector.
On the computer running CMN Free/Busy Web Services:

•) On the computer running CMN free/busy connector web services, run
the Get-CmnAutodiscoverConfig cmdlet, and verify that the CmnAvail-
abilityUrl is set to https://<host>/EWS/Service.asmx ((where <host>
is either <smtpdomain> or autodiscover.<smtpdomain>).
•) On the computer running CMN free/busy connector web services, ensure
that Get-CmnAvailabilityConfig is configured to communicate to the cor-
rect host and port for the computer running the CMN Domino Free/Busy
connector service.
On the computer running CMN Domino Free/Busy Connector

Service.
•) On the computer running the CMN Domino Free/busy Connector Ser-
vice, ensure the Domino service is properly configured using
Set-CmnDominoFreeBusyConfig.
•) Ensure the CMN Domino Free/busy connector service is running and
there are no errors in the event log.
•) Ensure Lotus Notes is properly configured to connect to your Domino
server.
•) If you see the following error in your event log: NAMELookups are
limited on this server to a size smaller than what would be
returned. See your Domino Administrator for more information.
1. Open the Notes.ini file on your Domino server and add or modify the
following entry: NAMELOOKUP_MAX_MB =<number>.
2. Increase this value until the issue is resolved.
45
Outlook/OWA Users Cannot See Free/Busy

Information for a Large Number of Users
If you see the following error message: The maximum message size quota for
incoming messages (65536) has been exceeded, you must increase the quota
by using the MaxReceivedMessageSize property on the appropriate binding
element.
If you are using OWA or Outlook and querying Free/Busy information for a
Domino user, edit the Web.Config file in the EWS folder on the CMN Web Server:
• Add the maxReceivedMessageSize property to the file and set it to a

large value.
<netTcpBinding>
<binding name="CMNFreeBusyClientSettings"
closeTimeout="00:01:00"
maxReceivedMessageSize="655360">
</binding>
</netTcpBinding>
Troubleshooting Foreign Domain

Issues
Check the Foreign Domain by ensuring the following:
• The foreign domain is created in Domino, and the Calendar System

property matches the CalendarDomain property set for the Person
Documents representing the users in Exchange and the
ForeignDomainName setting for the QCALCON server task.
• The Server name for the Foreign domain document is the name of the
server where the QCALCON Domino server task is installed.
46
Troubleshooting
Free/Busy Requests do not route to

registered Foreign Domain
In some installations, the Domino server does not properly route free/busy
requests to the registered Foreign Domain. You can determine where the
free/busy requests are being routed by temporarily enabling debug messages
for the Domino Schedule Manager.
To enable debug messages

1. At the Domino Server Console, enter: Set conf debug_sched_all=1
– OR –
Add Debug_sched_all=1 to your notes.ini file for the Domino server.
2. Create a meeting request for an Exchange user, and try to view

free/busy for that user.
3. Look for messages in the Domino Server Log such as:
SchMsgQHandles_New> Opening queues for <FOREIGN DOMAIN>
4. Try setting the ForeignDomainName in QCALCON to the value of
<FOREIGN DOMAIN> found on the server console output.
5. Restart QCALCON.
6. Retrieve free/busy information for this user again. Depending on the
installation of Lotus Domino Server, this value may be
LWPSCHEDGATEWAY.
7. Once free/busy is working, disable debug messages on the Domino
server.
Troubleshooting Exchange
Free/Busy Errors
To troubleshoot errors retrieving Free/Busy Information from Exchange, you can
use the Get-CmnExchangeFreeBusy cmdlet.
Get-CmnExchangeFreeBusy [-UserEmailAddresses] <String> [-StartDate]

<Date> [-EndDate] <Date> [-EwsUrl] <String> [-Credentials]
<String>[-ShowTentativeAsBusy] [<CommonParameters>]
This cmdlet will retrieve free/busy information for one or more uses directly from
Exchange using the same code used by the Exchange Free/Busy connector
service.
47
This cmdlet can be used to narrow down whether the problem is retrieving
Free/Busy information from Exchange, or the configuration of the QCALCON
Domino Server task or its communication with the Exchange Free/Busy
Connector Service.
Troubleshooting Domino Free/Busy

Errors
To troubleshoot errors retrieving Free/Busy information from Domino, you can
use the Get-CmnDominoFreeBusy cmdlet:
Get-CmnDominoFreeBusy [-UserEmailAddresses] <String> [-ServerName]

<String> [-Password] <String> [-StartDate] <Date> [-EndDate] <Date>
[-IdPath] <String> [<CommonParameters>]
This cmdlet will retrieve free/busy information for one or more uses directly from
Domino using the same code used by the Domino Free/Busy connector service.
This cmdlet can be used to narrow down whether the problem is retrieving
Free/Busy information from Domino, or the configuration of the CMN Free/Busy
Web Services and their communication with the Domino Free/Busy connector
service.
Troubleshooting using PowerGUI

You can use Quest PowerGUI to troubleshoot any issues you may have with
configuring all components of the CMN Free/Busy Connector.
Troubleshooting Web Services

To troubleshoot Web Services
1. From the Navigation Tree, select Diagnostics and

Troubleshooting | Test Web Services.
A table appears indicating if the Autodiscover and FBC EWS
subcomponents are installed.
2. Select Test DNS Host Name, and enter an SMTP Domain.

3. Select the DNS Host Name that was registered to the CMN Web
Server.
4. Click Test.
48
Troubleshooting
This verifies that the specified host name resolves to the computer
where the Domino server is installed.
5. Select Test IIS Configuration, and enter an SMTP domain.

6. Select the DNS Host Name that was registered to the CMN Web
Server.
7. Click the URLs to verify the IIS and DNS are properly configured.
Troubleshooting free/busy for Domino

users
To troubleshoot free/busy information for Domino users
1. From the Navigation Tree, select Post-Configuration Verification
and Troubleshooting | Troubleshoot free/busy for Domino
users.
2. From the Actions Pane, select Test Domino Server.
3. Enter the Domino server, credentials, and email address to test.
4. Click Test.
This retrieves free/busy information directly from the Domino Server
for a specified user.
5. From the Actions Pane, select Test free/busy through Exchange

to allow you to test free/busy for a Domino user through Exchange.
6. Enter the Exchange server, credentials, and email address to test.
7. Click Test.
8. This retrieves free/busy information directly from the Exchange
Server for a specified user.
You can also select Post-Configuration Verification and Troubleshooting |

Event Log to see if any error messages were logged.
Troubleshooting free/busy for Exchange

users
To troubleshoot free/busy information for Exchange users
Troubleshooting | Troubleshoot free/busy for Exchange
users.
2. From the Actions Pane, select Test Exchange Server.
3. Enter the Exchange server, credentials, and email address to test.
49
4. Click Test.
This retrieves free/busy information directly from the Exchange
Server for a specified user.
5. From the Actions Pane, select Test free/busy through Domino to

allow you to test free/busy for an Exchange user through Domino.
6. Enter the Domino server, credentials, and email address to test.
7. Click Test.
This retrieves free/busy information directly from the Domino Server
for a specified user.
8. From the Actions Pane, select Test Exchange Web Services URL.
A dialog box appears stating that PowerGUI will now launch the
Exchange Web Services URL in Internet Explorer.
9. Click OK.
Internet Explorer opens pointing to the Exchange Services URL.
You can also select Diagnostics and Troubleshooting | Application Event Log
to see if any error messages were logged.
Accessing SupportLink
Knowledgebase
You can access Quest SupportLink to get various knowledgebase articles.
To access SupportLink
Troubleshooting | SupportLink Knowledgebase.
2. From the Actions Pane, select SupportLink Knowledgebase.
SupportLink opens.
50
Appendix A:
Configuring CMN F/B
Connector Using cmdlets
• Running Cmdlets
• Configuring the Web Server Components
• Configuring the Lotus Notes Component
• Configuring the Exchange Server
Component
• Configuring the Domino Server Component
51
Running Cmdlets
Note: A PowerShell cmdlet must be run on the same computer as the FBC
subcomponent to which it will be applied.
For more information on PowerShell cmdlets, see the PowerShell
Administrator Guide.
To run the cmdlet

• Go to Start | Programs | Quest Software | Quest Coexistence
Manager for Notes | Free Busy Connector | Free Busy
Connector Management Shell.
– OR –
• Open the 32-bit version of PowerShell and type:
Add-PSSnapIn Quest.CMN.FreeBusy
Configuring the Web Server

Components
The Web Components consist of the CMN Autodiscover Web Service and the CMN
FBC EWS.
Configuring the Autodiscover Web Service

The Autodiscover Web Service is responsible for supplying Exchange with the
URL to the FBC EWS.
The following cmdlet sets the URL that the Autodiscover Web Service will return
to Exchange:
• Set-CmnAutodiscoverConfig -CmnAvailabilityUrl <String>

For example, you can use:
https://<HostName>/EWS/Service.asmx
... for the CmnAvailabilityUrl parameter, where <HostName> is:

autodiscover.<smptdomain> or <smtpdomain>
For example:
Set-CmnAutodiscoverConfig -CmnAvailabilityUrl
"https://targetHost.company.com"
To see what is already configured for the Autodiscover Web Service, enter:
Get-CmnAutodiscoverConfig
52
Configuring the FBC EWS
The FBC EWS communicates with the Quest CMN Domino Free/Busy Connector
Service to retrieve free/busy information for Domino Users.
The following cmdlet configures the FBC EWS:
• Set-CmnAvailabilityConfig -HostName <String> -PortNumber

<UInt32>
Where:
• HostName is the name of the computer where the Quest CMN Domino
Free/Busy Connector Service is installed (or localhost if it is installed
on the same computer)
• PortNumber is the TCP port on which the service is listening
For example:
Set-CmnAvailabilityConfig -HostName
DominoFreeBusyHost.company.com -PortNumer 8900
To retrieve the current settings for the service, enter the following cmdlet:
• Get-CmnAvailabilityConfig.
Configuring the Lotus Notes

Component
The Lotus Notes component is the Quest CMN Domino Free/Busy Connector
Service, which retrieves free/busy information from the Domino Server and
returns it back to the FBC EWS.
Type the following:
1. $securePassword = Read-Host -AsSecureString -Prompt "Enter

Domino User Password"
2. Type your Domino password and click Enter.
3. Set-CmnDominoFreeBusyConfig [-DominoServerName <String>]
[-DominoPassword <SecureString>]
[-DominoUserFetchIntervalInMinutes <UInt32>]
[-DominoUserSmtpDomains <String>] [-ListeningPort
<UInt32>] [-FreeBusyCacheTimeoutInMinutes <UInt32>]
[-DominoIdFilePath <String>][<CommonParameters>]
Where:
• DominoServerName is the name of the Domino server
53
• DominoPassword is the password of the Domino user

($securePassword)
• DominoUserFetchIntervalInMinutes is the time set to refresh the list of
Domino users
• DominoUserSmtpDomains add the fully qualified SMTP domain for a
Domino mail domain
• ListeningPort is the listening port for the Quest CMN Domino Free/Busy
Connector Service. The product uses port 8960 and 8961 for TCP
communication. These ports can be adjusted if required using the
provided cmdlets. Ensure these ports are not in use and not blocked
by any firewall applications.
• FreeBusyCacheTimeoutInMinutes is the interval to cache the free/busy
information for the Quest CMN Domino Free/Busy Connector Service
• DominoIdFilePath is the path to the ID file for a Domino user. This file
path must be stored on the same computer where the CMN Domino
Free/Busy Connector Service is installed.
For example:
$securePassword = Read-Host -AsSecureString -Prompt "Enter

Domino User Password"
Set-CmnDominoFreeBusyConfig -DominoServerName
CompanyDominoServer.company.com -DominoPassword
$securePassword -DominoUserFetchIntervalInMinutes 20
-DominoUserSmtpDomains DominoSmtpDomain.company.com
-ListeningPort 9800 -FreeBusyCacheTimeoutInMinutes 10
The following parameters are mandatory to configure the Domino Free/Busy

Connector Service:
• -DominoServerName
• -DominoPassword
• -DominoUserSmtpDomains
Service Logon Account

On some installations of Lotus Notes, you may need to set the service logon
account to be a domain user.
To set the Service Logon account

1. Open Computer Management.
2. Select Services and Applications | Services | Quest CMN
Domino FreeBusy Service.
3. Right-click Properties.
4. Click the Log On tab and specify an account, if required. The account
must have access to run Lotus Notes.
54
Configuring the Exchange Server
Component
The Exchange Server component is the Quest CMN Exchange Free/Busy
Connector service, which retrieves free/busy information from Exchange and
returns it back to the CMN Domino Server Task (QCALCON).
The CMN Exchange Free/Busy Connector Service requires the Exchange Web
Services (EWS) URL for your Client Access Server (CAS). This URL is formatted
as the following:
https://<exchangeservername>/EWS/Exchange.asmx
If you do not know the name of the CAS server to use, or you are using a hosted
Exchange server, you can use the Get-CmnExchangeWebServicesUrl cmdlet to
retrieve the EWS Url.
1. Type: $credential = get-credential.

This displays a dialog that will prompt for your credentials. Enter the
credentials of a mail-enabled user. This step is optional and should be
used in scenarios such as Exchange Online where the currently
logged-on user does not have access to the Exchange Server.
2. Type: $ewsUrl = get-cmnExchangeWebServicesUrl -EmailAddress

<emailAddress> -Credentials $credential
... where
• <emailAddress> is the email address of a valid Exchange User
• credentials are the credentials collected in step 1.
After running the cmdlet, the $ewsUrl contains the Exchange Web Services URL.
You can use this variable in the Set-CmnExchangeFreeBusyConfig and
Get-CmnExchangeFreeBusy cmdlets, as required in the procedure below.
To configure the CMN Exchange Free/Busy Connector Service

1. Type: $mailEnabledCredentials=Get-Credential
This will display a dialog prompting for the credentials. Enter the
credentials of a mail-enabled user.
2. Type:
Set-CmnExchangeFreeBusyConfig [-EwsUrl <String>]
[-ShowTentativeAsBusy <String>][-ListeningPort <UInt32>
[-FreeBusyCacheTimeoutInMinutes <UInt32>] [-Credentials
<PSCredential>] [<CommonParameters>]
... where:
55
• EwsUrl is the URL of the FBC EWS, for example,

https://<exchangeservername>/EWS/Exchange.asmx. This URL must
be resolvable from the computer where CMN Exchange Free Busy
Service is installed.
• ShowTentativeAsBusy, if set to true, shows a user that had a tentative
status in Outlook as busy in Lotus Notes
• ListeningPort is listening port for the Quest CMN Exchange Free/Busy
Connector Service. The product uses port 8960 and 8961 for TCP
communication. These ports can be adjusted if required using the
provided cmdlets. Ensure these ports are not in use and not blocked
by any firewall applications.
• FreeBusyCacheTimeoutInMinutes is interval to refresh the cache for
the Quest CMN Exchange Free/Busy Connector Service
• Credentials are the credentials of a mail-enabled user in Exchange.
These credentials are the credentials specified in step 1.
The following are examples of the above commands:
C:\PS> $mainEnabledDomainUserCredentials
C:\PS> Set-CmnExchangeFreeBusyConfig -Credentials

$mainEnabledDomainUserCredentials
https://<ExchangeCASServerName>/EWS/Exchange.asmx
C:\PS> Set-CmnExchangeFreeBusyConfig -EwsUrl

https://ExchangeClientAccessServer.company.com/EWS/Exchan
ge.asmx -ListeningPort 9850 -FreeBusyCacheTimeoutInMinutes
10 -Credentials $mainEnabledDomainUserCredentials
Configuring the Domino Server

Component
The Domino Server component is the CMN Domino Server Task (QCALCON),
which intercepts free/busy requests for Exchange users and communicates with
the Quest CMN Exchange Free/Busy Connector Service.
To configure the CMN Domino Server Task (QCALCON)

1. Type:
Set-QCalConConfig [-ConfigPath] <String>
[-ForeignDomainName <String>] [-HostName <String>]
[-PortNumber <UInt32>]
Where:
• ConfigPath is the UNC path to QCalCon.exe.config if it is not installed
locally
56
• ForeignDomainName is the SMTP Domain for the Foreign Domain
Name
• HostName is the TCP host where the Quest CMN Exchange Free/Busy
Connector Service is installed
• PortNumber is the TCP port used by the Quest CMN Exchange
Free/Busy Connector Service is installed
The following is an example of the above command:
C:\PS> Set-CmnQCalConConfig -ForeignDomainName Exchange

-HostName CmnEx changeFreeBusyHostName.company.com -Port
9540
If you did not install the PowerShell SnapIn on the Domino server, you can
modify it from another computer using the -ConfigPath parameter. This
parameter specifies the UNC Path to QCALCON.exe.config file located in the
Domino server directory.
If a UNC path to this directory does not exist, you can manually edit the
Qcalcon.exe.config file.
Caution: Be very careful when manually editing the Qcalcon.exe.config

configuration file. A single typo, misspelling or inadvertent extra character
could disable the entire F/B Connector system.
To manually edit the Qcalcon.exe.config file

1. Open QCALCON.exe.config in a text editor such as Notepad.
2. Edit the ForeignDomainName and the name of the computer running
the Quest CMN Exchange Free/Busy Connector Service (as shown
below).
<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<appSettings>
<add key="ForeignDomainName" value="<ForeignDomainName>"/>
</appSettings>
<system.serviceModel>
<bindings>
<netTcpBinding>
<binding name="CMNFreeBusyClientSettings"
closeTimeout="00:01:00">
</binding>
</netTcpBinding>
</bindings>
57
<client>
<endpoint name="CMNFreeBusyServiceEndpoint"
address="net.tcp://<HostName>:<Port number>FreeBusyServiceHostLibrary"
binding="netTcpBinding" bindingConfiguration="CMNFreeBusyClientSettings"
contract="Quest.CMN.FreeBusy.FreeBusyServiceHostLibrary.IFreeBusyContract"/>
</client>
</system.serviceModel>
</configuration>
3. Save the document.

4. Restart QCALCON server task. QCALCON server task is set to
automatically start when the Domino Server starts, but does not
start after installing the product.
To verify if QCALCON is running, type the following on the Domino Server

Console: Show tasks
If it is running, you should see an entry for QCALCON.
To shut down QCALCON, type the following on the Domino Server console:
tell qcalcon quit
To start QCALCON, type the following on the Domino Server console:
Load qcalcon
To restart QCALCON, do one of the following:
• Type: restart server to restart the entire Domino server and apply
changes.
– OR –
1. Type: tell QCALCON quit
2. Type: load qcalcon
58
Glossary
This glossary contains definitions taken from Microsoft publications.
C
Coexistence Manager for Notes
A service that provides the important "missing pieces" of
a Notes–Exchange coexistence achieved with the Microsoft
Transporter Suite.
Common Name
The identifying name assigned to a directory object,
typically a container. A common name must be unique
within a context.
D
Domain Name System (DNS)
A hierarchical, distributed database that maps domain
names to various types of data, including IP addresses.
Every node on the Internet is identified by a unique,
numerical IP address of the form 255.255.255.255,
although any particular IP address may be associated with
0, 1 or more domain names. The DNS defines the
associations of domain names to their corresponding IP
addresses.
Domino
The name of the applications and messaging server
program for the Lotus Corporation's Lotus Notes product.
For more information, see www.ibm.com.
Domino Server Task

Also known as QCALCON. Intercepts free/busy requests for
Exchange users and communicates with the Exchange
Free/Busy Connector Service.
F
Free/Busy connector service
A service that allows Exchange users to see the availability
of Domino users, and conversely, allows Domino users to
see the availability of Exchange users.
59
L
Lotus Notes
An IBM tool that provides World class e-mail, calendar,
scheduling and collaboration capabilities. For more
information, see
http://www-142.ibm.com/software/products/ca/en/
domino.
N
Notes Migrator for Exchange
A migration tool that converts users from Lotus Notes to
Microsoft Exchange and Exchange Online. It migrates
users’ e-mail, calendars, tasks and personal address
books to the users' new mailboxes on the
Exchange/Exchange Online server.
P
PowerGUI
An extensible graphical administrative console for
managing systems based on Windows PowerShell.
PowerShell
A Windows command-line shell and scripting language
designed specifically for system administrators and built on
top of the Microsoft .NET Framework. For more information,
see www.microsoft.com.
S
Server Certificate
An electronic document which uses a digital signature to
bind together a public key with an identity.
Simple Mail Transfer Protocol (SMTP)

The standard TCP/IP protocol that governs message
transmission over the Internet, by addresses in the form
name@domain.com. SMTP is the default transport protocol
for Microsoft Exchange.
60
INDEX F
FBC EWS (CMN)
configuring with cmdlets 53
A foreign domain troubleshooting 46
Autodiscover web service (CMN) Free/Busy Connector
configuring with cmdlets 52 configuring with PowerGUI 30, 32
Availability web service (CMN) introducing 9
configuring with cmdlets 53 uninstalling 21
B H
Binding, creating 27 hosted exchange 25
C I
certificates 25 introducing Free/Busy Connector 9
configuring
DNS 23 L
Domino Server 33 Lotus Notes component (CMN)
Domino server 29 configuring with cmdlets 53
Domino Server clusters 37 Lotus users cannot see free/busy
Exchange server 28 information
for a large number of users 43
D
deployment of F/B Connector M
subcomponents 14, 18 multi-domain support 36
DNS multiple Domino servers 37
configuring 23
Domino clusters 37 O
Domino components (CMN) Outlook users cannot see free/busy
configuring with cmdlets 56 information
Domino Free/Busy for a large number of users 46
troubleshooting 48 for Domino users 44
Domino Server
configuring 33 P
Domino server PowerGUI 18, 19
configuring 29 opening 29
DominoServer troubleshooting with 48
configuring multiple servers 37
Q
E Quest PowerGUI 18, 19
equivalent domains 36
EWS (CMN) R
configuring with cmdlets 53 recommended deployment of F/B
Exchange Free/Busy Connector
troubleshooting 47 subcomponents 14, 18
Exchange server
configuring 28 S
Exchange server component (CMN) subcomponents of F/B Connector,
configuring with cmdlets 55 deployment of 14, 18
SupportLink 63
knowledgebase 50
61
T
troubleshooting 41
Domino free/busy 48
Exchange free/busy 47
foreign domain 46
free/busy for Domino users 49
free/busy for Exchange users 49
Lotus users cannot see Free/Busy
for a large number of users 43
Outlook users cannot see
Free/Busy for a large number of
users 46
Outlook users cannot see
Free/Busy for Domino users 44
SupportLink knowledgebase 50
using PowerGUI 48
web services 48
U
uninstalling Free/Busy Connector 21
62
About Quest Software
Now more than ever, organizations need to work smart and improve efficiency.
Quest Software creates and supports smart systems management
products—helping our customers solve everyday IT challenges faster and easier.
Visit www.quest.com for more information.
Contacting Quest Software

Email info@quest.com
Mail Quest Software, Inc.
World Headquarters
5 Polaris Way
Aliso Viejo, CA 92656
USA
Web site www.quest.com
Refer to our Web site for regional and international office information.
Contacting Quest Support

Quest Support is available to customers who have a trial version of a Quest
product or who have purchased a Quest product and have a valid maintenance
contract. Quest Support provides unlimited 24x7 access to SupportLink, our
self-service portal. Visit SupportLink at http://support.quest.com.
From SupportLink, you can do the following:
• Retrieve thousands of solutions from our online Knowledgebase

• Download the latest releases and service packs
• Create, update and review Support cases
View the Global Support Guide for a detailed explanation of support programs,
online services, contact information, policies and procedures. The guide is
available at: http://support.quest.com.
63
64

Free Busy Connector User Guide 103

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Free Busy Connector User Guide 103

Uploaded by

Copyright:

Available Formats

Coexistence Manager for Notes

Free/Busy Connector 1.0.3

Quest Software World Headquarters

All CMN documentation is intended for network administrators, consultants,

STEP 5-3: CONFIGURE THE EXCHANGE FBC

TROUBLESHOOTING EXCHANGE FREE/BUSY ERRORS . . . . . . . . . .47

About CMN’s Free/Busy Connector

CMN’s Free/Busy (F/B) Connector is a coordinated set of applications that

How the Free/Busy Connector

CMN’s bidirectional Free/Busy Connector therefore contains these five

• Free/Busy Autodiscover Web Service: Tracks the location of the

• Domino Free/Busy Connector Service: Translates Exchange F/B

Outlook User Retrieves F/B Data for a

Notes User Retrieves F/B Data for an

1. The Domino server requests Sally’s free/busy information from the

Deployment of F/B Connector

Installation and Configuration Overview

1. Plan your FBC installation and configuration.

If your configuration will vary from the typical, recommended configuration as

About Quest PowerGUI and

The CMN Free/Busy Connector PowerShell Administrator Guide (a separate PDF

In our typical, recommended configuration, Quest PowerGUI and the PowerPack

To manually install the CMN Free/Busy Connector PowerPack, on a

On Domino Server: Install QCALCON

On CMN FBC Web Server: Install

On CMN Exchange FBC Server:

If Necessary: Install Quest

If You Want to Uninstall CMN Free/Busy Connector

Use CMN’s Directory Connector to define a bidirectional update (a pair of

You may choose instead to perform a directory synchronization manually, in

To synchronize Domino mail users to Exchange contacts:

1. Using the Exchange Management Console, create a mail contact for a

To synchronize Exchange mail users to Domino contacts:

To Add a Foreign Domain Document

1. As a Domino Administrator, select the Configuration tab.

Network Load Balancing

Domain Name System (DNS) Configuration

For Exchange to get free/busy information from the domain supported by a

The "autodiscover." part of this URL is optional, but it must be defined

Use this method if you are using Microsoft DNS.

ADDING A DNS HOST

To add a DNS host:

For more information about registering and verifying a domain, see

Web Services Certificates

You can obtain a certificate from either of two sources:

Requesting and Installing a Certificate Using IIS 6.0

4. Select Create a new certificate request, and click Next.

To install the certificate using IIS 6.0:

Requesting and Installing a Certificate Using IIS 7.0

Installing the certificate using IIS 7.0:

Requesting a Certificate from a Local CA

6. In the Certificate Template box, select Web Server.

Requesting a Certificate from a Public CA

Exchange Server Configuration

Domino Server Configuration

The CMN Free/Busy Connector subcomponents can also be installed in

Step 5-1: Open PowerGUI

For more information on PowerGUI, see the CMN Free/Busy Connector

Step 5-2: Configure Web Server and Lotus

To configure the Autodiscover Web Service on the CMN Web Server:

To configure the FBC EWS on the CMN Web Server:

5. Enter the port number of the computer hosting the Domino

Step 5-3: Configure the Exchange FBC Service