Clean Up Legacy Account Permissions
Once your users have started to log on under their new accounts in the target domain and are not experiencing any problems with access to resources, you may want to remove unnecessary references to the original source accounts in groups, user rights, and object security descriptors.
|
|
Caution: Cleanup is hard to undo, so it is recommended that you clean up permissions only when you are sure that all users are using their target accounts for all applications and have no problems accessing resources. |
Cleanup of legacy account permissions is performed by the same wizards used to update resources. Refer to the table below to choose the resource updating tool and the right option to cleanup legacy account permissions from distributed resources, Active Directory, and BackOffice servers.
| To clean up legacy account permissions for | Tool to use | Re-permissioning option to choose | References |
|---|---|---|---|
| Distributed resources | Resource Updating Manager |
Clean up legacy local group membership, user rights and permissions of migrated users. This option is available when you create a processing task in Resource Updating Manager. |
See the Distributed Updates in Resource Updating Manager section of the Migration Manager for Active Directory Resource Processing Guide. |
| Active Directory | Active Directory Processing Wizard | Clean up group membership and permissions of migrated users | See the Active Directory Processing section of the Migration Manager for Active Directory Resource Processing Guide. |
| Exchange servers | Exchange Processing Wizard | Clean up legacy object ownership and permissions of migrated users | See the Exchange Processing section of the Migration Manager for Active Directory Resource Processing Guide. |
| Systems Management servers | SMS Processing Wizard | Clean up object ownership and permissions of migrated users | See the SMS Processing section of theMigration Manager for Active Directory Resource Processing Guide. |
|
|
Caution: After the cleanup, users from the source domain will lose their access rights. If cleanup is done before running Resource Updating Manager with the Reassign local group membership, user rights, and object permissions to target users option selected, there will be no way to get these permissions back, nor will there be a way to reassign permissions to target users by Resource Updating Manager. You will have to restore resources from a backup. |
Decommission Migrated Environments
In an Exchange migration, after mailbox migration is completed, you can clean the source mailboxes and move them to another server in the same administrative group. This ensures the uninterrupted collaboration for the other users of source organization and frees up hardware.
The last server of the source administrative group should be kept and maintained until the whole Exchange migration is completed.
Uninstalling Migration Manager for Exchange
To uninstall Migration Manager for Exchange including all installed updates perform the following steps:
- Start the Migration Manager console.
- Switch to the Exchange Data tab.
- Go to the Agent Management node of the navigation tree.
- In the middle pane, select all agent hosts where legacy Exchange agents and/or Migration Agent for Exchange are installed
- Perform the Revoke Roles | All Roles operation for all hosts where legacy Exchange agents and/or Migration Agent for Exchange are installed.
- Close Migration Manager Console.
- Open Programs and Features in the Control Panel and select Quest Migration Manager 8.15 and click Uninstall.
|
|
IMPORTANT: Quest Migration Manager 8.15 product updates should not be uninstalled from the list of installed updates in the Installed Updates section. The product update removal is not supported. You can only completely uninstall Quest Migration Manager for Exchange 8.15. This will do the complete uninstall for the whole product, including installed Public Update. |
