Tchater maintenant avec le support
Tchattez avec un ingénieur du support

Migrator for Notes to Exchange 4.15.2 - Scenarios 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's Office 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 remember to 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 more information about configuring smart hosts for those servers.

To configure smart-host SMTP routing with Quest's CMN, both smart hosts are configured to point to the CMN server. Within 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 CMN User Guide (chapter 3) explains these configurations in much greater detail.

When pre-migration preparations are complete ...

When pre-migration preparations are complete ...

When you have completed the pre-migration preparations described above, go on to the Batch migration process below, 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 users’ local workstations and migrates content for one user. SSDM streamlines the migration 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 (Migrator for Notes to Exchange 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 all of the Pre-migration preparations described earlier 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 target Active Directory is now provisioned with a single mail-enabled object for each Notes object you want to migrate, but no mailboxes have yet been created for these objects.
•
The Notes forwarding addresses in the target AD objects are verified as functional for forwarding mail from Exchange back to Notes.
•
Migrator for Notes to Exchange user collections have been defined (although they may be adjusted with each pass through the batch-migration process).
•
If you intend to use some coexistence strategy, your coexistence method and tools (such as Quest’s Coexistence Manager for Notes), has been configured for any/all coexistence features you plan to use.
 

The 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 below.

The instructions and field notes here and in the Migrator for Notes to Exchange Administration Guide both contain special notes for optional and conditional steps in thse procedures.

Step 1: Sync the AD and Domino directories

 

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

Organizations typically experience staff additions and departures during a migration transition period. Any directory changes that occur during the migration project may 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 CMN’s Directory Connector. See Quest’s CMN User Guide for details.

CMN’s 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 just prior to migrating each collection.

Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation