Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

EDIT: significantly changed my question here to streamline it a bit. I've gone ahead and used 100 as my corrupted item count and ran it from the Exchange Shell.

So the trail of tears continues with my SBS 2003 to 2011 migration: all the mailboxes have moved mailbox store from OLDSERVER to NEWSERVER, with the Local Move Requests completing successfully, except for one.

What I'd like to do now is review the previous move request log files: when they were in progress, I could right-click Properties > Log > View Log File, but now that they're completed, that's not available. Nor can I use:

Get-MoveRequestStatistics <user> -includereport | fl MoveReport the move request has now completed and it errors out with "couldn't find a move request that corresponds...".

Basically what I'd like to do is present the list of baditems to the user so that they're aware of what items didn't come across and if anything important was lost, be able to check their current OST, an archive.pst, etc. to recover it if possible.

If this all needs to be wrapped up in a batch Exchange power shell command to pipe the output to log files on disk somewhere, I'm all ears, and would appreciate it for the next migration we do.

share|improve this question
Why is the local move request failing? too many corrupt items? – DKNUCKLES Nov 11 '12 at 14:49
Definitely saw some in the logs, but now that I've cancelled the move request, I'm not sure where the logs are to confirm that was the reason; bit blury-eyed last night. – gravyface Nov 11 '12 at 15:00
up vote 1 down vote accepted

To literally answer your question, no, there is no way to change the mailbox from legacy user to user mailbox.

However, you can delete just the mailbox and create a new one. Make sure to copy all of the addresses from the old mailbox on to the new one. Also get the current Distinguished Name from the current mailbox and add it as an x500 address on the new mailbox.

But this is less than optimal. You should instead restart the mailbox migration and open a new question about why that move is failing.

To see the logs from a previous move, use this powershell command:

(Get-Mailbox **alias** | Get-MailboxStatistics -IncludeMoveHistory).MoveHistory
share|improve this answer
I've restarted it several times. What I'd like to be able to do is find where the log persists after the move fails. right-click properties has nothing now that the move request has been cancelled, but is there a persisted log file somewhere so I can review and fix before starting again? – gravyface Nov 11 '12 at 18:26
See my edit above. – longneck Nov 11 '12 at 21:46
Beauty. Thanks. – gravyface Nov 11 '12 at 22:10

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.