Chat now with support
Chat with Support

We are currently experiencing issues on our phone support and are working diligently to restore services. For support, please sign in and create a case or email for assistance

Migrator for Notes to Exchange 4.16.3 - SSDM User Guide

About the Migrator for Notes to Exchange documentation Scenarios overview Migration to a proprietary Exchange
Migration to a proprietary Exchange target Pre-migration preparations Batch migration process Post-migration activities
Migration to Microsoft 365
Pre-migration preparations Batch migration process Post-migration activities
SSDM (per-desktop) migration

Step 15 (if using smart hosts for mail routing): Configure smart hosts

Conditional Step: Applies only if you intend to use smart hosts for SMTP mail routing.

Establish and configure the Domino and Exchange smart host servers and verify the configurations by testing mail flow. The creation of mail-enabled Active Directory accounts (in an earlier step) has entered the necessary targetAddress values into the AD object records.

The details of configuring smart-host SMTP mail routing are beyond the scope of this guide, but see your Domino and Exchange documentation and online resources for information about configuring smart hosts for those servers.

To configure smart-host SMTP routing with Quest CMN, both smart hosts are configured to point to the CMN server. In CMN, one set of SMTP IN and SMTP OUT queues is configured to accept mail from Domino and deliver it to the receiving Exchange server, while another set is configured to accept mail from Exchange and deliver it to Domino. Multiple CMN servers can be deployed for load balancing and redundancy. The Coexistence Manager for Notes User Guide (chapter 3) explains these configurations.

When pre-migration preparations are complete ...

When you have completed the pre-migration preparations, go on to the Batch migration process section and/or see chapter 4 for information about SSDM (per-desktop) migration.

Batch migration process

Migrator for Notes to Exchange includes two migration engines:

The Data Migration Wizard migrates batches of users simultaneously, and performs valuable administrative functions (e.g. mailbox creation, routing updates, etc.), provisions public distribution lists.
The Self-Service Desktop Migrator (SSDM) runs on end-user local workstations and migrates content for one user. SSDM streamlines the migration of local content, reduces burden on the migration team, and includes a Silent Mode to minimize end-user interaction and requirements.

Either migration engine can be used independently for the entire data migration, or the two may be used together to meet a variety of project requirements, as discussed in the Pre-Migration Planning Guide (see the Batch vs. Per-Desktop Migration topic in chapter 3).

This section provides process instructions for a typical migration to a proprietary Exchange, in which an administrator uses the Data Migration Wizard to perform the migrations for multiple batches (user collections) of users. SSDM (per-desktop) migration, described in chapter 4, may also be part of your Migration Plan.

IMPORTANT: Be sure you have completed the Pre-migration preparations described in this chapter before you begin this batch-migration process.

This batch-migration procedure is repeated for each group of users to be migrated, as shown by the looping arrow in the flow chart. The first pass through the procedure begins with these assumptions:

The following flow chart summarizes the batch-migration process for a proprietary Exchange target. The step numbers in the flow chart correspond to the step numbers in the process instructions. The instructions and field notes here and in the Migrator for Notes to Exchange Administration Guide contain special notes for optional and conditional steps in the procedures.

Step 1: Sync the AD and Domino directories

Conditional Step: This step applies only if CMN is used for directory updates. If not, skip to step 2.

Organizations typically experience staff additions and departures during a migration transition period. Any directory changes that occur during the migration project can introduce data inconsistencies between the source and target environments—changes that occur after the initial directory updates in the pre-migration preparations. These can be reconciled using the CMN Directory Connector. See the Quest Coexistence Manager for Notes User Guide for details.

The CMN Directory Connector can be configured to automatically run directory updates at scheduled intervals. However, it may be useful to also initiate updates manually at this step in the process to ensure the directories are consistent prior to migrating each collection.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating