Notes and Exchange Coexistence: Architecture Overview,

[patris1]

http://www.messagingtalk.org/notes-and-exchange-coexistence-architecture-overview-part-1

PART-1

Introduction

The document will detail steps to coexist Lotus Notes and Microsoft Exchange 2007. We will focus on coexistence in this article and will separately discuss about migration in a different article. Some companies have requirements for a coexistence solution which will need to last for a couple of months to a year ore even more. Although it is not recommended to have such a long coexistence period this requirement typically exists because of the long durations it can take to develop, deploy and migrate existing Notes applications to a separate environment (typically Microsoft Sharepoint).
Microsoft has a tool called Microsoft Transporter Suite to perform coexistence between Notes and Exchange. This tool can perform Directory Syncronization, Free Busy Lookup and basic migration tasks. However, it is not a full solution if an organization wants to have a complete coexistence solution and above all for a longer period. Notes and Exchange have differences in certain areas on their working of a typical email system and this is not fully resolved by the Microsoft Transporter Suite.
To resolve this issue a few companies have partnered with Microsoft to come out with products on coexistence and migration between Notes and Exchange.Two of these companies who have managed to resolve most of the issues are Binary Tree and Quest. In this article i will be discussing about Binary Tree as a coexistence tool along with MS Transporter Suite and how we can configure settings in the Notes and Exchange servers to give users seamless experience during Coexistence.
Overview of Coexistence Setup

A brief description of our coexistence environment

Our Environment consists of the following servers :

• 2 Domino servers - One server is the Domino mail server DOM/Earth, and the other is Notes Coexistence server DOM1/Earth.
• 3 CAS/HUB MS Exchange 2007 servers - CAS01 and CAS02 are two CAS and HUB Servers. CAS03 is also a CAS/HUB server on which MS Transporter Suite will be installed.
• 2 Mailbox MS Exchange 2007 servers in Clustered Copy Replication pair.
• 2 Active Directory servers.

We are hosting two companies COMPA and COMPB in the Notes and Exchange Domains. In Exchange the two companies are configured with Multi-tenant architecture.
Network Port to be opened for coexistence
Port 1352 from Notes Coexistence server "DOM1" (in Exchange Segment) to Notes Mail server "DOM" (in Notes segment).
The DOM1/Earth domino coexistence server needs to be in the Exchange server segment. We are doing this because of couple of high ports necessary for Directory Syncronization and Free Busy lookup required by the MS Transporter Suite (on CAS03) and DOM1 (Notes Coexistence server).

Lotus Notes Configuration
The Notes environment consists of Notes mail, application and smtp servers. We will introduce another Notes server called the Notes Coexistence server to facilitate our coexistence with Microsoft Exchange 2007. Preferably the Notes coexistence server should be in the same Notes domain as the Notes Mail Server. This server will act as a gateway from Notes to Exchange for Mail Routing, Directory Syncronization and Free Busy lookup.
Setup Notes Coexistence server
The coexistence server should be installed as any Domino R6.5.6 server. I will not detail the steps to installs the domino server here. Preferably the Notes Coexistence server should be in the same network segment as the Exchange servers. In our environment we have setup DOM1/Earth server as our Notes coexistence server which acts as a gateway between Mail server DOM/Earth and the Exchange Environment.
Notes Address Book Configurations
On the Notes Address book (names.nsf ) we have to implement some minor changes for Coexistence Mail Routing. Please note we are using Binary Tree coexistence software as our coexistence product and configuration changes will be suited to the product along with Domino.
a). Create a Foreign Domain Document called "Exchange" in the Notes address book. Under "Mail Information" put "Gateway Server name" as DOM1/Earth and "Gateway Mailfile name" as "btexchange.box". (We will later create this database). Fill in the same information under "Calendar Information".

b). Create a Foreign SMTP Domain Document.
Under "Routing" tab in the "Message Addressed To Internet Domain Name" field, type in "target.local".
Should be routed to Domain name keyin "SMTPToExchange1".

