In 2010 you were able to import mailboxen from the EMC, and in 2007 you would do it from another server/client which needed to be x86 and have the exchange management tools installed...
But to be honest i'm glad that's no longer required.
So down to business:
To be able to import the psts, you first need the apropriate role memberships/permissions.
To hand out these permissions open the EMS(note that you must have the "organization administration" role/permission)
Issue the following command:
New-ManagementRoleAssignment –Role “Mailbox Import Export” –User <your account>
Then close the shell and restart it, this is needed to enforce your permissions.
Now you are ready to import the psts command is as follows:
New-MailboxImportRequest -Mailbox mailboxname -FilePath \\server\share\file.pst
(please note that it is REQUIRED to use a unc path, this can be \\localservername in case the psts are stored locally. Also it MUST be in a share, so something like c:\folder\psts will not work.
After you completed the command, your request will be queued and progressed, to view this progress you can issue:
Get-MailboxImportRequest
Unfortunately there is no such thing as % process or something...
If the import fails, it's probably because there is a corrupt message(s) in the pst (check event log to verify)
Should this be the case you can add an extra argument allowing corrupt items to be skipped in the import process.
to do so enter
New-MailboxImportRequest -Mailbox mailboxname -FilePath \\server\share\file.pst -BadItemLimit <number of items>
You can import all the mailboxes at the same time, they will be processed one by one.
That's it you're done.
No comments:
Post a Comment