Part 7: Configuring Coexistence Manager for Notes with Exchange 2013 On-premise

[Andersson]

Published: 2013-11-11
Updated: -
Version: 1.0

 

The previous post took us through the technical prerequisites, these should now be ready and in place before installing and configuring Coexistence Manager for Notes (CMN).

Before going into any details, if you are planning to do have a coexistence scenario between Domino and Exchange, you may want to consider using Dell Software’s Coexistence Manager for Notes. However, one important thing to mention is that there is a requirement from the vendor, to use certified people for the project.

This blog post is based on Coexistence Manager for Notes version 3.5.1.51.

Some of you might know that I wrote some articles regarding this topic two years ago, the configuration has changed a bit. I want to share it with the community and I hope you enjoy reading it.

 

Read the other parts:

Part 1: Migrations – Overview
Part 2: Prerequisites for Domino/Notes migrations
Part 3: Migrating Domino/Notes to Exchange 2013 On-premise
Part 4: Migrating Domino/Notes to Office 365
Part 5: Migrating Resources Mailboxes, Mail-In databases and Groups
Part 6: Prerequisites for Coexistence Manager for Notes with Exchange 2013 On-premise
Part 8: Configuring Coexistence Manager for Notes with Office 365
Part 9: Prerequisites for Migration Manager Exchange
Part 10: Migrating User Mailboxes from Exchange 2003 to Exchange 2013 using Migration Manager
Part 11: Migrating User Mailboxes from Exchange On-premise to Office 365

 

Installation of Coexistence Manager for Notes (CMN)

There is no need for further description on how to proceed with the installation of CMN, select the features that should be used, then it’s a “next-next-finish” installation.

 

Licensing

Startup “Quest Coexistence Manager for Notes Management Console” and go to “Common – Licensing” to provide a valid license file.

 

Mail Connector configuration

This post is not about how to create the mail flow configuration between Exchange and Domino since I assume, if you’re working and reading this topic, you’re familiar with how to create Send/Receive connectors in Exchange and Domain documents and Connection documents in Domino.

 

I will, however, post an article on how to configure Exchange and Domino regarding the mail flow.

Let’s configure CMN regarding mail flow, startup “Quest Coexistence Manager for Notes Management Console” and go to “Mail Connector”.

 

Go to “Inbound Servers”, remove any default values, add all incoming servers, both source and target servers. Just make sure to specify their function (Server type).

 

When all are added, it will look similar to the picture below.

 

Go to “Outbound Servers”, remove any default values. Either use the “Add” button or if you’re about to add the same as the Inbound, then use the “Copy from Inbound Servers” button.

 

After the servers are added, it will look similar as the picture below.

 

For Notes Doc Links, I will use the option “Notes links (Requires Notes client on clients)”, but you should select the option that will provide the best solution in each scenario.

 

I’m using the default settings for Network settings.

 

If needed, TLS can be used and it’s in this window the configuration takes place. In my lab environment, I’m not using TLS.

 

I’m using the default settings for Advanced Message settings.

 

I prefer to use the option “Rewrite Notes Common Names”, so it becomes more user-friendly and easier to read than a long Domino displayname.

Other options are not enable, use them if needed.

 

I’m using the default settings for Message Content Limits settings.

 

In the lab environment I’m not using the sub-domain option. However, if needed, here is the place to configure it.

 

Active Mail, it requires Notes client 7.0.3, 7.0.4 or 8.0 on the CMN server. It also requires the Notes client on the clients for being able to use the feature.

 

Default settings in Notification messages.

 

Here is a sample of the “ResourcesMap.tsv” file that’s used for mapping resources so they can be booked from Exchange/Outlook.

 

Import the “ResourcesMap.tsv” file, just verify the imported items and change the “Resource type” if they are not correct or configured.

 

Directory Synchronization configuration

Let’s walk through the directory synchronization, which is required to get Free/Busy to work properly. It’s required to provision users as contact objects.

With CMN 3.5.x, the directory synchronization uses a new module, which uses SQL for its configuration. Just see my picture below as an example of the SQL configuration.

