Migration Exchange 2007 -> Exchange 2013 Sp1 Fails after using Remove-MoveRequest with -force
Posted on 2014-07-23
I am having an issue Moving Mailboxes from and Exchange 2007 Server to an Exchange 2013 Sp1 Server.Both server are part of the same Exchange organization.
-I wanted to perform a Mailbox sync on the 221 mailboxes in our organization, with a cut-over at a scheduled time. So I created batch that included all the mailboxes and set the "Manually complete batch" ON. The mailboxes synced to the new Exchange server with no errors. When I scheduled the cut-over and Clicked the "Complete Move" link I noticed that the the Exchange server started to sync the Mailboxes from Scratch(meaning from 0%). It was too late for me to cancel the move as it was showing "completing" status on all mailboxes; furthermore, due to the large amount of mailboxes and Data the sync would have taken me out of the Scheduled outage window. I had to cancel the move.
I performed the below commands:
Remove-MigrationBatch -Identity "blablabla" -Force
Remove-MigrationUser <identity> -Force
-The users are still on the old exchange server(2007) and email is still flowing in; however when I try to create a new batch it and run it, it will indeed create it, but then all the users disappear from the batch. The batch becomes Idle with no users in it.
-if I Use EMS to try to move a user manually using: New-MoveRequest -Identity 'firstname.lastname@example.org' -TargetDatabase "Mailbox Database" -WhatIf it says:
What if: Creating move request "domain.local/username"
-but there is no move request generated.
-I can see that the Mailbox DB on the new server has data, it is quite large and I know it was a mistake to do what I did but Given the fact that the Company operates 24/7, I was forced to use the method I used.
Any Ideas how resolve this issue so I can start the sync process again? I quite new to Exchange 2013.