c). You should already have your Domino Global Domain documents present in your Notes address book. In our environment we have compa.com and compb.com Global Domain documents. In your existing Global Domain Document make sure that the Internet Address Lookup field is "Enabled".

d). Connection Document- Create a connection document with connection type "SMTP". Source server is Notes coexistence server DOM1/Earth. Destination Server is MS Transporter server CAS03. Destination Domain is SMTPExchange1. This "SMTPExchange1" domain is a fictitious domain and is created to link the above Domain document "target.local" with this connection document.

In the second tab Replication/Routing select SMTP Routing and change the value of Route at once if to 1 message.

Third tab Schedule set as shown below.

e). Open the configuration document of the Notes coexistence server DOM1/Earth.

i. Under Router/SMTP > Basics> Address Lookup set as "Full Name then Local Part"

ii.Under Router/SMTP > Basics> Exhaustive Lookup set as "Disabled".

iii. Under MIME > Conversion Options > General , under General Conversion Options set Return Receipt as Enabled.

iv. Under MIME > Conversion Options > Outbound , under Lookup Internet Address for all All Notes Address when Internet Address is not defined in document select "Enabled".

v. Under MIME > Conversion Options > Outbound , under Perform exhaustive lookups when converting Notes Addresses to Internet Addresses select "Enabled".

f). We have create a new id called Exchange Migrator for migration and will have to give "Reader" Access in the Address book ACL.

We will use this id Exchange Migrator/Earth to configure the Notes client on CAS03.

Summary

In this article "Notes and Exchange Coexistence Part 1" we have seen the architecture of the Coexistence setup and the ports necessary to be opened to create the setup. We have also detailed the Domino Server configurations that is necessary for the coexistence setup

---

موضوعات مشابه:

• A Few Notes Regarding Remote SQL Logging with Microsoft ISA Server 2006&Forefront Threat Management
• Implementing Exchange Server 2007 for coexistence with Exchange Server 2003
• TCP Overview

---

[patris1]

http://www.messagingtalk.org/notes-and-exchange-coexistence-binarytree-configurations-part-2

PART-2

In this part we will discuss how to install and configure the calendar component of the MS Transporter Suite on the Domino environment. In the next article we will have a detailed discussion how MS Transporter Suite will be used for Directory Syncronization and Free Busy schedule lookup from the Exchange environment.
We will continue our discussion in this article with the BinaryTree coexistence software and Domino Configurations on the Coexistence server necessary.
MS Transporter Suite Calendar component Installation
The most recent version of the MS Transporter Suite can be downloaded from Download details: Microsoft Transporter Suite, in both 64-bit and 32-bit versions:

• The 64-bit version of the Transporter Suite is used on production Exchange Server 2007 servers and 64-bit migration workstations
• The 32-bit version of the Transporter Suite is used on 32-bit migration workstations, and test Exchange Server 2007 servers on a 32-bit operating system.

Note: The 32-bit Exchange Server 2007 servers are not supported for production use.
Steps to install MS Transporter Calendar Component on Domino Server
1. On the Notes Coexistence server DOM1/Earth stop the Domino Server.
2. Install the MS Transporter Suite.
i. On the Welcome page, click Next.
ii. Accept the terms of the license agreement, and then click Next.
iii. Select Free Busy Connector Add-In Task For Lotus Domino. The installation location is determined based on information the Domino servers places in the Registry upon installation.

4. Click Install, and then click Finish.

This will complete the installation of the Calendar component on the Notes Coexistence server DOM1/Earth.

The next step is to install the coexistence software from Binarytree this server.

Binary Tree Installation and Configuration

Binary Tree has several products for migration , we will be using their product Coexistence for Exchange for this deployment. You can download a trail version of the product in the below link

Home - Products: Enable high-fidelity email and calendar coexistence between Lotus Notes and Microsoft Exchange with CMT for Coexistence

The download will contain the following files.

btcache.ntf, btstats.ntf, btstore_212.ntf, nBTCal.exe, nbtcal.sym, nBTCalF.exe, nbtcalf.sym, nBTCalL.exe, nbtcalL.sym, nBTEX.dll, and nbtex.sym.