The configuration can be found under “Directory Connector – SQL Settings”.

 

Domino Users synchronization, go to “Directory Connector – Connector Settings”. Press “Add” button and “Next” in the window.

 

Give the connector a friendly name like “Domino to AD – Users”, verify the “Direction” value and press “Next”.

 

Type in Source information: domino server, username, password and LDAP port.

 

Type in Target information: domain controller, username, password and LDAP port.
In my scenario, I’ve specified a domain controller, so I enabled that checkbox.

Specification of domain controllers are common in scenarios where you want to use the closest domain controller possible for faster reading and writing.

 

Select the object to process – “Users & Contacts”, specify the OU that should be synchronized.

 

Specify the target OU where objects will be created, also specify Target Search Base DN and load the Exchange attributes from AD and add them.

If you want to specify a different targetAddress domain (forwarding) use the “Enable Internal Routing Domain” option and specify a domain in the value field.

 

No connector order is selected.

 

A synchronization schedule is created, in my example 5 AM and 2 PM. The appropriate timing depends on how often and how many changes are done within Domino.

 

Press “Finish” to close the final window.

 

Groups synchronization, go to “Directory Connector – Connector Settings”. Press “Add” button and “Next” in the window.

 

Give the connector a friendly name like “Domino to AD – Groups”, verify the “Direction” value and press “Next”.

 

Type in Source information: domino server, username, password and LDAP port.

 

Type in Target information: domain controller, username, password and LDAP port.
In my scenario, I’ve specified a domain controller, so I enabled that checkbox.

Specification of domain controllers are common in scenarios where you want to use the closest domain controller possible for faster reading and writing.

 

Select the object to process by selecting “Groups” and specify the OU that should be synchronized.

 

Specify the target OU where objects will be created, also specify Target Search Base DN and load the Exchange attributes from AD and add them.

If you want to specify a different targetAddress domain (forwarding) enable the option “Enable Internal Routing Domain” and specify a domain in the value field.

 

No connector order is selected.

 

A synchronization schedule is created, in my example 5 AM and 2 PM. The appropriate timing depends on how often and how many changes are done within Domino.

 

Press “Finish” to close the final window.

 

Resources synchronization, go to “Directory Connector – Connector Settings”. Press “Add” button and “Next” in the window.

 

Give the connector a friendly name like “Domino to AD – Resources”, verify the “Direction” value and press “Next”.

 

Type in Source information: domino server, username, password and LDAP port.

 

Type in Target information: domain controller, username, password and LDAP port.
In my scenario, I’ve specified a domain controller, so I enabled that checkbox.

Specification of domain controllers are common in scenarios where you want to use the closest domain controller possible for faster reading and writing.

 

Select what object to process “Resources”, specify the OU that should be synchronized.

 

Specify the target OU where objects will be created, also specify Target Search Base DN and load the Exchange attributes from AD and add them.

If you want to specify a different targetAddress domain (forwarding) enable the option “Enable Internal Routing Domain” and specify a domain in the value field.

 

No connector order is selected.

 

A synchronization schedule is created, in my example 5 AM and 2 PM. The appropriate timing depends on how often and how many changes are done within Domino.

 

Press “Finish” to close the final window.

 

 

Free/Busy configuration

Since we now have the contact objects provisioned and the mail flow working, it’s time for the most involved part of the coexistence, the Free/Busy configuration.

 

Qcalcon configuration

The installation of Qcalcon on a Domino server is a standard “next-next-finish” procedure and a Domino server task will be created during the installation. The software can either be installed on an existing server or a dedicated Free/Busy server (I would recommend the latter IF possible).

 

Start the Qcalcon configuration by starting the “Coexistence Management Console”, see picture below.

 

Configure Qcalcon with the following properties (as an example):

“Gateway Mail File Name: mail.box” (verify with Domino Administrator on which to use)
”Quest Exchange Free/Busy Connector Service Endpoint: cmn35“ (resolvable DNS name to CMN server)

Note: You need to provide a valid license before the software can be used.

 

Domino configuration, go to the CMN server and start the CMN console, then go to “Domino Free/Busy Connector”.

