Migrator for Notes to Exchange 4.16.3

Re-run the Data Locator Wizard for this collection (only) and select 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.

Reassess the collection membership with respect to the total data volume to be migrated for the collection members. You can 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).

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 instructions for the Collection Wizard.


	NOTE: Notes groups (distribution lists) are typically migrated separately after all users are migrated. The Post-migration activities include the migration of groups.

Step 4: Create Exchange mailboxes and perform Notes administrative operations

Run the MNE 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. After this step Exchange routes all free/busy queries for these users to their new Exchange mailboxes to which the users are fully migrated in the next step.

The Notes administrative operations you select 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 the CMN 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 check box selected but select Disable in the drop-down list.

In some configurations, migrated objects that have been merged or mailbox-enabled in AD become unrecognizable to a Notes' directory update, so the update mistakenly creates duplicate objects in AD. You must Disable foreign directory sync if all three of the following conditions are true:

•

You are using the CMN Directory Connector to perform directory updates from Notes to Exchange during coexistence.

•

Your mail-routing method during coexistence is to use Notes forwarding addresses to set forwarding from Notes to Exchange.

•

The Notes person documents are not set to turn users into Exchange objects.

•

Set user visibility in the Domino directory: Tells the wizard to let you specify the scope of user visibility in the Domino directory. The visibility setting is important when the Quest Coexistence Manager for Notes (CMN) is used to update both directories with modifications. As mailboxes are created in Exchange for migrating users, it can 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 in CMN to ensure the Exchange entries for migrated users are synchronized 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 this section of the Migrator for Notes to Exchange Program Parameters Reference for information about how to assign the values.) If this check box is clear, the wizard ignores the [PersonDocCustom] section of the Task Parameters.

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


	NOTE: Quest recommends you perform the 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 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 final cutover. In this procedure you migrate the user data in the same program run that you 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.

NOTE: If you are migrating data using file system access (rather than by server access):

•

Verify that all migrating users are logged off before you start the Data Migration Wizard. If the data is accessible through the Domino server, Quest recommends you locate and migrate the data using server access. If that is not possible, and you need to use file system access to locate and migrate the data, you must ensure that all users to be migrated (in the current collection) are logged off the system.

•

Also, ensure 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.

Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação

Selecione seu produto:

Para podermos atendê-lo melhor, informe o Propósito de seu chat:

Soluções recomendadas para seu problema

Migrator for Notes to Exchange 4.16.3 - Scenarios Guide

Step 2: Refresh the Migrator for Notes to Exchange SQL data

Step 3: Reassess and refine user collection membership

Step 4: Create Exchange mailboxes and perform Notes administrative operations

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