Copy all the *.exe and *.sym files into the Program Directory of Domino server DOM1/Earth.

Copy all the ntf files in the Domino Server Data directory of DOM1/Earth. Sign these templates with your Notes security officer id and make it and your admin id the Manager access to these ntf files.

Creating Binary Tree databases

a. Create a database named btexchange.box in the Domino server data directory. Use a Notes client to create this database with the mailbox.ntf template. This database is created in the Notes Coexistence server DOM1/Earth.

b. Create a database in the Domino data directory of DOM1/Earth named btstore.nsf using the template btstore_212.ntf.

c. Create a database in the Domino data directory of DOM1/Earth named btcache.nsf using the template btcache.ntf.

Creating Log Folders

Create two folders for BT logs. We have created two folders in the below locations.

i. C:\Lotus\Domino\Data\BTLOg
ii. C:\Lotus\Domino\Data\BTWork

Notes.ini Modifications

Open the Notes.ini file from the Domino program directory of DOM1/Earth and edit it with the following parameters.

a. On the Server Tasks line add in the "btcal" task

ServerTasks=Update,Replica,Router,AMgr,AdminP,CalC onn,Sched, btcal

b. On the Server Tasks line add in the "excalcon" task as shown below along with the "cas03 btexchange.box" parameters. The excalcon task has already been installed by the MS Transporter component. The parameter basically tells Domino to connect to the exchange CAS/HUB server CAS03 (where the exchange component of the MS Transporter Suite will be installed) to fetch freebusy information.

ServerTasks=Update,Replica,Router,AMgr,AdminP,CalC onn,Sched, btcal,excalcon cas03 btexchange.box

c. At the end of the Notes.ini file copy and paste the below lines. These are Binary Tree software parameters and need to be modified according to your environment.

;**************Start BT Parameters***********
EXTMGR_ADDINS=BTEX
BTEXCHANGEDOMAIN=Exchange
BTALTEXCHANGEDOMAINS=compa.com,compb.com
BTEXCHANGEDB=btexchange.box
BTEXCHANGEROUTER=exchange.box
BTRECIPCONVERTFIELD=shortname
BTEXCHANGESERVER=target.local
BTHOLDDOMAIN=exchghold.target.local
BTPROCESSDOMAIN1=compa.com,compb.com
BTPROCESSDOMAIN2=target.local
BTNOTESDOMAINS=_
BTLINKSOPTION=0
BTCACHEDB=btcache.nsf
BTAPPTREROUTE=1
BTDEBUGIDLEDELAY=25
BTDELAY=30
BTORPHANDELAY=120
BTRETRYLIMIT=5
BTCALRESTARTTIMER=360
BTBCCSKIPADDRESS=user@host
BTSUPPORTMULTIPLEDOMINODOMAINS=1
MIMEFORCEATTACHMENT=1
BTINATTOPT=0
BTINATTSKIPNAMES=image###
BTINATTSKIPNAMESOLD=image###
BTREMOVEATTACH=xxx
BTMULTISCHEDREPORTLEVEL=4
BTMULTISCHEDREPORTADDRESS=achinta@tspl.com.sg
#BTMULTISCHEDREPORTTEXT=***Attention!!! *** Repeat/Recurrence Pattern used in scheduling the original meeting cannot be used at this time. Please cancel the original meeting and schedule a new one using a supported pattern.
#BTMULTISCHEDREPORTTEXT1=Dear User\n\n\nYou cannot send these types of messages\n\n
#BTMULTISCHEDREPORTTEXT2=So don't do it\nEnd of Story
BTZAPPSUPPORT=1
BTSTOREDB=btstore.nsf
BTZAPPUNIQUECOPY=N
BTZAPPCHECKENCRYPT=1
BTZAPPBYPASS=1
BTZAPPBYPASSDOCSWITHFIELDS=In_Reply_To
BTEXPANDGROUPS=Y
BTSENDEXPANDED=Y
BTWORKDIRECTORY=C:\Lotus\Domino\Data\BTWork
BTLOGDIRECTORY=C:\Lotus\Domino\Data\BTLOg
BTLOGCACHE=1
BTLOGICAL=1
BTLOGRMB=1
BTLOGUIF=1
BTLOGWMBP=1
;BTZAPPIGNORESTOREDFORMS=0
;BTZAPPPROCESSFORMS=<value1>,<value2>,none,<value3 >
;BTZAPPIGNOREFORMS=<value1>,<value2>,none,<value3> or allnonstandard
;BTZAPPIGNOREFORMS=allnonstandard,NonDelivery Report,Memo
BTZAPPIGNOREFORMS=Memo,SMSFrm,allnonstandard
BTZAPPORGS=Earth
BTZAPPREADERS=ZAppReaders
BTZAPPSENDORIGINAL=0
BTSTORETEXT1=e-Mail sent to you from Lotus Notes contains specific elements requiring Lotus Notes Client\n\nPlease press link below to access it\n\n
**********End Parameters*********************

