Migrator for Notes to Exchange 4.16.1

Step 5 (if mail routing by domain differentiation): Configure mail routing domain for Exchange


	Conditional Step: This step applies only if you will configure email coexistence by temporary routing domains (domain differentiation in DNS) during the migration. If you will instead use smart hosts for mail routing (or will not configure mail routing at all), skip to step 6.

Whether your organization implements SMTP mail connectivity only or full coexistence with Quest Coexistence Manager for Notes (CMN), most migrating organizations use temporary SMTP domains to route traffic between Notes and Office 365. Other administrators configure SMTP mail routing with smart host servers for single-namespace environments. The routing method must be configured at both the server and user levels. At the user level, Notes person documents and AD object records are configured later in this procedure when provisioning the target AD and synchronizing the two directories.

If you are using subdomains for mail coexistence, configure the servers now as described the following procedure. If you are using smart hosts for mail routing, skip this step since you will configure the smart hosts in step 15.

To configure distinct domains for mail routing:

The routing domains can be subdomains of the primary domain (e.g., notes.domain.com and exchg.domain.com) or completely separate SMTP domains. As long as they are unique to the respective mail systems and resolvable (via DNS or host files), they will suffice for routing. To configure routing domains:

If appropriate SMTP domains are not already available, create them in DNS. One domain must direct traffic to Exchange (e.g., exchg.domain.com). Mail sent to the Notes mailboxes of migrated users will be forwarded to the corresponding mailboxes in Exchange using the exchg.domain.com domain. The other domain (e.g., notes.domain.com) is used for connectivity to Notes.

After configuring the new exchg.domain.com domain in DNS, configure Exchange to accept the SMTP domain, and create a recipient policy to generate appropriate secondary SMTP addresses, so all Exchange users will be able to receive mail at this domain.

Configure Notes to accept mail to the new notes.domain.com SMTP domain/address.

Verify the new domains by testing mail flow.

Step 6 (only for coexistence with Quest CMN):Install and configure CMN components

Step 6 (only for coexistence with Quest CMN):
Install and configure CMN components


	Conditional Step: This step applies only if you use the Quest Coexistence Manager for Notes (CMN) for directory, email, and/or free/busy coexistence during the migration. If you will migrate without CMN coexistence, skip to step 7.

Refer to the Quest Coexistence Manager for Notes User Guide to install and configure the desired components: Directory Connector, Mail Connector, and/or Free/Busy Connector.

Verify your CMN configuration by testing mail flow.

Free/busy coexistence with Office 365

Exchange cannot route a free/busy query to Domino for a user who already has an Exchange mailbox. Exchange can route such queries only to its own Exchange mailboxes. This Exchange free/busy limitation is explained in greater detail in chapter 1 of this Scenarios Guide (see the Provisioning and mailbox creation topic under Migration to Microsoft Office 365).

The chapter 1 reference describes a method of provisioning Office 365 that can preserve both Exchange-to-Notes free/busy queries and Exchange-to-Notes mail routing.

Directory coexistence with Office 365 and a local AD

Microsoft restricts access to its hosted AD, and these restrictions prevent the CMN Directory Connector from supporting directory coexistence directly between Domino and Office 365. But if you have a local AD, you can establish a “two-step” coexistence between Notes and Office 365, as follows:

Configure the CMN Directory Connector for bidirectional updates between Notes and a local, proprietary Active Directory.

Configure Microsoft AD Sync tool to synchronize the local AD with Office 365.

The combination of the two, run sequentially, would configure an effective directory coexistence between Domino and Office 365.

Most organizations will perform a directory synchronization as part of the process to provision a local proprietary AD (in a later step, if you intend to provision Office 365 from a local AD), and the CMN Directory Connector is well suited to that purpose.