Type in Domino configuration;
”Domino Server Name: domino/target” (specify server where Qcalcon is installed)
”Domino User fetch interval in minutes: 15”
”Domino User SMTP domain: target.local”
”Domino ID file path: C:\Temp\mmig.id” (Browse and select the ID file)
”Domino Password: *****” (Type in the password for that ID file)
”Enable Performance counters: Check”

 

Go to “Quest Web Services”

Type in Domino configuration;
”Quest Autodiscover Host Name: target.local”
”Quest Domino Free/Busy Connector Host Name: localhost”

Don’t forget to create (if not done already as specified in part 6) the AvailabilityAddressSpace, or Free/Busy won’t work as expected.

 

Exchange configuration, let’s finish the Free/Busy configuration by completing the Exchange part by going to “Exchange Free/Busy Connector – Exchange Free/Busy”.

Type in Exchange configuration;
”Exchange Server location: EWS Endpoint” (more about these options can be found in the User Guide)
”Exchange Host Name: mail.testlabs.se”
”Exchange Online: Unchecked”
”Exchange Username: sa-cmnfb@testlabs.se”
”Exchange Password: *****”
”Show tentative As Busy: Yes”
”Enable Performance Counters: Enable”

Use the Test button to verify that the functionality is working as expected.

Note: Certificate needs to be deployed before a successful test.

 

Additional Configurations

 

Certificate/IIS

Coexistence Manager relies on certificates since it’s using HTTPS for requests. This is important to understand.

The provided “Quest Autodiscover URL” and “Quest EWS URL” is based on the value entered in the “Quest Autodiscover Host Name” field. This common name is used during Free/Busy requests and is required to be in the certificate used in IIS. It should be bound to IIS and the “QuestFreeBusy” website.

 

Once the certificates have been deployed into the CMN server and IIS, use the Test buttons in the CMN console to verify the Quest Autodiscover functionality. In most cases, the autodiscover DNS record is pointed to the Exchange so, in order to test this functionality, use the host file and point it to CMN server.

A last thing to verify is that the “QuestFreeBusy” website is enabled for HTTP (80) and HTTPS (443) traffic, since it’s a requirement.

 

Note: If using internal PKI solution, make sure to deploy the whole certificate chain to the involved servers. When it comes to Office 365 deployments, this will be discussed in the next blog post.

 

Autodiscover

In most environments, the autodiscover DNS record is pointed to the Exchange. The workaround for proper flow of Free/Busy requests is to add a line into the host file at the CAS server(s).

 

Like the example below:

 

The Autodiscover is used since the mail contacts have a targetAddress with “@target.local” and there is a configured value for that domain in the AvailabilityAddressSpace configuration. Because of that, the request ends up checking these contacts Free/Busy externally via Autodiscover, which is pointed to CMN.

 

EWS/WebServices

Just make sure to verify that the value configured in the InternalUrl and ExternalUrl is found in the Exchange certificate. And also, if using Internal PKI, that the whole chain is deployed to the involved servers and clients.

 

Verification of functionality

 

Notes client (source)

Mail flow

 

A mail is sent from the Lotus Notes client (8.5.x) to two users that were migrated and now have an Exchange mailbox and are using Outlook 2013.

The mail is a standard mail, see picture below.

 

During the transport, these actions are being logged into the CMN.log file on the CMN server, some related entities can be found below:

 

2013-11-10 14:13:25,914 INFO CMN.logging [5] – Connection received from 172.16.1.16.
2013-11-10 14:13:26,274 INFO CMN.logging [5] – Message Number [1] on Thread [5] from Domino (172.16.1.16:3157) to Exchange (172.16.1.12:25): Connection established.
2013-11-10 14:13:41,900 INFO CMN.logging [Proxy 1] – Message Number [1] on Thread [3] from Domino (172.16.1.16:3157) to Exchange (172.16.1.12:25): Processed Message ID: OFA35F4382.5A84A034-ONC1257C1C.00482E50-C1257C1C.0048A376@target.local – Size: 578 – From: Jonas.Andersson@target.local – To: Anette.Andersson@exchange.testlabs.se, Klas.Andersson@exchange.testlabs.se – Processing Time: 1.792 Seconds – Changes: ActiveMailRemovedExtraneousAttachment, ActiveMailRemovedOnd, MimeModified

 