Following are the paramaters that you might need to modify suited to your environment.

i. Parameter BTALTEXCHANGEDOMAINS, BTPROCESSDOMAIN1 will depend on the MX domains that you host.

ii. Parameter BTMULTISCHEDREPORTADDRESS will be an email address where you want to send the error messages.

iii. Parameter BTWORKDIRECTORY and BTLOGDIRECTORY can be different for your environment.

iv. Parameter BTZAPPORGS will be your Notes Organizaton.

Once we have completed the settings restart the Domino server DOM1/Earth.

Once the server is restarted you might get the following warning message on the Domino console as the Excalcon task will not be able to connect to the MS Transporter Calendar component on the CAS03 server. At this stage this error message is ok and can be ignored.

Summary

In this part "Notes and Exchange Coexistence Part 2" we have discussed about MS Transporter component on Domino and detailed more on how to configure Binary Tree coexistence software for your Coexistence environment. This will complete the Domino Configurations part and we will move on to Exchange configurations in the next article

[patris1]

http://www.messagingtalk.org/notes-and-exchange-coexistence-ms-transporter-configurations-par

PART-3

In this article we will will start our Coexistence configuration on the Exchange environment. We will discuss more on the MS Transporter suite and its configurations necessary for the coexistence setup.

MS Transporter Suite Installation and Configuration
We will already detailed in the previous article on where to download the MS Transporter Suite, below is the link again.
Download details: Microsoft Transporter Suite
The Transporter Suite should be installed on a Exchange 2007 server with a CAS/HUB Role installed. In our case we will install it on CAS03.
Step 1:
Installation is relatively straight-forward:
1. On the Welcome page, click Next.
2. Accept the terms of the license agreement, and then click Next.
3. Note: that Microsoft Transporter Tools is selected, choose an alternate installation location if you want, and then click Next.
4. Click Install, and then click Finish.
1. Open the Transporter Management Console. In the left pane, click Connect, and then, in the right pane, click Create Directory Connector.

Step 2:
A Notes client (preferably 7.0.2 or later) is be installed on CAS/HUB server CAS03. Once the Notes client is installed you need to configure it with a Notes id file which has "Reader" access to the Notes Public Address book (names.nsf). We have created a separate id called Exchange Migrator for this task and have given "Reader" Access in the Notes ACL.

Step 3:
Directory Syncronization Configuration
Before we begin the configuration we want to decide whether we need a two way syncronization between Domino and Exchange. In our case we will only perform a one way syncronization from Domino to Exchange. This is because we will configure the address in Domino in such a way that migrating users to Exchange will still have a contact in Domino without the need of a syncronization back from Exchange to create it as a contact.
To begin, a new connector must be created.
1. Open the Transporter Management Console. In the left pane, click Connect, and then, in the right pane, click Create Directory Connector.

2. Click Next, click Create, and then click Finish.

To configure the new directory connector
To configure the connector, double-click the newly created object, and you are presented with tabbed property pages to fill in, the first being the General tab.
1. On the General tab for Schedule select "Every 15 minutes".
2. Under Directory Servers > Global Catalog. Choose a global catalog in the same site as the Exchange Server 2007 server. In our environment we choose adpoc.pocdom.local.
3. Next, type the Domino Server name from where the Domino Directory will be syncronized from i.e, DOM1/Earth.

