Summary: In this guide, you will learn how to use the Get-MailboxExportRequest cmdlet in MS Exchange via Exchange Management Shell (EMS) to view a detailed status of ongoing mailbox export requests. The cmdlet is used after the mailbox export request has been created via EMS by using the New-MailboxExportRequest.
New-MailboxExportRequest cmdlet is used in MS Exchange 2010 SP1 and later versions to export mailboxes from Exchange database (EDB) files to PST format. However, after the export request is initiated, the PowerShell window doesn’t display any progress or status of export requests. Thus, to view a detailed status of requests initiated by the New-MailboxExportRequest cmdlet, Get-MailboxExportRequest cmdlet is used. It helps admins to find if an export request is completed, stuck, or requires additional actions.
How to Use Get-MailboxExportRequest Cmdlet?
To use the Get-MailboxExportRequest, admin or user should be assigned with the Mailbox Import Export role. Also, you can run the Get-MailboxExportRequest only in on-premise Exchange.
Following is the Get-MailboxExportRequest syntax you can use to search and view the detailed status of the export request,
You can get a list of all mailbox export requests by entering Get-MailboxExportRequest in the EMS. However, you can use various parameters with this cmdlet to filter and view the desired information.
Below are a few examples of the Get-MailboxExportRequest with common parameters. However, you may not have access to all the parameters.
This parameter is used to get the status of ongoing export request that belongs to a particular identity. This identity is created by the user while creating the export request.
This parameter returns the status of ongoing export request with the identity john\EDBtoPST. However, you can’t use this parameter with other parameters such as -BatchName, -Mailbox, -Name, -Status, -Suspend, and -HighPriority.
This parameter is used to filter the results based on the source mailbox, i.e. the mailbox from where data is being exported to PST.
By default, the Get-MailboxExportRequest provides the name, mailbox, source, and status of the export requests. However, you can further use Format-List to display limited and required details in a formatted table list. For instance,
The above command returns the status of export requests created to export PST from Exchange database EDB01. You can change the -Status parameter value with the following to filter and view export requests.
This parameter is used to get the status of a batch export request initiated by using the New-MailboxExportRequest cmdlet.
The above command returns the status of completed PST export requests in My_Report batch.
If the status of the export request is stuck, suspended, or incomplete, you can use the Set-MailboxExportRequest to modify the export request with some exceptions and complete it. Learn more about Set-MailboxExportRequest cmdlet.
But if the export requests are still stuck or not modified and fail to save mailbox data to PST file, you can use EDB to PST Converter software, such as Stellar Converter for EDB.
By using this software, you can export all mailbox items, such as emails, contacts, attachments, notes, etc. from an Exchange EDB file to PST. Unlike EMS, the software is GUI based and displays the export progress. Thus, you don’t need to use the Get-MailboxExportRequest cmdlet or any permission to export PST from the Exchange database files. Besides PST, you can also export and save the mailbox data to EML, MSG, RTF, PDF, and HTML formats in a few clicks.
By using this software, you can avoid data loss, save time and efforts in exporting mailboxes from Exchange to PST, and troubleshooting the export requests by using New-MailboxExportRequest, Set-MailboxExportRequest, or Get-MailboxExportRequest. Also, unlike EMS, the software supports all Exchange versions, such as 2019, 2016, 2013, 2010, 2007, 2003, 2000, and 5.5.
Plus, the software supports both hosted and offline EDB files. And it can export the mailbox data directly to Live Exchange or Office 365.
Reasons to Use Stellar Converter for EDB
Here is a brief comparison (see below table) between the Mailbox Export-Import cmdlets via EMS vs. Stellar Converter for EDB.
You can export Exchange mailboxes to PST manually by using the New-MailboxExportRequest cmdlet and view the progress and detailed status of export by using the Get-MailboxExportRequest cmdlet. You need to manually create individual export requests to export mailbox data to PST and monitor the export requests as no progress is shown. Also, you need permission and assigned roles to export PST by using these cmdlets. On the other hand, these cmdlets are only supported by MS Exchange 2010 SP1 or later versions. Thus, if you need to export PST from older Exchange versions, you can’t use these cmdlets.
Moreover, these cmdlets can lead to loss of mailbox items and incomplete mailbox export due to several reasons discussed in this New-MailboxExportRequest article. To avoid these scenarios and save time, you can use Stellar Converter for EDB. The software extracts the mailboxes from Exchange database files and saves the data to PST files with 100% precision and accuracy, without losing any mailbox item. You can get started by downloading the free demo version below.
Ravi Singh is a Senior Writer at Stellar®. He is an expert Tech Explainer, IoT enthusiast, and a passionate nerd with over 5 years’ experience in technical writing. He writes about Data Recovery, File Repair, Email Migration, Linux, Windows, Mac, and DIY Tech. Ravi spends most of his weekends working with IoT devices and playing games on the Xbox. He is also a solo traveler who loves hiking and exploring new trails. Read More