How to handle the migration of shared or delegated mailboxes? (4230493)

During a migration there will be mailboxes that are shared, either through delegation or via permissions, so that other users can access the resources of other mailboxes. Such an example would be a shared mailbox between a group of users added to their MAPI profile as an additional mailbox, or an assistant that has the delegated permissions on their supervisor's mailbox for the scheduling of appointment etc. How should this be handled?

When mailboxes are shared between users or mailboxes are using the delegate model, it is always recommended that these mailboxes be synchronized and switched along with either the delegator, or the users that are using the shared mailbox. This will remove any problems such as delays during the synchronizing from source to target, or possible permission problems with target users accessing mailboxes in the source.

For further information on this topic such as planning, identifying and implementing, please contact your Quest Engagement Manager, or Professional Services individual.

For additional information related to shared mailboxes please see the following solutions:

Solution SOL53788 - AD permissions are not fully migrated from source to target -https://support.quest.com/SUPPORT/index?page=solution&id=SOL53788

Solution SOL46577 - How does QMM (Quest Migration Manager) handle "Send on Behalf" mailbox permission? -https://support.quest.com/SUPPORT/index?page=solution&id=SOL46577

Solution SOL48950 - Values in the publicDelegates linked attribute that point to groups are not resolved. They are left in Unresolved Links queue. -https://support.quest.com/SUPPORT/index?page=solution&id=SOL48950