4. Then, enter and confirm the Notes password for the id file which will perform the Syncronization using the Notes client installed, which is Exchange Migrator.
5. On Sync to Active Directory tab under "Source Domino Directory" click on Add and key in the required information for Domino.

6. Under Target Active Directory select the OU under which you want to syncronize your Domino user contacts. In our environment we have pre-created an OU in the active directory called "Domino Users" under "Hosting" as shown below.
Note: The OU "Domino Users" must have "Full Control" permissions for the server CAS03 which replicates the Domino directory to Exchange i.e, where the MS Transporter is installed.

7. The following will be the final configuration screen for the Sync to Active Directory tab.

8. In the Sync to Domino tab as we will only do a one-way syncronization from Domino to Exchange the "Routable Exchange Domains" field needs to be filled.
We will specify an entry there as "target.local". This is a domain name that will be used by Domino to route emails to Exchange from the Notes Coexistence server.

9. On the Advanced tab uncheck the two fields "Sync Contacts to Domino Directory" and "Sync Groups to Domino Directory".

Step 4 :
Calendar Syncronization Configuration
"Microsoft Exchange Server MAPI Client and Collaboration Data Objects 1.2.1" must be installed on the CAS03 server which hosts the MS Transporter Suite. The "Microsoft Exchange Server MAPI Client and Collaboration Data Objects 1.2.1" package is available on the Microsoft Download Center (Download details: Microsoft Exchange Server MAPI Client and Collaboration Data Objects 1.2.1).
Before we configure the calendar we need to configure some settings in Exchange.
a) Public Folders : A Public Folder server must be available in the Exchange Server 2007 Administrative Group. When first installing Exchange Server 2007, you are asked to choose whether "compatibility with earlier versions of Outlook" is required. Selecting the appropriate check box causes a Public Folder store to be created. We assume you have already a Public Folder store in Exchange.
A specific folder must exist to store items representing the Free/Busy information for Domino users. Verify the existence of this folder using the following command in the Exchange Management Shell:
Get-PublicFolder -Identity "\NON_IPM_SUBTREE\SCHEDULE+ FREE BUSY" Recurse
Output should be similar to:

b) Availability :
Availability settings must be changed to cause the Availability service to use the Public Folder when gathering Free/Busy information for Domino users. This change must be performed using the Exchange Management Shell. Depending on the namespace design you chose, there may be multiple address spaces (SMTP domains) that need to be configured, including the address space used by Exchange Server.
The command required is of the form:
Add-AvailabilityAddressSpace -ForestName dominodomain.com AccessMethod PublicFolder
Output is as shown the a similar format to as below:

In our lab the command required will be the three mentioned below , two SMTP domains compa.com and compb.com and the active directory domain pocdom.local. As the availability service is a part of the active directory domain pocdom.local has to be included.
Add-AvailabilityAddressSpace -ForestName compa.com AccessMethod PublicFolder
Add-AvailabilityAddressSpace -ForestName compb.com AccessMethod PublicFolder
Add-AvailabilityAddressSpace -ForestName pocdom.local AccessMethod PublicFolder
c) Client Access Server Settings

The Transporter Suite for Lotus Domino communicates with the Exchange Server that performs the Client Access server role. If the Exchange Server that hosts the Client Access server role also hosts the Mailbox server role, the Free Busy Connector for Lotus Domino will not work until secure sockets layer (SSL) is disabled on the /Public virtual directory of the server hosting both roles.

Summary
In this article "Notes and Exchange Coexistence Part 3" we have partly configured the MS Transporter Suite on CAS03 (a CAS/HUB server). We will continue the full configuration of the MS Transporter Suite on the next article

[patris1]

http://www.messagingtalk.org/notes-and-exchange-coexistence-part-mailrouting-configurations-p

PART-4

