Mailbox migration with the EMS
DisplayName Aisha Bhari
TotalMailboxSize 564.8 KB (578,340 bytes)
This may be (and probably will be) displayed on the screen differently.
We can see the status of a mailbox move with the following cmdlet:
[PS] C:\>Get-MoveRequest | fl displayname,status,TargetDatabase
DisplayName : Aisha Bhari
Status : Completed
TargetDatabase : DB1
Optionally, we can indicate the threshold of "bad" (or corrupt) items that we are willing to skip (and essentially lose):
[PS] C:\>New-MoveRequest "firstname.lastname@example.org" -TargetDatabase "DB1" -BadItemLimit 100 -AcceptLargeDataLoss
The default is 0.
Mailbox migration with the EMC
Now we'll see the process with the Management Console. I'll also take into account the user's perspective as well.
First, we go to the "Recipients" section of the EMC (below the Organization and Server sections), locate the mailbox in question, right-click on it and select "New Local Move Request".
We then select the target database (click "Next" as needed):
Then we decide the threshold for "bad items" (this is the equivalent of what we did at the command line earlier with the -badItemLimit parameter):
We click "Next/Finish" and if all goes well, we should see this:
The User Experience
This was the result:
This concludes the mailbox migration process in itself.
It can be interesting, and useful for troubleshooting, to compare "Connection Status" and "Autoconfiguration" results before and after the migration.
For example, this...
Note: the server name is "EX1" (the Exchange 2007 server).
Compared to this:
Notice that the name of the CAS Array is also what we see in the account "Server Settings":