Unable to update pre-migration meeting requests after migration to Office 365
We recently migrated from Exchange 2010 to Office 365. At the same time, we changed our naming structure from last name, first name to first name, last name.
The naming change may have been more significant than the migration to 365.
My problem is this: I have staff who have meeting requests with internal and external people from before migration to 365. While the meeting requests migrated successfully, the meeting owner's ability to edit or change the meeting has been lost. Even though the account owner's email address is the same, the name order change may have severed the relationship to the object.
When the person tries to update a meeting, he gets the following NDR:
Your message did not reach some or all of the intended recipients.
Subject: In-Person Meeting
Sent: 8/15/2016 3:36 PM
The following recipient(s) cannot be reached:
Person01 on 8/15/2016 3:36 PM
This message could not be sent. Try sending the message again later, or contact your network administrator. You do not have the permission to send the message on behalf of the specified user. Error is [0x80070005-0x0004dc-0x000
Person02 on 8/15/2016 3:36 PM
This message could not be sent. Try sending the message again later, or contact your network administrator. You do not have the permission to send the message on behalf of the specified user. Error is [0x80070005-0x0004dc-0x000
The NDR is implying that the very person who sent the original meeting request no longer has permission to update his meeting request. I attribute this to both the name order change and the migration from 2010 to 365.
I'd appreciate any suggestions for this issue.
The naming change may have been more significant than the migration to 365.
My problem is this: I have staff who have meeting requests with internal and external people from before migration to 365. While the meeting requests migrated successfully, the meeting owner's ability to edit or change the meeting has been lost. Even though the account owner's email address is the same, the name order change may have severed the relationship to the object.
When the person tries to update a meeting, he gets the following NDR:
Your message did not reach some or all of the intended recipients.
Subject: In-Person Meeting
Sent: 8/15/2016 3:36 PM
The following recipient(s) cannot be reached:
Person01 on 8/15/2016 3:36 PM
This message could not be sent. Try sending the message again later, or contact your network administrator. You do not have the permission to send the message on behalf of the specified user. Error is [0x80070005-0x0004dc-0x000
Person02 on 8/15/2016 3:36 PM
This message could not be sent. Try sending the message again later, or contact your network administrator. You do not have the permission to send the message on behalf of the specified user. Error is [0x80070005-0x0004dc-0x000
The NDR is implying that the very person who sent the original meeting request no longer has permission to update his meeting request. I attribute this to both the name order change and the migration from 2010 to 365.
I'd appreciate any suggestions for this issue.
Adam Brown
This happens when the Legacy Exchange DN is not added to the mailboxes in Office 365 during the migration. How did you complete the migration process?
ASKER
I didn't perform it personally, but there were complications as we started out as a ProPlus 365 customer first - and then upgraded to enterprise. This turned out to be messy requiring deleting and re-adding the users on the 365 side. Then, when we decommissioned the Exchange server (properly instead of just turning it off) again there was a deletion and re-addition and copying over of the Exchange attributes (because we were already syncing the AD objects). I may not be explaining it well, since I only have a limited understanding of the process, but I know that it had bumps in the road either because the path is inherently bumpy - or we made bad choices.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
User upvoted, but no further response to determine if this resolved the issue. Generally, though, this issue is caused by missing x.500 addresses.