Sorry for the long title, but I cant think of any other way of putting it. 

We are testing an Exchange 2010 - 2013 upgrade/migration and as part of the testing we migrated a mailbox from 2010 to 2013, and then moved it back to 2010 again - for testing purposes. Now, when we try and migrate it back from 2010 to 2013 we can select it, initiate the job, but within a couple of seconds the number of mailboxes to move drops to 0 (zero) and then the job completes, with no errors at all, but the mailbox is still on the 2010 Information Store.

Now, we dont plan on doing this but is this unique to use, or is this a bug/feature? Exchange 2010 is at SP3 with UR8MK2, and Exchange 2013 is with SP1/UR8.

Thanks

Hello

tip: get-moverequest -ide email | remove-moverequest
and try move again mailbox.
if not start move try move from powershell:
new-moverequest -ide email -targetdb newdb
and check log: get-moverequest -ide email | get-moverequeststatistics -includereport | fl

Hi Phil,

In addition to the above suggestions, I recommend you check if the mailbox databases are mounted normally. If no, please mount it and continue the move request to check the result.

For your reference:

Mount-Database

https://technet.microsoft.com/en-us/library/aa998871(v=exchg.150).aspx

Hope this can be helpful to you.

Best regards,

Further, when you need to migrate users mailboxes from old server to upgraded one, I would suggest you to follow the Exchange server deployment assistance that is available from Microsoft team and covers all the required aspects in order to accomplish this job easily. Here you go : https://technet.microsoft.com/en-us/office/dn756393.aspx

Moreover, if you wish to achieve this goal automatically, you may also consider on this application available at (http://www.exchangemigrationtool.com/) that could be an alternative approach to get this job done without any interruption.

Thank you all for your answers. I haven't had chance to look at it again but will be very soon and I will feed back.

Thanks again.

Phil

Hi all, as an update to this it does look to be a bug in the BATCH move routine. If you use the powershell cmdlet to just move the mailbox without putting it in a batch it works fine. So this manifests itself more when you use the GUI for mailbox moves as even single items are put into a batch.

Thanks

Phil

Hi Phil,

In your case, I recommend you use EMS to do the migration. What's more, please take your time to post the error message when you migrate mailbox via EAC for my further research.

Best regards,

Hi,

Any update?

Best regards,

Hi, there isnt an error message, it simply starts to do the batch migration and within a few seconds the number of mailboxes to move have reduced to 0 (zero), and then it completes... It is strange...

Phil

Hi,

From your description, I would like to clarify that we couldn't move a mailbox that had been moved until we cleared the move request. In your case, I recommend you clear all the move requests and then continue the migration to check the result.

Hope this can be helpful to you.

Best regards,

Hi,

I am just writing to see if there is any update with your issue. If there is any update, pelase let me know.

Best regards,

Hi, sorry for the late reply. 

The issue is with the Batch Move process, so using the web gui, or the direct Powershell commands. If we delete the previous move requests you still cannot move the mailbox back to 2013, unless you do an individual move-mailbox request (so not part of a batch).

Thanks