New-Managementroleassignment Mailbox Import Export

Importing / Exporting mail data in .pst files may be performed with various 3rd party applications, but IMHO we should always use what’s “inside-of-the-box” if it’s possible. Therefore you should focus on follownig cmdlets:

  • New-MailboxImportRequest
  • NewMailboxExportRequest
  • Get-MailboxImportRequest
  • Get-MailboxExportRequest

Even as an Exchange Admin, shortly you will find out that none of them are available for you. Pitty. I have no idea why they made it this way, but you have to assign your admin account a new role “Mailbox Import Export”. To do so, execute following powershell cmdlet:

Having that done, you must close Exchange Powershell Console and start it anew. Otherwise cmdlets won’t be available. Next, make sure that you know the target mailbox name and it exists (Get-Mailbox); put the .pst file on the network share since we have to use UNC path.

To start a .pst import run following command:

Optionally you may specify -TargetRootFolder where all data should be imported. This will keep affected mailboxes clean. Another option is to specify which folders from the .pst should be imported – this can be done with IncludeFolders parameter.

Data import process will begin and take some time (depending on the data amount). To stay up to date with current status, you may use Get-MailboxImportRequest cmdlet – this will indicate if the job is queued, running or completed.

If you’re interested in completion percentage, you may pipe Get-MailboxImportRequest to Get-MailboxImportRequestStatistics cmdlet.

More details / examples on usage of cmdlets can be found on Microsoft Technet pages:


Like this:



Tags: Exchange, powershell

# Specific Group

New-ManagementRoleAssignment-Role"Mailbox Import Export"-SecurityGroupExchange-Admin-Group


# Specific User

New-ManagementRoleAssignment-Role"Mailbox Import Export"-UserAdmin




New-MailboxImportRequest-Mailbox targetuser-FilePath"\\PathToFile\file.pst"-TargetRootFolder"Restored_Data"





Applies to: Exchange Server 2010 SP3, Exchange Server 2010 SP2

Topic Last Modified: 2011-03-19

By default, the Mailbox Import Export management role isn't included in any of the built-in role groups, such as the Organization Management role group. To import or export mailbox data, you need to add the Mailbox Import Export management role to a role group.

You can add the Mailbox Import Export management role to a role group with no scope between the role and the role group. When you do this, the implicit read and implicit write scopes of the role apply. For details about how to add the Mailbox Import Export management role to a role group with a predefined scope, see Add a Role to a Role Group.

Looking for other management tasks related to importing and exporting mailbox data? Check out Managing Mailbox Import and Export Requests.

  • Because you can't add roles to built-in role groups, you need to create a role group to which you can add the Mailbox Import Export management role. For detailed instructions, see Create a Role Group.

  • Read the following topics:

  • Be aware that role assignments are additive. This means that all the roles are added together when they're evaluated. If two roles are assigned to a user and one role contains a cmdlet but the other doesn't, the cmdlet is still available to the user.

  • By default, role assignments, including the Organization Management role, don't grant the ability (called role delegation) to assign roles to other users. Role delegation is an advanced task. To enable a user to assign roles to other role groups, see Delegate Role Assignments.

After you add the Mailbox Import Export management role to a role group, you may also want to:

© 2010 Microsoft Corporation. All rights reserved.
Categories: 1

0 Replies to “New-Managementroleassignment Mailbox Import Export”

Leave a comment

L'indirizzo email non verrà pubblicato. I campi obbligatori sono contrassegnati *