Comments on: Exchange 2007 and Domino Free/Busy Coexistence

By: Kushal

Kushal — Fri, 07 Aug 2009 23:29:43 +0000

We recently installed Microsoft transporter suite for co-existence between domino, exchange 2003 and exchange 2007 users. As per one of the consultant we installed the calcon on a server with 2 domino partitions. One of the calcon is for exchange 2003 version and renamed it to excalcon2k3, since they both need to be in the same domino program directory. Each of the domino servers are running calcon and connecting to two different exchange servers (one to 2003 and the other to 2007). But when a notes client submits free busy request for exchange 2003 users, the request is actually going to the domino server which is connected to exchange 2007 server and the request fails. We tried recreating the foreign domain documents , restarted all the services and it worked for a while and started failing again.

Has anyone tried running 2 calcon processes on a a partitioned domino server and if so, was there any work around.

By: Elan Shudnow

Elan Shudnow — Thu, 04 Jun 2009 15:02:32 +0000

OWA 2007 uses the Availability Service to pull Free/Busy information but through a different API than Outlook 2007 uses. Outlook 2007 uses Availability Service as well, but again, uses a different API than OWA uses. Outook 2003 doesn’t use the availability service but goes directly to public folders.

Seems a bit odd that OWA would work but not anything else. Can’t think of anything off the top of my head, but I’ll reply back if I do. If you figure it out, please comment with what you’ve discovered. Will be much appreciated.

By: Jose Osorio

Jose Osorio — Wed, 03 Jun 2009 19:13:24 +0000

Hi Elan,

Our Company is migratin from lotus Domino 8.0 to Exchange 2007.

Free/Busy works Fine, but i have this issue:

Domino users From Lotus Notes Client and Domino Web Access can view Free/Busy information of Exchange Users.

Exchange Users only from OWA can view Free/Busy information of Domino Users. Exchange Users from Outlook client 2003/2007 can´t view Free/Busy information from Domino Users.

Do you know why Outlook clients can´t do that?

Thanks.

Regards.

By: Elan Shudnow

Elan Shudnow — Tue, 12 May 2009 15:46:15 +0000

The problems were primarily related to the thing we had to do with adding the CAS fQDNs to Internet Sites. But either way, you are not supposed to host public folders on a CCR if you have “more than one” public folder database in your entire Exchange organization. You can check the CCR documentation on public folder support for more information.

By: Buster

Buster — Tue, 12 May 2009 08:47:22 +0000

Could you clarify what you meant with public folders on CCR-cluster and problems that you saw?

By: subject: exchange

subject: exchange — Fri, 27 Feb 2009 19:04:50 +0000

Weekend reading…

When to use Move Mailbox Wizard or ExMerge to move Exchange mailboxes Exchange 2007 SP1 Features with…

By: Perry Hiltz

Perry Hiltz — Wed, 25 Feb 2009 15:41:55 +0000

Elan, Great article.

Unfortunately when organizations are executing a significantly large migration from Domino to Exchange, there are a tremendous number of fidelity issues related to the implementation of iCal between Domino and Exchange utilizing only the transporter. As you are already aware messaging utilizing the transporter suite along and certain migration products do not provide full ability to reply to messages once migrated.

In addition these large organizations that require significant coexistence between the two platforms see significant issues with respect to the conversion of inline images, meeting invitations, and even embedded Domino objects such as embedded forms, buttons, and even encrypted mail.

Each of these can lead to a significant number of help desk calls, user problems and perceived failure. I’d love to discuss this with you sometime.

By: Trevor

Trevor — Tue, 24 Feb 2009 16:37:10 +0000

One issue we ran into during our migration (Notes 6.5 to Exchange 2007) is that the CalCon process on Domino wouldn’t return free/busy information for users who were recently migrated using Quest’s Notes Migrator for Exchange. After about of month of working with Microsoft PSS, we figured out a workaround…

Quest’s tool uses the “Other” setting for mail system when it sets forwarding for person documents. With this type of form, the CalCon process requires the full “Other address” (aka – forwarding email address) to be part of the “User name” field. In addition, we had to make the forwarding address + @domain (e.g.: John_Doe@exchange.domain.com@domain.com) the first name listed in the “User name” field before F/B requests were processed correctly.