Archive for October, 2012

~ Complete Migration button in the E-Mail Migration Tool can not see anymore – Office365 Email migration dashboard ~

October 14, 2012 Leave a comment


Enhanced email migration dashboard make administrator more easier to migrate on-premises mailboxes to Office 365.The below shown migration dashboard lets you create and manage multiple migration batches and troubleshoot migration issues, with real-time statistics about the current migration batch and the mailboxes being migrated to Office 365.




With the new enhancements administrators could carryout below tasks with the migration tool dashboard,

  • Create new migration batches and schedule them accordingly.
  • Restart failed migration batches.
  • Get details about skipped items.
  • Open migration reports.
  • Edit Migration batches.

With the new service updates Complete Migration button is completely removed from the migration dashboard. I was surprised when I couldn’t see the Complete Migration button on the Dashboard. With deep analysis I could find the reason Smile.  In earlier version (Exchange Online Build R5 Version – 14.15.xx.x) administrators clicked Complete Migration on the e-mail migration tool (Complete-Migration in Windows PowerShell cmdlet) to complete the overall migration when they had migrated all mailboxes to Office 365 and configured their MX record to point to Office 365. In the recent service update (Exchange Online Build R6 Version – 14.16.xx.x) , the Complete Migration button (and the underlying PowerShell cmdlet) has been removed.


According to the Microsoft TechNet KB article the reason for remove the Completed Migration specified as below,


Here’s why we removed it: the Complete-Migration cmdlet facilitated the notion of a “switch over” to the new cloud mail organization. In other words, after completing the migration, users in the organization would start using their cloud mailboxes. But in reality, running the Complete-Migration cmdlet merely performed a final synchronization between the corresponding on-premises and cloud mailboxes, and then removed any records related to the migration. Completing the overall migration was typically done after the MX record update.  


With the new service update (Exchange Online Build R6) Administrators have more control of their migration at the migration batch level so admin no longer saw the need to complete the overall migration with the introduce of the concept of “multiple migration batches” and moved all the lifecycle control to the migration batch. When a migration batch is completed it’s synced process admin can simply delete the migration batch by selecting it the e-mail migration tool and clicking Delete. This runs the Remove-MigrationBatch cmdlet, which removes any records related to the migration batch and deletes the batch. Until admin do the deletion  once the migration batch sync is completed there will be a synchronization happening in the backend in every 24 hours time from on premises to Office365.

For your additional knowledge I have below showed the way you could retrieve the Exchange Build number from online using PowerShell Cmdlet


Click Start > All Programs > Accessories > Windows PowerShell > Windows PowerShell.

Run the following command (Put your Global Admin Credentials that you used to login to  Portal)

$LiveCred = Get-Credential



$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri -Credential $LiveCred -Authentication Basic –AllowRedirection


Import-PSSession $Session




Run the following command

Get-OrganizationConfig | select AdminDisplayVersion



As you can see above Exchange Online Build version is R6 (

Exchange Online build

14.15. XX . X


14.16. XX . X



Hope this article helpful for you guys… Cheers.. Smile

Categories: Office365