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

Migrator for Notes to Exchange 4.16 - 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 Office 365
Pre-migration preparations Batch migration process Post-migration activities
SSDM (per-desktop) migration

Step 12: Provision Office 365 from the local AD

Conditional Step: Applies only if you are using Microsoft AD Sync tool to provision Office 365 from a local Active Directory. If you are provisioning by Migrator for Notes to Exchange or some other method, you will not provision Office 365 until the Batch migration process later in this chapter. For now, skip ahead to step 13.

Microsoft AD Sync tool copies object data from your local Active Directory up to Office 365, and can provision mail-enabled objects into Office 365 without (yet) creating mailboxes. In this step:

1
Run Migrator for Notes to Exchange’s Data Migration Wizard to Prepare local Active Directory accounts for MS AD Sync. This is a necessary administrative step that must precede your running the AD Sync tool.
2
Run Microsoft AD Sync tool to provision all users in all collections into Office 365 as mail-enabled objects, without mailboxes. (Mailboxes will be created just prior to each user collection’s migration, in the Batch migration process described later in this chapter.)

Step 13: Assess per-user migration volume

Before you migrate any users, you should have a general sense of the volume of data to be migrated by each user, and in each user collection. Migrator for Notes to Exchange offers a Notes Data Locator Wizard that finds source data stores, and determines the per-user data volumes within those stores.

Run the Notes Data Locator Wizard now to find the source data and review per-user data volumes for all user collections, and to verify ownership of archives and PABs prior to migration. Then View Summaries | User and Resource Detail to review the per-user data volumes, and modify your collections (if necessary) to accommodate any unexpected or atypical data volumes. See the Notes Data Locator Wizard chapter in the Migrator for Notes to Exchange Administration Guide. The View Summaries features are part of Notes Migration Manager, described in chapter 1 of the Administration Guide.

Step 14 (if necessary):Copy end users' local data to a central location

Conditional Step: Applies only if you want to use Migrator for Notes to Exchange’s Data Migration Wizard to batch-migrate data that resides on end users’ workstations.

Migrator for Notes to Exchange includes several options for migrating data that resides on end users’ workstations. One approach uses Migrator for Notes to Exchange’s Self-Service Desktop Migrator (SSDM), which offers an optional Silent Mode to minimize user interaction and impact. This approach is discussed in mroe detail in chapter 4 (SSDM (per-desktop) migration) of this Guide.

Some scenarios, however, require central migration of local Notes PABs and archives. Migrator for Notes to Exchange’s Data Migration Wizard (in the Batch migration process, as described later in this chapter) can then migrate content to Exchange mailboxes, personal archives, or PST files. In that case, the program must have access to the source data. Migrator for Notes to Exchange includes a PAB Replicator feature to automate the process of replicating end users’ PAB data to server-based NSFs or into the mail file of each user. Alternatively, users’ local data could be copied to a central location by some other means.

See chapter 9 of the Migrator for Notes to Exchange Administration Guide for full information about how to use Migrator for Notes to Exchange’s PAB Replicator.

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

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

Mail coexistence is configured in both directions when migrating to Office 365. Some organizations use temporary SMTP domains to route traffic between Notes and Office 365, while others prefer to configure SMTP mail routing with smart host servers, for single-namespace environments.

If you have not configured mail routing by subdomains (domain differentiation) in step 5 above, you should now establish and configure the smart host servers for Domino and Office 365.

Either method must be configured at both the server and user levels. At the user level, Notes person documents and AD object records were configured earlier, when provisioning Office 365 and synchronizing the two directories.

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. In particular, see the Microsoft article Create a Send connecto to route outbound mail through a Smart host.

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 Office 365 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.

Remember to verify your smart host configurations by testing mail flow.

Documents connexes