Saturday, 12 March 2016

Import PST Files to Office365


A container ship arriving in port on a very calm day.
Migrating data especially importing PST files always been a tedious task and pain for an administrators. Utilizing the local cache always won’t be seamless solution for the users to access the data. Now after Microsoft has launched this new Import service tool, Importing PST’s wont be big challenge for Office365 admins. Here we will see how to utilize this service.
This process follows:
  1. Consolidate PST data to network share
  2. Assign “Import & Export” RBAC permission to access Import service
  3. Install Azure Import tool
  4. Prepare CSV file to start importing
  5. Obtain Unique URL Key
  6. Start upload
Consolidate Data:
Consolidate all PST’s and keep it in network share or Drive.
Assign “Import & Export” RBAC permission to access Import service
  • Login in ECP
  • Go to permissions
  • Create new admin role
  • Select “Mailbox Import Export”
  • Add members who need access
Refer Screenshots below:
ECP
Permission
Admin Roles Import MailboxImport
Prepare CSV file to start importing
Create Csv as mentioned below:
Make one line in the CSV for each PST you wish to import. In the FilePath column for each PST, enter the full “Friendly Path” to that PST. “Friendly Path” means take the path to the PST in your system, and change “\” slashes to “/” slashes, and remove leading slashes, for example:
pst “cy13.pst” stored at \\SERVER01\PSTshareR1\Kingsonfolder, the FilePath column becomes SERVER01/PSTshareR1/Kingsonfolder
The following figure is an example spreadsheet that you can use as a model to create your file:
CSV
Obtain Unique URL Key
  • Login to Office365 admin center
  • Click on Import
  • Upload files over network
  • Show Key & Show URL
  • Create a script as below
AzCopy.exe /Source:C:\PST1 /Dest:https://4d66da4ac2854194b2da046.blob.core.windows.net/ingestiondata/C:/PST1 /Destkey:zbTLKZxRlvxQ9K/nNcn6byhMXsyelkuv3l5Po2w52ZgegxXIlgOk8fGdOqpskCGvu1EKIH/ssFH2eHE03naGiA== /S /V:C:\PSTUpload\Uploadlog.log
Check the Slashes (\) in Source and DEST (/)
AZure
Command
Now start the Mapping Job from Office365 Portal:
Follow the screenshots:
1
2
3
4
5
More details : Click here
Feel free to comment for any questions.

No comments:

Post a Comment

Google+ Followers

Blog Archive