In the destination mailbox it should look like the picture below

 

And the reply from Outlook ends up in the source mailbox (Notes), just like the picture shows below

 

Calendar Free/Busy

A Free/Busy request was done by arranging a new meeting in the Notes client and selecting the migrated users. If the busytime lookup is working as expected, it should look similar to the picture below:

 

During the busytime lookup requests, these actions are being logged into the QCalCon.wlog and ExchangeFreeBusyService.wlog file on the CMN server. Some examples on log entries can be found while doing the busytime lookup, see below:

 

QCalCon.wlog:

2013-11-10 17:24:12,362 [LWPSCHEDGATEWAY] INFO ScheduleRequestManager – Message retrieved from queue
2013-11-10 17:24:12,362 [11] INFO ScheduleRequestManager – ScheduleRequestHandler() enter
2013-11-10 17:24:12,362 [11] INFO ScheduleRequestManager – NotesInitThread
2013-11-10 17:24:12,362 [11] INFO ScheduleRequestManager – Cast thread parameter to SchMsgWrapper instance
2013-11-10 17:24:12,362 [11] INFO ScheduleRequestManager – Release SCHMSG instance from SchMsgWrapper instance
2013-11-10 17:24:12,362 [11] INFO ScheduleRequestManager – Process SCHMSG message
2013-11-10 17:24:12,362 [11] INFO ScheduleRequestManager – SchContainer_DupHandle: Duplicate SCHMSG hContainer handle
2013-11-10 17:24:12,362 [11] INFO ScheduleRequestManager – SchContainer_GetRequest: Get hContainerObject request from message hContainer
2013-11-10 17:24:12,362 [11] INFO ScheduleRequestManager – UserNameList: 2
2013-11-10 17:24:12,362 [11] INFO ScheduleRequestManager - Anette.Andersson@exchange.testlabs.se
2013-11-10 17:24:12,362 [11] INFO ScheduleRequestManager - Klas.Andersson@exchange.testlabs.se
2013-11-10 17:24:12,362 [11] INFO ScheduleRequestManager – ClientNameList: 0
2013-11-10 17:24:12,362 [11] INFO ScheduleRequestManager – DominoServerNameChain:
2013-11-10 17:24:12,362 [11] INFO ScheduleRequestManager – Call GetFreeBusyForUsers
2013-11-10 17:24:12,362 [11] INFO ScheduleRequestManager – GetFreeBusyForUsers() enter
2013-11-10 17:24:12,362 [11] INFO ScheduleRequestManager – GetEmailsFromList() enter
2013-11-10 17:24:12,362 [11] INFO ScheduleRequestManager – Create SmtpEmailList
2013-11-10 17:24:12,362 [11] INFO ScheduleRequestManager – Create NameRepository
2013-11-10 17:24:12,362 [11] INFO ScheduleRequestManager – 2 entries in list
2013-11-10 17:24:12,362 [11] INFO ScheduleRequestManager – FullName:Anette.Andersson@exchange.testlabs.se
2013-11-10 17:24:12,362 [11] INFO ScheduleRequestManager – FullName:Klas.Andersson@exchange.testlabs.se
2013-11-10 17:24:12,362 [11] INFO ScheduleRequestManager – ScheduleRequestManager() exit
2013-11-10 17:24:12,362 [11] INFO ScheduleRequestManager – Call ExchangeFreeBusyService net.tcp to get Free/Busy information
2013-11-10 17:24:13,377 [11] INFO ScheduleRequestManager – GetFreeBusyForUsers() exit
2013-11-10 17:24:13,377 [11] INFO ScheduleRequestManager – GetFreeBusyForUsers returned 2 results
2013-11-10 17:24:13,377 [11] INFO ScheduleRequestManager – Create SCHED_LIST result instance for user anette.andersson@exchange.testlabs.se
2013-11-10 17:24:13,377 [11] INFO ScheduleRequestManager – Is a valid user.
2013-11-10 17:24:13,377 [11] INFO ScheduleRequestManager – Allocate 8 bytes to hold SCHED_LIST
2013-11-10 17:24:13,377 [11] INFO ScheduleRequestManager – Convert 0 Free/Busy times to TIMEDATE format
2013-11-10 17:24:13,377 [11] INFO ScheduleRequestManager – Schedule_NewFromSchedList()
2013-11-10 17:24:13,377 [11] INFO ScheduleRequestManager – Create SCHED_LIST result instance for user klas.andersson@exchange.testlabs.se
2013-11-10 17:24:13,377 [11] INFO ScheduleRequestManager – Is a valid user.
2013-11-10 17:24:13,377 [11] INFO ScheduleRequestManager – Allocate 2600 bytes to hold SCHED_LIST
2013-11-10 17:24:13,377 [11] INFO ScheduleRequestManager – Convert 72 Free/Busy times to TIMEDATE format
2013-11-10 17:24:13,377 [11] INFO ScheduleRequestManager – Schedule_NewFromSchedList()
2013-11-10 17:24:13,377 [11] INFO ScheduleRequestManager – Set SCHMSG flags to SCHMSG_ReplyToRqst
2013-11-10 17:24:13,377 [11] INFO ScheduleRequestManager – MQPut: Place SCHMSG in output queue
2013-11-10 17:24:13,377 [11] INFO ScheduleRequestManager – SchContainer_FreeRequest: Free hContainerObject
2013-11-10 17:24:13,377 [11] INFO ScheduleRequestManager – SchContainer_Free: Free hContainer
2013-11-10 17:24:13,377 [11] INFO ScheduleRequestManager – Delete SCHMSG message
2013-11-10 17:24:13,377 [11] INFO ScheduleRequestManager – NotesTermThread
2013-11-10 17:24:13,377 [11] INFO ScheduleRequestManager – Free/Busy request processing took 00:00:01.0212926
2013-11-10 17:24:13,377 [11] INFO ScheduleRequestManager – ScheduleRequestHandler() exit

 