In the previous article we have partly discussed on the MS Transporter Suite configuration. We will complete the configuration in this article.
MS Transporter Installation and Configuration
Free/Busy Connector
Now we need to create the Free/Busy Connector for Exchange. This will enable the Excalcon task in the Notes Coexistence Server DOM1/Earth to gather Free Busy information to and from Exchange user to Domino.
To create the Free/Busy Connector
1. Open the Transporter Management Console. In the left pane, click Connect, and then in the right pane, click Create Free/Busy Connector.

2. Then, click Next, click Create, and then click Finish.

3. Once the Calendar connector is created right click on it and go to Free Busy Connector properties. Fill in the below values as shown below in the fields under "Exchange Free Busy Configuration". We will put "0" for both Maintain cache information and Timeout, this ensures that that when users lookup free busy information from Outlook for a Domino users the server always connects to Domino and gets the latest information.

On the Domino Free Busy Configuration section we will put the Notes Coexistence server name DOM1/Earth.
Put the password as the Exchange Migrator/Earth password which has been used to configure the Notes client on the machine. One more thing you might want to check on the Notes client that on the Location document make sure the Domino Directory server is DOM1/Earth.
4. Now click on the "Advanced" tab. On the "Connected Domino SMTP Domains" key in the SMTP domains that are routing through Domino and Exchange.

Directory Synchronization and Calendar Syncronization Services
Once the two connectors have been created. we need to start up the windows services that have been created due to the connectors.
Go to Windows services where you can find two services created.
a. Microsoft Exchange Directory Connector Service for Lotus Domino
b. Microsoft Exchange Free Busy Connector for Lotus Domino

Now make these two services as Automatic and restart the server.
Note: A point to note the Calendar service has to start before the Directory Sync service. Its quite possible that it starts the other way when the server restarts. So once you restart the CAS HUB Transporter server follow the below sequence.
i. Stop the "Microsoft Exchange Directory Connector Service for Lotus Domino" service.
ii. Restart the "Microsoft Exchange Free Busy Connector for Lotus Domino" service.
iii. Start the "Microsoft Exchange Directory Connector Service for Lotus Domino" service.
Now as mentioned in Part 2 of this series the Excalcon task in Notes Coexistence server was not able to connect to the Exchange server giving a warning message. As we have already installed the Free Busy Connector services in Exchange we can go back to the Notes Coexistence server.
At the DOM1/Earth console issue the following command:
load excalcon cas03 btexchange.box
Once you issue the command the Calendar component will be connected to the CAS03Free Busy connector component. The below screen will be displayed.

Mail Routing Configurations f or Coexistence setup
When Directory syncronization occurs between Notes and Exchange its only one way , ie from Notes to Exchange. Users in Domino appear as Contacts in Exchange.
A migrated Lotus Notes User to Exchange will have the following person document setting in Domino Address book as shown below.
Mail System: Other
Domain: Exchange

This user's Exchange account will be created as below with the following email addresses

How Notes users communicate with Exchange users?
When a Notes user sends an email to Exchange user like Test User1 as above, the Domino server locates the "Exchange" Domain and routes the email to the Exchange server through the Notes Coexistence server (in our case DOM1/Earth). The Coexistence server DOM1/Earth sends the email to tuser1@target.local on Exchange and Test User1 receives the email.
The same routing takes place when a Notes users sends a Calendar lookup request or Calendar Invitation to the Exchange user.
How Exchange users communicate with Notes users?
Once Directory syncronization has taken place from Notes to Exchange , the Notes user accounts appear as Mail Contacts in the Exchange. When an Exchange user sends an email or calendar invitation to Notes user they use the Mail contact in Exchange for such purposes.
Summary: Once we have finalized these settings we are actually completed with the MS Transporter Settings. To sum it up after the above configurations are completed we are ready to test Directory Syncronization and Free Busy Lookup between Exchange and Domino. We will perform these testings on Part 6 of this series. So if you want to check that out you can skip the following part

[patris1]

http://www.messagingtalk.org/notes-and-exchange-coexistence-exchange-configurations-part-5

PART-5

