Exchange 2016, moving a mailbox after suspending the move

I am in the process of replacing Exchange 2010 on one server with 2016 on another.  It is generally going well except for one issue.

I used EAC to move the mailboxes from the old database to the new one and have a problem.  The first time I attempted the move, it failed because the original server was offline.  It had failed on the first mailbox before I brought the original Exchange back online.  Once that was done, the others synced properly.

Because of a prompt that I saw, I used the shell to suspend the move of the failed account.  I believe that the command that I used was:
Suspend-MoveRequest -identity "email address here"

The batch finished properly with all but the first account moved.

Since then I've tried to move it with EAC but I've been unsuccessful each time.  I can select the one account and go through the steps, but nothing gets moved.  If I look at the details of the batch I see "0 selected of 0 total" at the bottom and "There are no items to show in this view" in the table.  It looks as if I failed to select the email account to move.

Of course, I COULD have made that mistake the first time; I've done worse before!  I was VERY careful the second and third time that I initiated a move and got similar results.

I tried issuing:
Resume-MoveRequest -identity "email address here"
thinking that it may have flagged my address as one not to be moved.  I get an error with that it "Couldn't find a move request...".  That makes sense to me as the request was cancelled.

What do I need to do to get the last mail account moved?
LVL 23
Who is Participating?
CompProbSolvConnect With a Mentor Author Commented:
I believe I found the resolution and will post it here in case it helps anyone else.

There are a number of suggestions here:

The one that did the trick for me is almost at the end.

I did:

 to see the list of users (just as confirmation) and noted that the one was listed as "Failed".  I then did:
Remove-MIgrationUser "email address I'm trying to remove"

That cleared it and allowed me to request again.

It failed the next time, but that is because of exceeding the quota.  That should be easy to fix.
CompProbSolvAuthor Commented:
I fixed the quota problem and it is now syncing.

I don't think it was the Suspend command that got me in trouble.  It appears that after a failed migration batch you need to do the Remove-MigrationUser on the specific mailbox.  The link provides a command to remove ALL of them:

Get-MigrationUser | Remove-MigrationUser -force

I hope this helps someone!
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.