ExchangeFreeBusyService.wlog:

2013-11-10 17:24:12,376 [15] INFO ExchangeFreeBusyConnector – Initialize() Enter
2013-11-10 17:24:12,377 [15] INFO ExchangeConfiguration – User name credential is sa-cmnfb@testlabs.se
2013-11-10 17:24:12,378 [15] INFO ExchangeFreeBusyConnector – Initialize() Exit
2013-11-10 17:24:12,378 [15] INFO FreeBusyWcfServiceBase – GetFreeBusyForUsers() Begin
2013-11-10 17:24:12,378 [15] INFO FreeBusyWcfServiceBase – Time span: 11/07/2013 17:15:00 Local — 04/24/2014 17:15:00 Local
2013-11-10 17:24:12,378 [15] INFO FreeBusyWcfServiceBase – Email addresses:
2013-11-10 17:24:12,378 [15] INFO FreeBusyWcfServiceBase - Anette.Andersson@exchange.testlabs.se
2013-11-10 17:24:12,378 [15] INFO FreeBusyWcfServiceBase - Klas.Andersson@exchange.testlabs.se
2013-11-10 17:24:12,379 [15] INFO ExchangeFreeBusyConnector – GetFreeBusyInfo() Begin
2013-11-10 17:24:12,379 [15] INFO ExchangeFreeBusyConnector - Email Addressees (Count=2), Start=11/07/2013 00:00:00 (Utc), End=04/24/2014 00:00:00 (Utc)
2013-11-10 17:24:12,379 [15] INFO ExchangeFreeBusyConnector - anette.andersson@exchange.testlabs.se
2013-11-10 17:24:12,379 [15] INFO ExchangeFreeBusyConnector - klas.andersson@exchange.testlabs.se
2013-11-10 17:24:12,379 [15] INFO ExchangeConfiguration – User name credential is sa-cmnfb@testlabs.se
2013-11-10 17:24:12,379 [15] INFO EwsWorker – Sending EWS request to Exchange
2013-11-10 17:24:13,117 [15] INFO EwsWorker – Receiving EWS response from Exchange 00:00:00.7369215
2013-11-10 17:24:13,117 [15] INFO EwsWorker – Sending EWS request to Exchange
2013-11-10 17:24:13,184 [15] INFO EwsWorker – Receiving EWS response from Exchange 00:00:00.0662414
2013-11-10 17:24:13,184 [15] INFO EwsWorker – Sending EWS request to Exchange
2013-11-10 17:24:13,247 [15] INFO EwsWorker – Receiving EWS response from Exchange 00:00:00.0627933
2013-11-10 17:24:13,247 [15] INFO EwsWorker – Sending EWS request to Exchange
2013-11-10 17:24:13,313 [15] INFO EwsWorker – Receiving EWS response from Exchange 00:00:00.0654069
2013-11-10 17:24:13,313 [15] INFO ExchangeFreeBusyConnector – GetFreeBusyInfo() End 00:00:00.9331625
2013-11-10 17:24:13,313 [15] INFO FreeBusyWcfServiceBase - Email Address: anette.andersson@exchange.testlabs.se
2013-11-10 17:24:13,313 [15] INFO FreeBusyWcfServiceBase - Valid User=True, Busy Time count=0
2013-11-10 17:24:13,313 [15] INFO FreeBusyWcfServiceBase - Email Address: klas.andersson@exchange.testlabs.se
2013-11-10 17:24:13,313 [15] INFO FreeBusyWcfServiceBase - Valid User=True, Busy Time count=72
2013-11-10 17:24:13,313 [15] INFO FreeBusyWcfServiceBase – GetFreeBusyForUsers() End Elapsed Time 00:00:00.9340514

 

