Move an On Prem Exchange 2010 Mailbox to Office365 via Windows Powershell

Post date: Jun 18, 2014 7:55:23 AM

--- Remote mailbox move---

Open Windows Powershell - Not EMS

$UserCredential = Get-Credential (use domain admin credentials)

$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/powershell-liveid/ -Credential $UserCredential -Authentication Basic -AllowRedirection

Import-PSSession $Session

$OnPremAdmin=Get-Credential

Move Command

new-moverequest -identity domain\username -remote -remotehostname OWA.DOMAIN.IE -targetdeliverydomain domain.onmicrosoft.com -remotecredential $onpremadmin

Additional Switches

-BadItemLimit 500

-AcceptLargeDataLoss

To check status you can use the following commands

Get-moverequest    (displays status of move requests)

Get-moverequest |fl (same as above with a little more info)

Get-moverequeststatists (gives % progress)

Get-MoveRequest -MoveStatus inprogress | Get-MoveRequestStatistics -IncludeReport | select * (gives you a report for all users currently being migrated)

Use the Shell to clear or remove a move request

This example clears the move request from all mailboxes that have a status of Completed.

Copy

Get-MoveRequest -MoveStatus Completed | Remove-MoveRequest

This example removes the move request for Ayla's mailbox.

Copy

Remove-MoveRequest -Identity 'Ayla@humongousinsurance.com'

Resolve failed Mailbox Move Requests    

So chances are there is a good possibility that a small number of mailboxes have the status of Failed and that if you dig in to the log of the transfer you will come across the following error:

    Error: This mailbox exceeded the maximum number of corrupted items that were specified for this move request.

Whenever the Exchange 2010 Mailbox Replication Service comes across a Mailbox with a corrupted piece of data (whether than be an attachment, calendar item etc…) it automatically skips the mailbox and continues to plow through

the rest in your list. This is by design and follows the mantra of “better safe than sorry”.

Fear not, if you are happy to accept data loss (more of this later) we can get around this. Head to your Exchange Powershell and enter the following:

        Get-MoveRequest | where {$_.Status -eq "Failed"} | Set-MoveRequest - BadItemLimit 100 -AcceptLargeDataLoss

The above will get all the mailbox move requests that have failed and set the maximum amount of corrupted items to 100 before it skips the entire mailbox (as what was previously occurring). Note the AcceptLargeDataLoss switch is needed if you set your BadItemLimit switch to anything about 50.

Now that we have told Exchange that we don’t mind a bit of data loss lets resume the move requests:

    Get-MoveRequest | where {$_.Status -eq "Failed"} | Resume-MoveRequest

 Depending on the amount of corrupt items in each mailbox, with any luck they will be now on their way to your new Exchange server. If you get a couple that still don’t move across and failed, just up the BadItemLimit and try again.