In this article we will discuss on the Exchange configuration portion. This is the Coexistence configuration part that details on Mail Routing between Exchange and Domino. Mail Routing between the two email systems uses basic SMTP. Our configurations will make sure that most of the content between the two systems remain intact.
MS Exchange configurations for Coexistence setup (Mail Routing)
The below settings that we will be performing in Exchange will be done through the Exchange Management Console.
Accepted Domains
Accepted domains are domains that make the Exchange server accept email from those domains when received from external systems. Hence they are needed for mail routing between Exchange and Domino.
We will be creating 4 accepted domains in the Exchange 2007 infrastructure. All the domains must be created as "Authoritative".
i. SMTP domain compa.com
ii. SMTP domain compb.com
iii. Active directory domain pocdom.local
iv. Temporary coexistence domain target.local
The default domain is Active directory domain pocdom.local.

Send Connectors
Send connectors are settings we need to create in Exchange to route an email to the Notes environment. We will create a send connector and call it "Outbound to Domino". In the address space we will put in the two SMTP addresses compa.com and compb.com.

On the "Network" tab we will key in the IP address where the Outbound emails from Exchange will be routed to Domino Server. Here we have put in the IP Address of the Notes Coexistence server DOM1/Earth where Exchange will send outgoing emails to Domino. You can input other Domino server Ips if you wish to create a fault tolerant architecture should the Notes Coexistence server fail.

On the "Source Server" tab input all the HUB Servers in your environment.

Receive Connectors
Now we will create Exchange Receive Connectors. Receive connectors are necessary for Exchange to allow receiving email from specific servers.
In our case we will need to receive emails from Domino. On the Exchange Management Console browse to the Server Configuration > Hub Transport. Click on the CAS03 server.This is the server that will receive emails from Domino. Create a Receive connector called "TARGET" as shown below.

Edit the properties of TARGET.

Click on "Network" tab. Now by default the CAS03 primary will receive emails from Domino. Just specify the primary IP address of CAS03 server under "Use these local IP addresses to receive mail".
Also, specify the remote server IP that will send emails to Exchange i.e. Notes Coexistence server DOM1/Earth IP address under "Receive mail from remote servers that have these IP addresses".

Now on the Authentication "tab" uncheck all options and enable "Externally Secured".

Under Permission Groups select all options as shown below.

This is how you create receive connectors in Exchange for the Coexistence setup. If you want redundancy you can create more receive connectors on the other HUB/CAS servers.
Email Policy
We will create an Email Policy for creating secondary address with target.local. When a new exchange user is registered this email policy will make sure that a target.local address is created automatically. However we need to take note that this address should be in shortname@target.local format, where shortname is from the personal document in the Domino Address book of the migrating user. A Domino user can have an alternate name, this name refers to the shortname. This name should be unique in the Notes address book and hence in the Exchange environment. Binary tree uses this shortname@target.local address to route emails between Notes and Exchange.

Once the policy is created click Finish.
Disable Exchange Rich text
A final setting that we would like to put in place is disabling the Exchange Rich text format option.
Under Organiaztion Configuration > Hub Transport , Click on properties of Remote Domains. Under "Format of Original Message sent as an attachment to journal report". select "Never Use" for "Exchange Rich text format" as shown below.

Summary
In this article "Notes and Exchange Coexistence Part 5" we have detailed more on the Exchange configurations necessary on the Coexistence setup. With this article we have come to the end of the configuration portions of the Notes and Exchange Coexistence setup. Once you have done all the configurations you should proceed to do the basic testing necessary

[patris1]

http://www.messagingtalk.org/notes-and-exchange-coexistence-testing-part-6

PART-6

In this article we will detail the most important testing part of the Coexistence setup to support the configuration that we have implemented in the previous 5 part articles. Although i have tried to detail most of the testing scenarios , you might come up with more detailed set of testing in your lab environment.
Testing Coexistence between Notes and Exchange
Now that we have setup the coexistence environment between Notes and Exchange we will test the following.