Outlook 2013 (destination/target)

 

Mail flow

A mail is sent from the Outlook 2013 client to a user that has not been migrated and remains in Domino.

The mail is a standard mail, see picture below.

 

During the transport, these actions are being logged into the CMN.log file on the CMN server, some related entities can be found below:

2013-11-10 17:37:40,731 INFO CMN.logging [5] – Connection received from 172.16.1.12.
2013-11-10 17:37:40,734 INFO CMN.logging [5] – Message Number [4] on Thread [5] from Exchange (172.16.1.12:32641) to Domino (172.16.1.16:25): Connection established.
2013-11-10 17:37:40,798 INFO CMN.logging [Proxy 4] – Message Number [4] on Thread [12] from Exchange (172.16.1.12:32641) to Domino (172.16.1.16:25): Processed Message ID: 845c8150e7184c1794427a406e6e90e5@TLEX01.testlabs.se – Size: 3332 – From: klas.andersson@testlabs.se – To: Jonas.Andersson@target.local – Processing Time: .002 Seconds – Changes: NoChange

 

In the destination mailbox (Lotus Notes) it should look like the picture below

 

And the reply from Notes ends up in the target mailbox (Outlook), just like the picture shows below

 

Calendar Free/Busy

A Free/Busy request was done by arranging a new meeting in the Outlook 2013 client and selecting the Domino users. If the Free/Busy request lookup is working as expected, it should look similar to the picture below:

 

During the busytime lookup requests, these actions are being logged into the QCalCon.wlog and ExchangeFreeBusyService.wlog file on the CMN server. Some examples on log entries can be found while doing the busytime lookup, see below:

 

Autodiscover.wlog

2013-11-10 17:45:29,687 [6] INFO AutodiscoverPage – IsSecureConnection: True
2013-11-10 17:45:29,688 [6] INFO AutodiscoverPage – UserAgent: ASAutoDiscover/CrossForest/EmailDomain//15.00.0712.014
2013-11-10 17:45:29,790 [6] INFO AutodiscoverPage – UserHostName: 172.16.1.12
2013-11-10 17:45:29,790 [6] INFO AutodiscoverPage – UserHostAddress: 172.16.1.12
2013-11-10 17:45:29,883 [6] INFO AutodiscoverPage – Email Address: Jonas.Andersson@target.local
2013-11-10 17:45:29,883 [6] INFO AutodiscoverPage – Quest EWS URL: https://autodiscover.target.local/EWS/Service.asmx

 

