Solved

Exchange 2013 Mailbox Migration Failed

Posted on 2016-10-26
3
41 Views
Last Modified: 2016-10-31
In the process of migrating all of my mailboxes from Exchange 2007 to 2013, all of my mailboxes migrated successfully except for 51. Some of them failed because of a mailbox size restriction that was present while trying to move them while others failed to move because of this error: Error: MigrationPermanentException: Active Directory property ‎'homeMDB‎' is not writeable on recipient

However, I believe I have corrected both issues so that the migration can go successfully but when I try to run the migration again it shows the mailboxes trying to sync, then shortly after the Total changes to a '0' then the migration batch completes without actually moving anything.

Any idea on how to fix this? The migration job that is moving all the mailboxes is still going so is it because i need to reset iis and then retry running their migration?
0
Comment
Question by:Joe Lowe
  • 2
3 Comments
 
LVL 9

Expert Comment

by:Marshal Hubs
ID: 41861540
This is because of permission issue!!
Go to Security tab of the account in AD Users and Computers. Check Advanced window, make sure that inheritance is enabled. Please refer this link for more information:http://www.techieshelp.com/exchange-2013-active-directory-property-%E2%80%8Ehomemdb%E2%80%8E-writeable-recipient/
0
 

Accepted Solution

by:
Joe Lowe earned 0 total points
ID: 41861552
I already corrected that issue. I was able to figure out by using stopping the migration batch that was running, open PowerShell, run Get-MigrationUser, noting all the Identities that failed, then running Remove-MigrationUser -Identity TonySmith. By doing that I was able to rerun a migration batch and get the users migrated successfully.
0
 

Author Closing Comment

by:Joe Lowe
ID: 41866623
Was able to figure it out.
0

Featured Post

How Do You Stack Up Against Your Peers?

With today’s modern enterprise so dependent on digital infrastructures, the impact of major incidents has increased dramatically. Grab the report now to gain insight into how your organization ranks against your peers and learn best-in-class strategies to resolve incidents.

Question has a verified solution.

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

How to resolve IMCEAEX NDRs in Exchange or Exchange Online related to invalid X500 addresses.
Did you know that more than 4 billion data records have been recorded as lost or stolen since 2013? It was a staggering number brought to our attention during last week’s ManageEngine webinar, where attendees received a comprehensive look at the ma…
This video discusses moving either the default database or any database to a new volume.
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an antispam), the admini…

685 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