Migrator for Notes to Exchange 4.16.3


	NOTE: This process does not create user Exchange mailboxes until prior to their migration (per user collection, in the Batch migration process) due to the Exchange free/busy limitation (explained in chapter 1, see the Important note under Migration to proprietary Exchange). If you will not configure free/ busy coexistence, you could create Exchange mailboxes earlier in the process in these Pre-Migration Preparations, as long as you also set Exchange-to-Notes mail forwarding for not-yet-migrated Notes users.

The typical and most direct method to provision Active Directory begins with an MNE directory export (step 8), followed by a directory update by the CMN Directory Connector, The illustration that follows includes the export of Domino directory data into the MNE SQL server database.

This provisioning step is necessary even if you have an existing AD that is already provisioned with user objects, since the AD object records must be synchronized with the latest Notes source object records before migration.

Quest recommends the following process to provision Active Directory (after the directory export has populated the MNE SQL server database, in step 8):

Synchronize the Notes/Domino directory with AD. Use the CMN Directory Connector (or some other method) to perform a bidirectional update between the two directories. Other tools and methods are also possible but CMN was designed to complement the Migrator for Notes to Exchange tools. The synchronization reads user data from the Notes source to create corresponding mail-enabled contacts in AD, and vice-versa, to update both directories with routing objects that correspond to users in the other system (to establish complete directories).

If Active Directory does not already contain user objects, the directory update will create them. Many organizations will already have an Active Directory in place for network authentication with users provisioned as security objects. In this case, configure the directory update to create new contacts in AD, which correspond to the existing user objects in AD. (The CMN Directory Connector can detect and merge potential duplicate entities by comparing their addresses but security objects that have been used only for network authentication typically do not have email addresses assigned. See the Coexistence Manager for Notes User Guide for more information.) If applicable, create the necessary connectors in the CMN Directory Connector component and run them to update both directories.


	NOTE: Migrator for Notes to Exchange also includes a feature that can provision users in AD and Exchange with mailboxes directly from contact objects. This can be useful in environments where security principals do not exist in AD and CMN is used to create routing contacts in AD. This approach also is useful for provisioning resource objects in some scenarios. This behavior is controlled by the MBoxFromContact parameter setting described in the Migrator for Notes to Exchange Program Parameters Reference.

Run the MNE Provisioning Wizard for all user collections to consolidate duplicate entities in AD and mail-enable objects already in AD. The Provisioning Wizard merges each information for each contact into the original corresponding AD object record and deletes the contact, leaving a single mail-enabled object in AD for each Notes user. Future directory updates will detect the merged AD object address attribute and will not re-copy the corresponding Notes object.

If contacts were not added to AD for directory coexistence, use the Provisioning Wizard (without contacts) to mail-enable the existing security principals. Addresses and attributes are pulled from the MNE SQL database to mail-enable objects since no corresponding contacts exist in AD.

In any of these scenarios, the result is a single, mail-enabled user object corresponding to each Notes user, and the preservation of any existing security, credentials, and routing. See the Migrator for Notes to Exchange Administration Guide (the Provisioning Wizard chapter) for instructions and application notes.

Verify Notes forwarding addresses. Your mail-routing method allows migrated users to communicate with not-yet-migrated Notes users, relying on existing mail-enabled AD objects to do so. The routing addresses must be verified and tested to ensure proper delivery.

Step 12: Assess per-user migration volume

Before you migrate users, you need an estimate of the volume of data to be migrated by each user and in each user collection. Migrator for Notes to Exchange provides 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 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 refine your collection members to accommodate any unexpected or atypical data volumes. The Notes Data Locator Wizard is documented in the Migrator for Notes to Exchange Administration Guide. The View Summaries features are part of Notes Migration Manager documented in chapter 1 of the Administration Guide.

Step 13 (when appropriate):Redirect inbound external mail to Exchange

Step 13 (when appropriate):
Redirect inbound external mail to Exchange

Modify the MX record to direct incoming external (Internet) mail to the Exchange server. The DNS modification can occur at any time after the user AD accounts are mail-enabled—before, during or after the migration. Some administrators prefer to minimize changes before and during the migration process so they update the MX record after the migration is complete (as described in the Post-migration activities at the end of this chapter).

Other administrators prefer to minimize the "hops" in the forwarding route by modifying the DNS halfway through the migration process. Others make the switch after the target AD objects are mail-enabled (in an earlier step).

In any case, after inbound mail is directed to Exchange, the Notes forwarding addresses in mail-enabled AD objects will route incoming mail to the Notes mailboxes of not-yet-migrated users until they are migrated. Incoming mail is not sent to Exchange mailboxes until MNE tells Exchange to stop routing mail to Notes for those users—when the users are migrated to Exchange with their own Exchange mailboxes.

Step 14 (if necessary):Replicate or copy local data to a central location

Step 14 (if necessary):
Replicate or copy 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 detail in chapter 4 (SSDM (per-desktop) migration) of this Guide.

Some scenarios, however, require centralized batch migration of local Notes PABs and archives. The MNE Data Migration Wizard (described in the next section under Batch migration process) 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 the mail file of each user. Alternatively, user local data could be copied to a central location by some other means.

请选择您的产品：

为向您提供更好的服务，请填写'Purpose of your Chat'（联系目的）：

针对您的问题建议的解决方案

Migrator for Notes to Exchange 4.16.3 - Scenarios Guide

Step 11: Provision AD with mail-enabled users

Step 12: Assess per-user migration volume

Step 13 (when appropriate):Redirect inbound external mail to Exchange

Step 14 (if necessary):Replicate or copy local data to a central location