EWS.wlog:

2013-11-10 17:45:31,178 [1] INFO Global – Application_Start
2013-11-10 17:45:31,190 [1] INFO Global – Assembly Title: CMX.Apps.FreeBusy.ExchangeWebService
2013-11-10 17:45:31,191 [1] INFO Global – File Version: 3.5.1.51
2013-11-10 17:45:34,771 [6] INFO QuestEWSService – RequestedView: Detailed
2013-11-10 17:45:34,772 [6] INFO QuestEWSService – RequestedViewSpecified: True
2013-11-10 17:45:34,772 [6] INFO QuestEWSService – MergedFreeBusyIntervalInMinutes: 30
2013-11-10 17:45:34,773 [6] INFO QuestEWSService – TimeWindow: 11/03/2013 08:00:00 Unspecified — 12/03/2013 08:00:00 Unspecified
2013-11-10 17:45:34,775 [6] INFO QuestEWSService – TimeZone bias: -60
2013-11-10 17:45:34,776 [6] INFO QuestEWSService - StandardTime: -10-Sunday 5 0
2013-11-10 17:45:34,776 [6] INFO QuestEWSService - DaylightTime: -3-Sunday 5 -60
2013-11-10 17:45:34,776 [6] INFO QuestEWSService - Jonas.Andersson@target.local
2013-11-10 17:45:36,774 [6] INFO QuestEWSService – Response:
2013-11-10 17:45:36,774 [6] INFO QuestEWSService - Email Address: jonas.andersson@target.local, FreeBusy Count: 61
2013-11-10 17:45:36,778 [6] INFO QuestEWSService – 00:00:02.0071483

 

DominoFreeBusyService.wlog:

