Migrator for Notes to Exchange 4.15.2 - Scenarios Guide

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

Whether implementing SMTP mail connectivity only or complete coexistence with Quest’s CMN, most migrating organizations use temporary SMTP domains to route traffic between Notes and Office 365. Other admins prefer to configure SMTP mail routing with smart host servers, for single-namespace environments. In either case, 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 will use subdomains for mail coexistence, configure the servers now as described below. If you will instead use smart hosts for mail routing, you can skip this step, since you will configure the smart hosts in step 15 below.

The routing domains may 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:

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

Refer to Quest’s CMN User Guide to install and configure the desired components: Directory Connector, Mail Connector, and/or Free/Busy Connector.

Remember to verify your CMN configuration by testing mail flow.

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’s Office 365).

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

Microsoft restricts access to its hosted AD, and these restrictions prevent CMN’s 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:

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 CMN’s Directory Connector is particularly well suited to that purpose.

Step 7: Discover Notes information

Migrator for Notes to Exchange needs to know the location of the Notes Address Books (NABs) that will serve as data sources for the Directory Export Wizard in the next step below. Migrator for Notes to Exchange also needs to know the Internet domains that will be used to generate users’ SMTP aliases. Migrator for Notes to Exchange therefore includes Wizards to search through your Notes environment and return the necessary information:

Run these two Wizards now, to prepare for the Directory Export Wizard in the next step below. See the NABS Discovery Wizard and Internet Domains Discovery Wizard chapters in the Migrator for Notes to Exchange Administration Guide for full information.

Step 8: Export Notes directory data

Migrator for Notes to Exchange’s Directory Export Wizard extracts user and group data from the Notes environment and populates Migrator for Notes to Exchange’s SQL database and other data files with this information. Other Quest applications require this data for input values. Run the Directory Export Wizard now to capture the necessary information. For more information and complete operating instructions for the Directory Export Wizard, see the Directory Export Wizard chapter in the Migrator for Notes to Exchange Administration Guide.