We're doing a lot of migrations at the moment; everyone seems to want to dump their on-premise exchange server and head to the cloud. I've read a lot about 365, but something managed to pass me by and this week (3rd migration) I've finally found out about it.
Importing PSTs to the 365 servers from their side; how I missed this I just don't know.
This new process has shaved a lot of time from the migrations, so here goes the new work routine:
1. End of play for the weekend; change MX records to point to 365 and turn off port 25 and 443 on networks firewall
2. Use Exchange Powershell to export all of the PST files from the server into a folder
3. Use AzCopy to upload the PSTs to Office 365
4. Create a mapping file and upload it to Office 365
5. Run the mapping file and import the PST files into the mailboxes
6. Add the accounts to all PCs and off we go
To do step 3 you need to get your SAS URL which is generated from the Office 365 portal and then enter it into the AzCopy cool (its basically the destination on an Azure cloud server).
Read the full Microsoft Documentation here
Here are a few useful commands that you may need following the above steps:
Importing PSTs to the 365 servers from their side; how I missed this I just don't know.
This new process has shaved a lot of time from the migrations, so here goes the new work routine:
1. End of play for the weekend; change MX records to point to 365 and turn off port 25 and 443 on networks firewall
2. Use Exchange Powershell to export all of the PST files from the server into a folder
3. Use AzCopy to upload the PSTs to Office 365
4. Create a mapping file and upload it to Office 365
5. Run the mapping file and import the PST files into the mailboxes
6. Add the accounts to all PCs and off we go
To do step 3 you need to get your SAS URL which is generated from the Office 365 portal and then enter it into the AzCopy cool (its basically the destination on an Azure cloud server).
Read the full Microsoft Documentation here
Here are a few useful commands that you may need following the above steps:
- Having trouble exporting emails from the server because of bad items in a mailbox? use the below switches:
- New-MailboxExportRequest -mailbox jsmith -filepath "\\server\PST\jsmith.pst" -baditemlimit 50000 -acceptlargedataloss
- Need to view the progress?
- Get-MailboxExportRequest
- Want to clear the finished exports from the report?
- Get-MailboxExportRequest -Status Completed | Remove-MailboxExportRequest
- Here's an example from the mapping file:
- Workload,FilePath,Name,Mailbox,IsArchive,TargetRootFolder,ContentCodePage,SPFileContainer,SPManifestContainer,SPSiteUrl
- Exchange,,jsmith.pst,jsmith@contoso.co.uk,FALSE,/,,,,
- Still having people connecting to the old server after migration? did you remember to turn auto-discovery off on the server? read me!
No comments:
Post a Comment