Changelog: Minor changes have been done in the connection doc, smarthost removed and forwarding address added.
For what I’ve seen here is a very large gap that I want to cover, Neil Hobson wrote a very good article about Domino to Exchange 2007
with Transporter Suite. It can be found here.
Also Elan Shudnow wrote a nice article regarding Free/Busy, a little bit more deep-dive into it and how it works, it can be found here.
Both of those articles used Exchange 2007 with Public Folder, this is not my case so here are a bit differences.
In my case, I’m not using any native tools, since Microsoft decided to not support and update their Transporter Suite to fit Exchange 2010
it was up to 3rd part suppliers.
I’m using Quest’s Coexistence Manager for Notes and I haven’t found any great guide or information on a real-world scenario.
That’s why this article is born J
I’ve decided to split this article into two parts, or else it will be very long.
These parts will cover SMTP routing and Free/Busy between the systems, the first part will cover the Infrastructure setup and Domino setup.
The second part will cover the CMN and Exchange configuration.
DirSync is not covered in neither of these parts.
Maybe I’ll write an article about that later if it would be of any interest?
Any form of feedback on the article would be nice, good as bad.
This is an overview of my Infrastructure in this setup.
And a little picture on the SMTP Routing mailflow setup and also here’s about the FreeBusy (F/B) information between the systems.
On the CMN server there’s a “connector” called QCalCon installed which handles the F/B between the systems, it sends and receives
the information between them like a collector. I will attach a picture about it below.
Here is some short information about the process (copied from Quest’s document “Free Busy connector user guide.pdf” and a little bit edited).
When Outlook requests free/busy information for Jonas, the following occurs:
1. Exchange resolves “target.local” through DNS. DNS has a zone called target.local which contains a host called
autodiscover.target.local. The host name must match the common name (of the certificate you requested) where
Coexistence Manager for Notes – Free/Busy Connector is installed.
Exchange connects to https://autodiscover.target.local/autodiscover/autodiscover.xml to query the location of the
Availability Web Service from which to receive free/busy information.
The Autodiscover Web Service returns the URL of the Availability Web Service where CMN Free/Busy Connector is installed.
2. Exchange requests free/busy information from this URL.
3. The Free/Busy Availability Web Service communicates with the Quest CMN Domino Free/Busy Connector Service to get free/busy
information. The Quest CMN Domino Free/Busy Connector Service configuration file is configured with Domino Server name,
Directory Server name, ID path, and secure password where your Domino server is installed.
4. The Quest CMN Domino Free/Busy Connector Service queries the Domino server for the free/busy information.
5. Jonas’s free/busy information is returned back to the Exchange server, where it is displayed to Klas.
When Lotus Notes requests free/busy information for Klas, the following occurs:
1. The Domino server requests free/busy information from QCALCON. QCALCON Domino Server Task is installed on the Domino server,
and configured to listen for “Exchange” calendar requests.
2. QCALCON communicates with the Quest CMN Exchange Free/Busy Connector Service to retrieve free/busy information.
3. The Quest CMN Exchange Free/Busy Connector Service retrieves free/busy information from Exchange using Exchange Web Services
4. Klas’s free/busy information is returned back to the Domino server (through the Exchange Free/Busy Service and QCALCON),
where it is displayed to Jonas.
The first thing to add when using sub-domains is to add the sub-domain into the global domain document.
It’s done in Configuration/Messaging/Domains and selecting the Global domain and choosing edit the domain.
In the field “Alternate Internet domain aliases:” there should be added the following domain in my setup:
Next thing to configure and setup is the Foreign SMTP Domain, this is added in Configuration/Messaging/Domains.
Choose “Add domain” and type in the following information.
Domain type: Foreign SMTP Domain
Internet domain: exch.target.local
Domain name: ToExchange
Then it’s time to add the Foreign Domain to be able to have the Free/Busy information between the systems.
This is added in Configuration/Messaging/Domains by choosing “Add domain”.
Domain type: Foreign Domain
Foreign domain name: Exchange
Gateway server name: domino/target
Gateway mail file name: mail.box
Calendar server name: domino/target
Calendar system: Exchange
Next thing to add is a connection document, it’s done in Configuration/Messaging/Connections and by pressing “Add Connection”.
In this document, it needs to be filled with information like source server, source domain, destination server and domain, destination ip,
Connection type: SMTP
Source server: domino/target
Connect via: Direct connection
Usage priority: Normal
Destination server: cmn.target.local
Destination domain: ToExchange
Optional network address: 172.16.2.20
Replication task: Disabled
Schedule: It should run 24 hours per day
Since we have a matching connection document with the Foreign Domain document we don’t need the smarthost configured. This is deleted in this version, v1.1.
When a Domino user is migrated, the Calendar information will be changed, another value that’s changed it the Mail System,
it will be set to: Other Internet Mail, then Domino knows that it doesn’t have the responsible for the mailbox.
And another option that will be changed is the forwarding address will be changed, in my environment it will be:
Klas.Andersson@exch.target.local since we use exch and domino as coexistence sub-domains.
I will attach two pictures about this, the first one shows the Other Internet Mail settings and the other one shows the calendar information.
This part is completed, next part will cover the Exchange configuration and the CMN configuration.
For setting up CMN from Quest, it’s recommended to use a PSO (certified consultant)!
Feel free to give feedback on the article!
I hope this was interesting and informative, thanks for reading!