Learn the Usage of New-MailboxExportRequest Exchange 2010

There are multiple scenarios where the Exchange admin looks for a solution to export Exchange 2010 mailboxes to PST. One of the most common reasons is backup of the server data in PST file format to keep the data safe and secure for future purpose. Besides all this, there are few rare conditions where one needs to export mailboxes from Exchange 2010 to Microsoft Outlook PST file. This blog will help users to export Exchange mailboxes into Outlook PST file with the help of New-mailboxexportrequest Exchange 2010. Read the article and know about this PowerShell command that helps you to export EDB mailboxes to PST file. 

About New-MailboxExportRequest PowerShell Command

This command is first introduced in Exchange 2010 sp1 (Service Pack 1). Microsoft Exchange server 2010 administrator is provided with a command to export mailboxes or archived data to PST file. The name of this cmdlet is new-mailboxexportrequest, which establishes a request to perform the migration. Each request will be having an identical name and the maximum mailboxes limit for data exporting is 10. Users can create only one request at a time.

Here, there is no need of having an Exchange Management console to export Exchange 2010 mailboxes to PST. Only the availability of MS Exchange Management Shell is mandatory for running New-mailboxexportrequest Exchange 2010.

The server users of Exchange 2010 are equipped with a bundle of PowerShell commands. These are used when one has to perform import or export operations on the server. Well, the PowerShell scripts are very much helpful and powerful but, unfortunately not supported on 64-bit systems.

Note: If an Exchange server file gets corrupted, disconnected, and dismounted then, one can also rely on the direct EDB to PST migration software provided by SysTools. It is so because it is an independent solution that extract mailbox from offline EDB file of Exchange 2010 and any version and export directly to PST file in a single shot. This utility support both dismounted/offlined Exchange database file and it provides Quick & Advance scan which resolves Exchange mailbox corruption and repair pub1 .edb & priv1 .edb file automatically without using any command. After recovery, users can export the recovered & healthy mailboxes to the Outlook data file in a simplified manner.

Download Now Free Purchase Now 100% Secure

Ways to use New-MailboxExportRequest Exchange 2010

The procedure involves 4 major steps to be performed at the administrative level for a successful migration.

Step #1: Permit all the Important Permissions and Roles

The very first step to exhibit migration is that you have to grant permissions to users for performing the export operation. This assigning activity is to be accomplished manually because by default, no accounts are having rights for the same. So, execute the following command in EMS :
New-ManagementRoleAssignment –Role “Mailbox Import Export” –MyUser Administrator
The command having ‘MyUser’ parameter is the username. After successful execution of this cmdlet, restart EMS session for accessing the required permissions.

Step #2: Develop Network Share to Store Output Files

It is possible that there are several client access server environment within a network. Any of them might process for the request to export mailboxes. Therefore, you need to validate the location of the targeted Outlook PST file. This defined path must be UNC, not the local one. In this situation, the suitable way is to generate a new network with the shared folder. Also, grant this folder with all read/write permissions.


Step #3: Begin Procedure to Use New-MailboxExportRequest
Once you have configured all the suggested things properly then, execute PowerShell commands. These cmdlets will be the one that are basically to transfer Exchange 2010 mailboxes to PST.

1. Export primary user mailbox to PST with following New-MailboxExportRequest Exchange 2010 command :

The parameter <pstfilePath> will describe folder where the server will be saving Outlook file data. This will not be creating the new directory. Instead, it will verify that the defined path is existing. It is so because if you mention an invalid path then, the procedure might gets failed.

2. Transfer particular items from mailbox to PST through the following cmdlets :

3. Use following command line to export personal Exchange archive to PST :

4. Type and execute following cmdlet to export a particular mailbox folder to Outlook :

While executing New-mailboxexportrequest Exchange 2010, mention the mailbox folder, which is to be transferred in Outlook. The folder to be exported needs to be described with ‘#’ symbol in opening and closing part. For instance: You want to export Inbox folder only then, write ‘#Inbox#’ in the command.

Step #4 : Final Time To Monitor and Clean up Mailboxes
This is the final step in which export procedure needs to be cleared. Execute following command to track status of entire active export activities :

Now it is the time to remove all the permissions that were assigned in beginning of the migration procedure :

Use following commands to close the request of exporting mailboxes :

Bringing It All Together

The manual approach involves the usage of new-mailboxexportrequest Exchange 2010 command to export Exchange 2010 mailbox to PST. It is quite obvious that an expert will be able to utilize commands for this kind of data transferring. But, a normal Exchange user or a person having less knowledge about the server will be unable to attempt a manual workaround. Therefore, for such users, we are recommending a product named SysTools Exchange Export that export Exchange mailbox to PST. The software directly exports Exchange mailboxes from Live Exchange 2016, 2013, 2010, etc., to PST file. There is no need for any command or permissions to export Exchange mailboxes to PST file format with this approach. Rest, it is the decision of an individual with which solution they want to go for.

Download Now Free Purchase Now 100% Secure