Powershell | S l e e k E x c h a n g e

Step 1 – Create User Mailboxes on premises

and migrate from YOUR source into the Mailbox onPrem. If you are coming from Lotus Notes, I would suggest tools from Binary Tree or Quest

Step 2 – Set forwarding SMTP Address to Source Email System

thats for the Delta-Migration time, days or weeks before your Outlook-Rollout. With this you can ensure that already migrated Exchange Online Users can send email to your legacy users

Import-Csv "C:\MigUserGeneral.csv" | ForEach-Object {(Get-Mailbox -Identity $_.EmailAddress | Set-Mailbox -ForwardingSmtpAddress $_.ForwardingSMTPAddress)}

1	Import-Csv "C:\MigUserGeneral.csv" \| ForEach-Object {(Get-Mailbox -Identity $_.EmailAddress \| Set-Mailbox -ForwardingSmtpAddress $_.ForwardingSMTPAddress)}

Example for this “MigUserGeneral.csv”

EmailAddress,ForwardingSMTPAddress,UserPrincipalName,License,UsageLocation,MBXLanguage,TimeZone

Donald.Duck@sleekexchange.net,Donald.Duck@coex.sleekexchange.net,Donald.Duck@sleekexchange.net,"SleekExchange-Tenant:ENTERPRISEWITHSCAL",DE,DE-DE,"W. Europe Standard Time"

Daisy.Duck@sleekexchange.net,Daisy.Duck@coex.sleekexchange.net,Daisy.Duck@sleekexchange.net,"SleekExchange-Tenant:ENTERPRISEWITHSCAL",DE,DE-DE,"W. Europe Standard Time"

Step 3 – Migrate your mailbox content to Office 365

Connect your Powershell to Exchange Online

Set-MigrationEndpoint -Identity NameOfYourEndpoint -Credentials (Get-Credential contoso\xxxxxx)

1	Set-MigrationEndpoint -Identity NameOfYourEndpoint -Credentials (Get-Credential contoso\xxxxxx)

(Note: If you don’t have already a MigrationEndpoint you have to create one. After this you can re-use this endpoint for each batch over and over. http://technet.microsoft.com/en-us/library/jj218611%28v=exchg.150%29.aspx)

New-MigrationBatch -Name XXX -SourceEndpoint NameOfYourEndpoint-TargetDeliveryDomain YourTenant.mail.onmicrosoft.com -CSVData ([System.IO.File]::ReadAllBytes("c:\user.csv")) -AllowIncrementalSyncs $True -AutoStart -BadItemLimit 100 -NotificationEmails alexander.hofer@sleekexchange.net –PrimaryOnly

1	New-MigrationBatch -Name XXX -SourceEndpoint NameOfYourEndpoint-TargetDeliveryDomain YourTenant.mail.onmicrosoft.com -CSVData ([System.IO.File]::ReadAllBytes("c:\user.csv")) -AllowIncrementalSyncs $True -AutoStart -BadItemLimit 100 -NotificationEmails alexander.hofer@sleekexchange.net –PrimaryOnly

(Note: This CmdLet is without the paramenter -AutoComplete which means that the move will suspend at 95%. Further the flip of the Cloud MailUser to the UserMailbox will not occure. The benefit is, that you can move the big data weeks before and cool down :-) Remember: In this state = AutoSuspend the Migration-Service will contact your MRS-Proxy (Mailbox Replication Service) each 24h and will check for new content, and in the case of new content, move the stuff to the cloud. Here you will find information about the user.csv http://technet.microsoft.com/en-us/library/dn170437%28v=exchg.150%29.aspx

Step 4a – Delete the forwarding SMTP Address to your legacy system on your on premises Exchange Server

Import-Csv "c:\MailUserGeneral.csv" | ForEach-Object {(Get-Mailbox -Identity $_.EmailAddress | Set-Mailbox -ForwardingSmtpAddress $Null)}

1	Import-Csv "c:\MailUserGeneral.csv" \| ForEach-Object {(Get-Mailbox -Identity $_.EmailAddress \| Set-Mailbox -ForwardingSmtpAddress $Null)}

Step 4b – Set forwarding SMTP Address on your legacy source to Office 365.

Remember that Microsoft has already done everything your you. MX Records for @yourtenant.mail.onmicrosoft.com is already in place i.e sleekexchange.mail.onmicrosoft.com

Step 4c – Migrate the rest from your source to all Exchange on premises mailboxes

Step 5 – Now your data is completely migrated to your on premises environment and you can move the last delta from 95% to 100%

Complete-MigrationBatch -Identity XXX -NotificationEmails alexander.hofer@sleekexchange.net

1	Complete-MigrationBatch -Identity XXX -NotificationEmails alexander.hofer@sleekexchange.net

(Note: the status AutoSuspend will switch to InProgress and finalize with Completed)

Step 6 – Post doings which some customers prefer

Connect your Powershell to Exchange Online & Office 365

Following Cmdlet will perform:

Set all user calendar to LimitedDetails
Set UsageLocation
Set Office 365 License
Set Mailbox Regional Settings

Import-Csv "MailUserGeneral.csv" | ForEach-Object {(set-MailboxFolderPermission -identity "$($_.UserPrincipalName):\Calendar" -User Default -AccessRights LimitedDetails) ; (get-MsolUser -UserPrincipalName $_.UserPrincipalName | Set-MsolUser -UsageLocation $_.UsageLocation) ;  (get-MsolUser -userprincipalname $_.UserPrincipalName | set-MsolUserLicense  -AddLicenses $_.License) ; (get-MailboxRegionalConfiguration -Identity $_.UserPrincipalName | set-MailboxRegionalConfiguration -LocalizeDefaultFolderName:$true -Language $_.MBXLanguage -DateFormat "dd.MM.yyyy" -TimeZone $_.TimeZone)}

Import-Csv "MailUserGeneral.csv" | ForEach-Object {(set-MailboxFolderPermission -identity "$($_.UserPrincipalName):\Calendar" -User Default -AccessRights LimitedDetails) ; (get-MsolUser -UserPrincipalName $_.UserPrincipalName | Set-MsolUser -UsageLocation $_.UsageLocation) ; (get-MsolUser -userprincipalname $_.UserPrincipalName | set-MsolUserLicense -AddLicenses $_.License) ; (get-MailboxRegionalConfiguration -Identity $_.UserPrincipalName | set-MailboxRegionalConfiguration -LocalizeDefaultFolderName:$true -Language $_.MBXLanguage -DateFormat "dd.MM.yyyy" -TimeZone $_.TimeZone)}

(Note: Use same .csv from Step 2)

have fun, Alex

S l e e k E x c h a n g e

tech shorties from the UC & Office 365 field… FYDIBOHF23SPDLT

Tag Archives: Powershell

Onboarding to Exchange Online / Hybrid Migration to Office 365