Intra-Forest Domain Migration
The most common scenario for the use of Migration Processing Wizard for Exchange is during Active Directory migration from one domain to another within the same forest. User accounts are migrated with their Exchange-related properties intact.
Role of Migration Processing Wizard for Exchange
After the migration of user accounts is complete, the users in the target domain can still log in to their mailboxes, provided the mailbox has been reconnected. However, these users do not have any of the permissions that the source user accounts had (because the target users have different SIDs). In public folders, the permissions are also based on the old domain configuration.
Run Migration Processing Wizard for Exchange against the Exchange server after the migration to make sure that:
- All delegation-related permissions on the mailboxes are re-aligned correctly to the new users.
- The new users have the same level of access to public folders that the old users did.
|
|
NOTE: You may need to use Migration Processing Wizard for Active Directory in the source domain after these steps. |
Source Forest Becomes an ERF
A popular scenario involving Migration Processing Wizard for Exchange is creation of an Exchange resource forest (ERF) topology instead of a single forest. In this variation of the scenario, user accounts move to another newly-created or existing Active Directory forest, and the target users are supposed to become the new owners of the mailboxes. The source forest remains as an ERF, and the source users are deactivated.
Role of Migration Processing Wizard for Exchange
After the migration of user accounts is complete, the users in the target forest have no access to the mailboxes in the ERF. Run Migration Processing Wizard for Exchange against the Exchange server after the migration to make sure that:
- The target forest user accounts become the new owners of the mailboxes.
- All delegation-related permissions on the mailboxes are re-aligned correctly to the new users.
- The new users have the same level of access to public folders that the old users did.
|
|
NOTE:
- You may need to use Migration Processing Wizard for Active Directory in the Exchange resource forest after these steps.
- ERF setup requires Migration Processing Wizard for Exchange only if the source forest becomes an ERF. If users’ SIDs can be resolved during the Exchange migration, the permissions will be modified correctly for both source and target users.
|
Users Change Forest in an ERF Topology
A possible scenario is when users from one forest have mailboxes in another (ERF) forest and are moved to a third forest. The target users are supposed to become the new owners of the mailboxes in the ERF, and the old forest is supposed to be decommissioned.
Role of Quest® On Demand Migration
After the migration of user accounts is complete, the users in the target forest have no access to the mailboxes in the ERF. Run On Demand Migration for Active Directory against the Exchange server after the migration to make sure that:
- The target forest user accounts become the new owners of the mailboxes.
- All delegation-related permissions on the mailboxes are re-aligned correctly to the new users.
- The new users have the same level of access to public folders that the old users did.
|
|
NOTE: You may need to use Migration Processing Wizard for Active Directory in the Exchange resource forest after these steps. |
Prerequisites (Exchange Server Processing)
- For a successful Exchange directory update, you must use an account with the Full Exchange Administrator role for the Exchange organization.
- For a successful Exchange server update, Integrated Windows authentication must be enabled on Exchange virtual servers and folders.
