<

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x

Importing PST files in to Exchange 2010

Published on
52,017 Points
28,717 Views
13 Endorsements
Last Modified:
Awarded
Community Pick
Importing PST’s in to Exchange 2010 is a lot easier than it was in 2007 due to the Role Based Access Control (RBAC) feature.

Before we can import PST’s to Exchange 2010 there are a few pre-requisites and they are:

You must have the x64 version of Microsoft Office Outlook 2010 installed on an Exchange Server that has the mailbox role installed.  This doesn’t have to be the mailbox server that all the mailboxes reside on.  NOTE: Prior to Exchange 2007 it was not supported to have any version of Outlook installed on an Exchange Server.  With Exchange 2007/2010 Outlook 2007 and above are supported.
You must configure a group/user with the Mailbox Import Export Management Role
The PST files you are importing (if doing a bulk import) must have the same name as the Exchange Alias for the user it will be imported to
The Mailboxes you are importing the PST’s in to must already exist

Download and install Outlook 2010

At the moment Microsoft Office 2010 is still in Beta release.  Its expected release date is June of 2010.  So you may be a bit jumpy (I know I was) about installing a Beta product on your production Exchange Server.  You don’t need to.  As long as the Exchange Server has the mailbox role on it, it doesn’t need to be the production server, it just needs to be part of the same Exchange Organisation.  So if you have Hyper-V or VMWare available just bring up an Exchange 2010 server purely for management tasks.  This is good practice anyway.

Download Office 2010 from here: http://www.microsoft.com/office/2010/en/default.aspx

The only product you need to install is Outlook 2010 so you can remove all the others if you wish by doing a custom installation.

Configure Mailbox Import Export Management Role

My recommendation would be to setup a group which you assign this role to and then add the users to this group.  If you will be creating a group then it must be a Universal Security Group.  Once you have your group then from an Exchange Management Shell run the following command:

New-ManagementRoleAssignment –Name “MailboxImportExport” –SecurityGroup “your_group_name" –Role “Mailbox Import Export”

Open in new window


At this point I would add the user you will be using to import the PST files to the group you have just created.  Then close the Exchange Management Console/Shell and logoff and back on again.

Importing

There are a few ways you can import PST files, either one by one or in bulk.  I would recommend you try one first just to make sure everything is setup as it should be and if your happy then go for a bulk import.

The commands you need to use are exactly the same for Exchange 2010 as they are for Exchange 2007.

Bulk Import Command:

Get-Mailbox | Import-Mailbox –PSTFolderPath x:\Full_Path_To_PST_Files

Open in new window


NOTE: The x:\Full_Path_To_PST_Files in both commands represents the actual location of the PST files

Single Import Command:

Import-Mailbox –Identity “Display_Name” – PSTFolderPath x:\Full_Path_To_PST_File.PST

Open in new window


NOTE: The –Identity in the single import command can be the display name, the e-mail address or the Exchange Alias.  The actual PST filename needs to be specified when doing a single import.
13
Author:Glen Knight
  • 5
  • 3
  • 2
  • +6
18 Comments
LVL 61

Expert Comment

by:Kevin Cross
demazter,

Very nice article!
Definitely useful information, so thank you for taking the time to write it down.

You have a BIG "Yes" vote from me above.

Regards,
Kevin
0
LVL 74

Author Comment

by:Glen Knight
Thanks Kevin :)
0

Expert Comment

by:emmet5150
This article (last paragraph) states that exporting a mailbox via this method in 2010 will result in the loss of single instance storage???  Can anybody confirm that?
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

LVL 74

Author Comment

by:Glen Knight
emmet5150,
As this is not related to the article I would recommend you open a question.  This way it will receive the exposure it needs from other experts.

0
LVL 74

Author Comment

by:Glen Knight
emmet5150,

Single Instance Storage (SIS)in Exchange 2010 is no longer.  But yes in any version of Exchange that uses SIS when you export the data to PST for that particular persons mailbox SIS is no longer valid.  Otherwise you would not have a copy of the attachment in your mailbox?

