Permission exist but not work after migrate exchange mailbox to another domain

Chong 871 Reputation points
2022-05-16T04:33:09.74+00:00

Hi,

We use ADMT to migrate domain from A to B, and also move the ex2016 mailbox in domain A to ex2019 in domain B.

After move the user mailbox and relate shared mailbox, user cannot access the shared mailbox in outlook. But can use "open another mailbox" in OWA to access the shared mailbox
Checked in EAC console and also PowerShell "get-mailboxpermission", the permission is existed.
If we add the additional mailbox in outlook, the shared mailbox no permission to access.
If we manual remove and add the permission again, the outlook can auto-map and show the shared mailbox correctly

Seems the permission is migrated but didn't work normally. Is it the know issue if the mailbox move from one domain to another domain?

Thanks

Chong

Exchange | Exchange Server | Management
0 comments No comments
{count} votes

Accepted answer
  1. Kael Yao 37,746 Reputation points Moderator
    2022-05-17T02:41:11.537+00:00

    Hi @Chong

    I tested in my lab and seemed to have reproduced this issue.

    I suppose the cause of this issue is the attribute msExchDelegateListLink which is responsible for automapping, was not migrated either by the Prepare-MoveRequest.ps1 script or ADMT.
    Thus the shared mailbox cannot be automapped in Outlook.

    But as a workaround, you should be able to add it manually in Outlook:

    1. locate File>Account Settings>Change>More Settings>Advanced
    2. add the shared mailbox as an additional mailbox
      202572-23.png

    You may also remove and re-add the permission to have the attribute added to the account.


    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


2 additional answers

Sort by: Most helpful
  1. Andy David - MVP 157.8K Reputation points MVP Volunteer Moderator
    2022-05-16T11:04:57.91+00:00

    I think your best solution is to remove and re-add the perms. They probably need to set again so Exchange "sees" it.

    0 comments No comments

  2. Chong 871 Reputation points
    2022-05-17T02:09:36.85+00:00

    Problem solved.

    It need to include the msExchDelegateListLink attribute during ADMT migration.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.