The export/import mailbox process has undergone a major change in 2010 SP1 Beta compared with the RTM version. Major changes are:
- There is no need to use export-mailbox and import-mailbox cmdlets. The new cmdlets to use are New-MailboxExportRequest and New-MailboxImportRequest.
- Outlook is no longer required to be installed on the machine from which the cmdlets are run.
- Exchange Mailbox Replication service handles the export/import process.
Importing and exporting mailbox data has been improved to allow you to import or export pst files in an asynchronous process. In order to see/run export/import cmdlets in the shell, you should be given explicit permissions. No user is allowed to run the command by default. The user who wants to run the cmdlets should be given “Mailbox Import Export” management role.
Let me explain with an example. I want to give my administrator account the necessary rights to run export/import cmdlets. The cmdlet I need to run is
New-ManagementRoleAssignment –Role “Mailbox Import Export” –User “administrator”
You can also create a group and give the group the necessary access. This way, you only need to add any new users who wants this permission to the correct group using AD Users and Computers (thereby avoiding the shell)!
New-ManagementRoleAssignment –Role “Mailbox Import Export” –SecurityGroup “ImportExportGroup”
Let’s get to business, now that the permissions are in place. In order to export a mailbox to a pst file, the command I need to run is
New-MailboxExportRequest –Mailbox “alias” –Filepath “\servernamesharefile.pst”
Run Get-MailboxExportRequest to find the status of the export process and in my case, it has completed successfully.
I do have the PST file in my C drive!
The file path should be a UNC, otherwise you will get the error below.
Similarly, New-MailboxImportRequest brings the PST file back to exchange. You can import a PST file into the primary mailbox or archive.
I have seen various articles which says that the “export-mailbox” cmdlet is no longer available in SP1 Beta. This is not right. The export-mailbox cmdlet is still available and runs successfully as long as Outlook 2010 X64 is installed. I ran it without any errors in an SP1 Beta server.
You receive the error below if you try running the “export-mailbox” without Outlook 2010 X64 installed.
The export/import process has improved significantly and we no longer need Outlook installed when the new cmdlets are used!