Also if you export multiple mailboxes that have the same atatchment in them to PST files then they need to have their own copy of that atatchment, therefore when you import those PST's to another Exchange Server because the Exchange server didn't receive the e-mails it will not be aware that they were the same message and can therefore not implement SIS.

Also the statement at the end of that article that outlook cannot be installed on an Exchange server is incorrect.

Thanks
demazter
0
LVL 76

Expert Comment

by:Alan Hardisty
Please refer to this article which advises it breaks SIS (from Microsoft) but only covers up to Exchange 2003

http://support.microsoft.com/kb/175481
0
LVL 76

Expert Comment

by:Alan Hardisty
This site references SIS in Exchange 2010 and advises that the feature is no longer there:

http://www.slipstick.com/emo/2009/up090910.htm
0

Expert Comment

by:emmet5150
Thanks for clearing that up.
0

Expert Comment

by:r1howell
I've followed this (I think) and when I try to import the pst, I get
StatusCode : -2147467259

any and all help would be greatly appreciated.
0
LVL 4

Expert Comment

by:KzooSteve
A note to others that might be looking to import PSTs into the Online Archive.

It looks like you have to upgrade to SP1 to be able to import PSTs into users Online Archives.
0

Expert Comment

by:dthomas13
r1howell:
I've followed this (I think) and when I try to import the pst, I get
StatusCode : -2147467259

any and all help would be greatly appreciated.

Hey R1howell,

You have to run the command from the Windows Powershell and not the Exchange one.
0
LVL 74

Author Comment

by:Glen Knight
You have to use the Exchange PowerShell.

My advice would be to open a question in the Exchange Zone where the experts can get some more information from you and assist you in resolving the problem.
0

Expert Comment

by:r1howell
Thanks for responses, but I had already migrated needed data manually.
0

Expert Comment

by:Ohmit
Hey guys thanks for spamming up my question :-)

Well Demazter  this doesnt work cause my Exchange Management shell does not look like yours and giving me a lot of errors when entering the commands!
0
LVL 74

Author Comment

by:Glen Knight
Ohmit, have you asked a question in the exchange zone?
0

Expert Comment

by:Ohmit
Now this is embarazing :-)
Someone put a link to your article in my question which I followed without notice.
Im so sorry :-)
0
LVL 5

Expert Comment

by:MacGyver80
Nice article and great read!  

I have a question, I am currently working a contract where I will be pretty much the point person in migrating another company's Exchange 2010 databases in to the client's Exchange 2010 all while converting shared calendar's in to public folders.  Now I've been an admin for Exchange 2010 but never performed a move such as this. Originally I was informed I was going to be working with a Senior Exchange Engineer which I just found out is not an engineer but more of an admin and no preparation has been made with the exception of them creating the accounts on the target domain including exchange accounts. Found this out about an hour ago and my consideration to be a full-time employee is riding on this project.

So now the situation is as follows:

-I wasted 2 weeks planning to use ADMT and the  .\PrepareMoveRequest.ps1 command but the CIO previously rejected the idea of creating a Two Way Transitive Trust between the 2 domain.  So this means the whole project just became more manual....URGGGGH!

-They want to export mailboxes, rules and Public Folders to PSTs and then copy the data via an IPSec tunnel to the target domain

-Employees from the source domain will be keeping their original SMTPs with secondary SMTPs from the company they are merging with

I want to Powershell script this to be able to batch import this in to the corresponding users mailboxes with a log file, if possible.

What would be my best option or choice for this?
0

Featured Post

Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

This video demonstrates how to sync Microsoft Exchange Public Folders with smartphones using CodeTwo Exchange Sync and Exchange ActiveSync. To learn more about CodeTwo Exchange Sync and download the free trial, go to: http://www.codetwo.com/excha…
Whether it be Exchange Server Crash Issues, Dirty Shutdown Errors or Failed to mount error, Stellar Phoenix Mailbox Exchange Recovery has always got your back. With the help of its easy to understand user interface and 3 simple steps recovery proced…

Keep in touch with Experts Exchange

Tech news and trends delivered to your inbox every month