Microsoft Office Tutorials and References
In Depth Information
Migration using remote Windows PowerShell
5. Start the migration by entering the following command:
Start-MigrationBatch
6. During the migration, you can monitor the progress by entering the following
command:
Get-MigrationBatch | fl Status
INSIDE OUT
Cutover migration best practices
Plan to do a cutover migration over a weekend and change the MX record as soon as the
cutover migration is successfully completed. Remember that cutover migrations are for
organizations with 1,000 or fewer mailboxes, and even though there is a final
synchronization, it is common for mailboxes to be missing items between synchronizations if a
cutover migration is left in synchronized mode for an extended period of time.
Therefore, plan to complete a cutover migration in a single pass and switch the MX records
as soon as possible. It also helps if prior to the migration you set the Time to Live (TTL)
for your MX records to be fairly short, thereby reducing the time required for Domain
Name System (DNS) convergence. The Complete-Migration cmdlet is deprecated as of
April, 2012. For more information, see http://community.ofice365.com/en-us/blogs/
ofice_365_technical_blog/archive/2012/04/04/why-administrators-don-t-see-the-com-
plete-migration-button-in-the-e-mail-migration-tool.aspx .
Using remote Windows PowerShell with the latest release of Office 365
with Exchange Online 2013
Follow these steps to initiate a migration to Exchange Online 2013 using remote Windows
PowerShell:
1. Open a new PSSession by entering the following commands:
Import-Module MSonline
$cred = Get-Credential
Connect-MsolService -Credential $cred
$Session = New-PSSession -ConfigurationName Microsoft.Exchange-ConnectionUri
https://ps.outlook.com/powershell/ -Credential $cred -Authentication Basic
-AllowRedirection
Import-PSSession $Session -AllowClobber
Search JabSto ::




Custom Search