立即与支持人员聊天
与支持团队交流

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 2: Refresh Migrator for Notes to Exchange's SQL data

To make sure your target AD is provisioned with current object data, update Migrator for Notes to Exchange’s SQL database before migrating each user collection. If you have updated the directories in step 1 above (optional), this process will also copy all updated directory data into the SQL database. To update the SQL server database:

Step 3: Reassess and (if necessary) refine the membership of this user collection

You defined your user collections (migration groups) in the Pre-migration preparations earlier in this chapter. Each pass through this Batch migration process applies these migration tasks to a single collection.

Now that you have updated your directories and refreshed your SQL data (the two preceding steps), you should:

1
Re-run Migrator for Notes to Exchange’s Data Locator Wizard for this collection (only), and then View Summaries | User and Resource Detail, to reassess the per- user data volume in the Notes source for this collection. The Notes Data Locator Wizard is documented in chapter 7 of 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.
3

Step 4: Create Exchange mailboxes and perform Notes administrative operations

Run the Migrator for Notes to Exchange Data Migration Wizard to create Exchange mailboxes and perform pertinent Notes administrative tasks for the users in the current collection. See the Data Migration Wizard chapter of the Migrator for Notes to Exchange Administration Guide for complete instructions. Note that after this step Exchange will route all free/busy queries for these users to their new Exchange mailboxes, to which the users will be fully migrated in the next step below.

The Notes administrative operations you select here will depend on your local circumstances and needs. The available Notes admin operations are:

Set foreign directory sync (feature available only when not setting or removing mail routing): Tells the Wizard to let CMN’s Directory Connector extract user data from the Notes directory during its directory synchronization. (This corresponds to the Notes parameter Allow foreign directory synchronization.) To disable foreign directory sync, leave the checkbox marked but select Disable in the drop-down list box.
Set user visibility in the Domino directory: Tells the Wizard to let you specify the preferred scope of user visibility in the Domino directory. This visibility setting is especially important when Quest’s CMN is used to update both directories with modifications. As mailboxes are created in Exchange for migrating users, it may also be advantageous to set visibility for the same user population. This eliminates the possibility of duplicate entries appearing in the Domino directory for migrated users after subsequent runs of the Directory Connector. The timing of this operation should be coordinated with the Exchange-to-Notes Connector schedule within CMN to ensure the Exchange entries for migrated users a synchronized back to Notes shortly before or after the visibility change.
Set Person Document Attributes: Tells the Wizard whether to assign attribute values to Notes person documents as defined by parameters in the [PersonDocCustom] section of the Task Parameters. (See that section of the Migrator for Notes to Exchange Program Parameters Reference for information about how to assign the values.) If this checkbox is unmarked, the Wizard will ignore the [PersonDocCustom] section of the Task Parameters.

Step 5: Set Notes-to-Exchange mail forwarding, and migrate user data

NOTE: Quest recommends you perform these final cutover tasks in a separate program run of the Data Migration Wizard, rather than in the same run with mailbox-enabling and Notes admin operations (in the preceding step). Some admins have reported latency conflicts when trying to perform all of these tasks together in a single program run.

A user is said to be migrated when he or she has an Exchange mailbox, and all external and internal mail for that user is routed to the new Exchange mailbox, and all of the user’s data has been copied to Exchange (mail, calendar entries, address books, archives, etc.). The event that migrates a user to the target environment is called the user’s "cutover" or "final cutover." In this procedure we migrate the users’ data in the same program run that we set Notes-to- Exchange mail forwarding.

It is critical to set Notes-to-Exchange mail forwarding for these users upon their final cutover, so any mail that arrives during or after the migration will route to Exchange as expected. The Notes-to-Exchange forwarding must remain in place until the MX record is updated to point to Exchange (in the Post-migration activities at the end of this chapter), and all Notes users have been migrated to Exchange.

Also, make sure that the server no longer has the NSF file open in its cache. The dbcache flush command closes all files being held open by the server for users that are no longer logged onto the server. Running the dbcache flush command prevents the server from blocking the Migrator for Notes to Exchange program’s access to the NSF files during the migration run.

Run the Data Migration Wizard again now, to perform this final cutover for users in the designated collection: Set Notes-to-Exchange mail forwarding, and migrate user data from Domino to Exchange. See the Data Migration Wizard chapter of the Migrator for Notes to Exchange Administration Guide for complete instructions.

相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级