Solved

Unable to update pre-migration meeting requests after migration to Office 365

Posted on 2016-08-16
4
185 Views
Last Modified: 2016-09-04
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-0x000524].
 
      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-0x000524].

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.
0
Comment
Question by:APPA_IT_Staff
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
4 Comments
 
LVL 41

Expert Comment

by:Adam Brown
ID: 41758073
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?
0
 

Author Comment

by:APPA_IT_Staff
ID: 41758114
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.
0
 
LVL 41

Accepted Solution

by:
Adam Brown earned 500 total points (awarded by participants)
ID: 41758179
Ok. Check each of the accounts' email addresses. If there is no x.500 address listed, that is the root of your problem with the meeting permissions. X.500 addresses are used by Exchange for communication on the back-end (between exchange servers) rather than the typical email address, and all calendar events are written with an ACL that includes the sender's x.500 address as the owner and the recipient's x500 as a secondary.

If the Exchange server was decommissioned by removing all exchange attributes from the user accounts, the attribute that holds the LegacyExchangeDN value (which translates into the x.500 address) is probably gone, but check to see if it's still there on your user accounts. If it is still there, add the whole string to the proxyAddresses attribute in a test case using this format:
X500:<legacyexchangedn>

Open in new window



That should reconnect the permissions as needed. However, if the legacyexchangeDN is not on any of the accounts, you won't be able to recover easily, since that value is randomly generated at mailbox creation time.
1
 
LVL 41

Expert Comment

by:Adam Brown
ID: 41783525
User upvoted, but no further response to determine if this resolved the issue. Generally, though, this issue is caused by missing x.500 addresses.
0

Featured Post

Get 15 Days FREE Full-Featured Trial

Benefit from a mission critical IT monitoring with Monitis Premium or get it FREE for your entry level monitoring needs.
-Over 200,000 users
-More than 300,000 websites monitored
-Used in 197 countries
-Recommended by 98% of users

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Changing a few Outlook Options can help keep you organized!
Sometimes clients can lose connectivity with the Lotus Notes Domino Server, but there's not always an obvious answer as to why it happens.   Read this article to follow one of the first experiences I had with Lotus Notes on a client's machine, my…
To add imagery to an HTML email signature, you have two options available to you. You can either add a logo/image by embedding it directly into the signature or hosting it externally and linking to it. The vast majority of email clients display l…
CodeTwo Sync for iCloud (http://www.codetwo.com/sync-for-icloud?sts=6554) automatically synchronizes your Outlook 2016, 2013, 2010 or 2007 folders with iCloud folders available via iCloud Control Panel. This lets you automatically sync them with…

626 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question