• Directory Syncronization between Notes and Exchange
• FreeBusy Look up from Notes
• FreeBusy Look up from Exchange
• Calendar Invitations from Notes to Exchange
• Calendar Invitations from Exchange to Notes
• Mail Routing from Notes to Exchange
• Mail Routing from Exchange to Notes

For testing purposes in our environment we have created 3 test users in Notes and 2 test users migrated to Exchange.
Users in Notes : Testing Admin1, Testing Admin2
Users in Exchange : Test User1, Test User2
1. Directory Syncronization between Notes and Exchange
Although Directory Syncronization can take place automatically every 15 minutes , the first Directory syncronization should be done manually to test out its working.
On the MS Transporter Connect Console on the CAS03 server right click on the Domino Directory Connector and click on "Syncronize Now".

2. A new page will be displayed that indicates the task to be performed. Click Next.
3. On the following screen, there are several synchronization options. Choose Full Synchronization, make sure that the Full one way synchronization from Domino option is selected, and then click Next.
4. On the summary screen that follows, click Next. A completion screen will be displayed, and should indicate that the wizard completed successfully.
Screen Shots are shown below

Important Note: We will only perform a one way syncronization from Domino to Exchange and not the other way round.
Notes users will be in the form of Contacts in Exchange as shown below. As you can see the Notes user Testing Admin1 and Testing Admin2 are in the contacts view.

2. Free Busy Lookup from Notes
On the Domino environment take a user Testing Admin1 and login to the Notes client. The user will be connected to the user's mailfile on DOM server. We will do a lookup for user Test User1. Check how the address resolved to Test User1/-/Earth@Exchange. The free busy information is displayed below with the Notes Coexistence server pulling the information from Exchange as you can see below.

3. Calendar Invitations from Notes to Exchange
Proceeding after the free busy lookup send the invitation to the Exchange. Below will what you will receive in Exchange. Note you will receive an ICS file as an attachment.
Moreover you can send Repeating Notes Invitations from Notes to Exchange. However Notes Custom Repeating occurrences are not supported in Exchange.

4. Free Busy Lookup from Exchange.
From Outlook client login to the Exchange user Test User1. Perform a lookup from the Scheduling Assistant for the Free Busy information of the notes user Testing Admin1. The client should return the free busy information from Domino as shown below.

5. Calendar Invitations from Exchange to Notes
Proceeding after the free busy lookup send the invitation to Notes.

When the Notes user receives the invitation it will be in the form below.
Reoccurring Meetings are supported from Exchange to Notes.

6. Mail Routing from Notes to Exchange
When you send an email from Notes to Exchange the name should resolve to @Exchange. Lets test with the user Testing Admin1 sending an email to Test User1 from Domino to Exchange.

The user will receive an email in Exchange however as mentioned before the email routing takes place using the target.local address from the Notes Coexistence server.
7. Mail Routing from Exchange to Notes
In Outlook client type an email address of a Notes user Testing Admin1. When you check the Properties of the user as shown below see the Email Address. It shows the SMTP address of the user. This is the email address of the contact that was syncronized from Notes.

Now that we have tested the Coexistence configurations a few points would like to highlight on the Supported and Unsupported features on the coexistence setup between Notes and Exchange.

Supported Features

i. Doc Links and database links are supported from Notes to Exchange. However you need to the Notes client to open the link.

ii. Encrypted emails are supported from Notes to Exchange. Notes client is needed to open the link. These links are stored in DOM1/Earth Notes Coexistence server.

iii. Buttons are supported from Notes to Exchange. Notes client is needed to open the link. These links are stored in DOM1/Earth Notes Coexistence server.

Unsupported Features

i. Notes Sections are not supported in Exchange.

ii. Custom reoccurring meeting are not supported from Notes to Exchange.

Summary

This concludes the six part articles of Notes and Exchange Coexistence. Once you have setup the coexistence users will be able to use your email infrastructure as usual. However, its recommended you should plan to move your users from Notes to Exchange as soon as possible. A long coexistence phase is not recommended. To give your users the best Email experience all of them should be on a single email system.

For migrating users from Notes to Exchange using Binary Tree Migration tool i will be publishing a few articles in the near future