サポートと今すぐチャット
サポートとのチャット

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

Step 12: Provision Microsoft 365 from local AD

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

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

1
Run the MNE 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.

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. Select View Summaries | User and Resource Detail to review the per-user data volumes and to modify your collections to accommodate 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-user local data to a central location

Conditional Step: Applies only if you want to use the MNE Data Migration Wizard to batch-migrate data that resides on end-user workstations.

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

Some scenarios require central migration of local Notes PABs and archives. The MNE Data Migration Wizard (in the Batch migration process, as described in this chapter) can migrate content to Exchange mailboxes, personal archives, or PST files. 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-user PAB data to server-based NSFs or into the mail file of each user. Alternatively, the user local data could be copied to a central location by other means.

See chapter 9 of the Migrator for Notes to Exchange Administration Guide for information about how to use the MNE 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 Microsoft 365. Some organizations use temporary SMTP domains to route traffic between Notes and Microsoft 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, you should now establish and configure the smart host servers for Domino and Microsoft 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 when provisioning Microsoft 365 and synchronizing the two directories.

The details of configuring smart-host SMTP mail routing are beyond the scope of this guide. See your Domino and Exchange documentation and online resources for information about configuring smart hosts for those servers. In particular, see the Microsoft article Create a Send connector to route outbound mail through a smart host.

To configure smart-host SMTP routing with Quest Coexistence Manager for Notes (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 Microsoft 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 Coexistence Manager for Notes User Guide (chapter 3) explains these configurations.

Verify your smart host configurations by testing mail flow.

関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択