2013-11-10 17:45:35,142 [3] INFO FreeBusyWcfServiceBase – GetFreeBusyForUsers() Begin
2013-11-10 17:45:35,143 [3] INFO FreeBusyWcfServiceBase – Time span: 11/03/2013 07:00:00 Utc — 12/03/2013 07:00:00 Utc
2013-11-10 17:45:35,149 [3] INFO FreeBusyWcfServiceBase – Email addresses:
2013-11-10 17:45:35,149 [3] INFO FreeBusyWcfServiceBase - Jonas.Andersson@target.local
2013-11-10 17:45:35,235 [3] INFO SmtpDomainMappings – smtpMappings count:0
2013-11-10 17:45:35,242 [3] INFO DominoFreeBusyConnector – GetFreeBusyInfo() enter
2013-11-10 17:45:35,243 [3] INFO DominoFreeBusyConnector – Get Domino user map.
2013-11-10 17:45:35,328 [3] INFO DominoSingleton – Ctor() enter
2013-11-10 17:45:35,328 [3] INFO DominoSingleton – Create DominoLibrary
2013-11-10 17:45:35,330 [3] INFO DominoSingleton – Initialize DominoLibrary
2013-11-10 17:45:35,411 [3] INFO DominoSingleton – Create UserMapRepository
2013-11-10 17:45:35,412 [3] INFO DominoUserMapRepository – ctor() enter; serverName = domino/target
2013-11-10 17:45:35,412 [3] INFO DominoUserMapRepository – ctor() exit
2013-11-10 17:45:35,412 [3] INFO DominoSingleton – Ctor() exit
2013-11-10 17:45:35,416 [3] INFO DominoUserMapRepository – GetDominoUserMap() enter; smtpDomain = target.local
2013-11-10 17:45:35,416 [3] INFO DominoUserMapRepository – jonas.andersson@target.local not found in cache.
2013-11-10 17:45:35,416 [3] INFO DominoUserMapRepository – 1 cache miss.
2013-11-10 17:45:35,425 [3] INFO NameRepository – GetTargetDominoUsers count:1
2013-11-10 17:45:35,426 [3] INFO NameRepository – Querying Domino Server Name=domino/target Domain=target.local
2013-11-10 17:45:36,718 [3] INFO NameRepository – Completed Domino Query
2013-11-10 17:45:36,718 [3] INFO NameRepository – No error in Domino query
2013-11-10 17:45:36,719 [3] INFO NameRepository – Address To Locate: jonas.andersson@target.local
2013-11-10 17:45:36,720 [3] INFO NameRepository – Domino Type: Person
2013-11-10 17:45:36,721 [3] INFO NameRepository – Domino Internet Address: Jonas.Andersson@target.local
2013-11-10 17:45:36,721 [3] INFO NameRepository – Domino Full Name: CN=Jonas Andersson/O=target
2013-11-10 17:45:36,721 [3] INFO NameRepository – Domino Mail File: mail\janderss.nsf
2013-11-10 17:45:36,721 [3] INFO NameRepository – Domino Mail Domain: target
2013-11-10 17:45:36,721 [3] INFO NameRepository – Domino List Name:
2013-11-10 17:45:36,721 [3] INFO NameRepository – Domino Mail Server: CN=domino/O=target
2013-11-10 17:45:36,721 [3] INFO NameRepository – Adding Jonas.Andersson@target.local to result set.
2013-11-10 17:45:36,721 [3] INFO NameRepository – finally – NameRepository :: GetTargetDominoUsers
2013-11-10 17:45:36,722 [3] INFO DominoUserMapRepository – 1 addresses found.
2013-11-10 17:45:36,722 [3] INFO DominoUserMapRepository – Adding jonas.andersson@target.local to cache.
2013-11-10 17:45:36,722 [3] INFO DominoUserMapRepository – GetDominoUserMap() exit
2013-11-10 17:45:36,722 [3] INFO DominoFreeBusyConnector – 1 Domino domain users found.
2013-11-10 17:45:36,722 [3] INFO DominoFreeBusyConnector – Filter list to SMTP Domino domain users.
2013-11-10 17:45:36,722 [3] INFO DominoFreeBusyConnector – Get Free/Busy information for each valid user in SMTP Domino domain user list.
2013-11-10 17:45:36,722 [3] INFO DominoFreeBusyConnector – Get live Free/Busy for Jonas.Andersson@target.local
2013-11-10 17:45:36,730 [3] INFO DominoLibrary – Sending request to Domino for free busy information.
2013-11-10 17:45:36,737 [3] INFO DominoLibrary – Domino response processing complete.
2013-11-10 17:45:36,749 [3] INFO DominoFreeBusyConnector – Add to result list
2013-11-10 17:45:36,749 [3] INFO DominoFreeBusyConnector – Sort the result list.
2013-11-10 17:45:36,752 [3] INFO DominoFreeBusyConnector – 1 Free/Busy results found
2013-11-10 17:45:36,752 [3] INFO DominoFreeBusyConnector – GetFreeBusyInfo() exit
2013-11-10 17:45:36,754 [3] INFO FreeBusyWcfServiceBase - Email Address: jonas.andersson@target.local
2013-11-10 17:45:36,754 [3] INFO FreeBusyWcfServiceBase - Valid User=True, Busy Time count=61
2013-11-10 17:45:36,754 [3] INFO FreeBusyWcfServiceBase – GetFreeBusyForUsers() End Elapsed Time 00:00:01.6046657

 

 

Notes from the field

 

Log reader tool – A good log reader, my favorite is the old tool that was included in the SMS 2003 resource kit called trace32.exe. It can be downloaded here.

 

Domino SMTP routing – Until I have published a new article on this topic, see the existing one since it can be difficult to understand on how SMTP routing is working between the systems. See the post about it here: http://www.testlabs.se/blog/2011/01/03/coexistence-between-domino-and-exchange-2010-%e2%80%93-part-1-of-2/

 

Network Monitoring – Network Monitoring or Wireshark may sometimes be your best friend during troubleshooting network connectivity. Portqry is another tool that could be of great value during initial network verification.

 

Don’t hesitate to comment if you would like to add anything or if you have other experiences, I will add it into the post and link your blog.

Next post will be on the same topic, but using Office 365 instead of On-premise.