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.
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. |
2 |
Reassess this collection’s membership, with respect to the total data volume to be migrated with this collection’s members. You may want to move some members from one collection to another to better conform to your organization’s grouping strategy (see the Batch vs. Per-Desktop Migration topic in chapter 3 of the Migrator for Notes to Exchange Pre-Migration Planning Guide). |
3 |
If necessary, rerun the Collection Wizard for this collection to change its membership. Chapter 5 of the Migrator for Notes to Exchange Administration Guide provides field notes and application notes for the Collection Wizard. |
NOTE: Remember that Notes groups (distribution lists) are typically migrated separately, after all users have been migrated. The Post-migration activities described below include the migration of groups. |
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.
• |
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. |
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. |
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.
|
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.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Termini di utilizzo Privacy Cookie Preference Center