How to Use the Set-MailboxExportRequest Cmdlet?

Read time 4 minutes

Numerous Exchange users are well-acquainted with the “New-Mailbox Export Request” cmdlet, which facilitates the extraction of Exchange mailboxes into PST files. For this export operation to be executed within the Exchange Management Shell, Exchange administrators are required to be equipped with the Mailbox Import Export Role.

The basic command for the Exchange mailbox export is –

The command needs information like a mailbox name and a network shared folder path for the PST file.

Export requests may not always succeed; they can occasionally remain incomplete or fail. The possibility of export failure exists due to various factors, including incorrect or nonexistent export permission assignments, oversized messages, problematic items, and a corrupted Exchange database. In this context, let’s delve into some information regarding repairing a corrupt Exchange database.

For such incomplete or failed export requests, we have the “Set-Mailbox Export Request” cmdlet, which allows users to modify the export requests are pending.

Let us see some important points related to this “Set-Mailbox Export Request” cmdlet.

Important Points about “Set-Mailbox Export Request” cmdlet

• User must be Exchange administrator or have the equivalent rights
• User must be assigned Mailbox Import Export Role
• Available for on-premises Exchange Server only
• Applicable to Exchange 2010 and later versions
• Used to modify export request options and rerun failed export requests

First of all, Exchange administrators who would be executing the cmdlet must be assigned the Mailbox Import Export Role. For that, users must launch the Exchange Management Shell and run this command to assign the Mailbox Import Export Role to the “Administrator” mailbox.

Now that all the permissions are assigned to the Exchange user or administrator, we can move to the different uses of Set-Mailbox Export Request cmdlet.

1. To perform export allowing data loss
   The switch or parameter AcceptLargeDataLoss can be used with the Set-Mailbox Export Request cmdlet to perform the export, allowing large data loss.
   Run this command.
   Set-MailboxExportRequest -Identity “<mailbox name>\MailboxExport01\” –AcceptLargeDataLoss
2. To prioritize mailbox export request (Low, Lower, High, Higher, Highest, Emergency)
   One can use the Priority switch here with the common cmdlet to run the request with the required priority sequence. Here is an example.
   Set-MailboxExportRequest -Identity “<mailbox name>\MailboxExport01\” –Priority Highest
3. To set Bad Items limit (corrupt mailbox items) to skip while performing the mailboxes export
   The switch is BadItemLimit, and it allows the set number of bad items or corrupted items that can be skipped while performing the request. The command for it is as under.
   Set-MailboxExportRequest -Identity “<mailbox name>\MailboxExport1\” -BadItemLimit 20
4. To set Large Items limit
   Using the switch LargeItemLimit with the “Set-Mailbox Export Request” cmdlet, users can specify the number of large items that can be there. Follow this command.
   Set-MailboxExportRequest -Identity “<mailbox name>\MailboxExport01\” -LargeItemLimit 15
5. To specify an expiry or age limit for the mailbox export request
   Users can utilize the CompletedRequestAgeLimit cmdlet to set a limit of days after which the export request will get automatically removed. Execute this command for it.
   Set-MailboxExportRequest -Identity “<mailbox name>\MailboxExport01\” –CompletedRequestAgeLimit 25

Not just these switches, some other switches can also be used with the Set-MailboxExportRequest cmdlet to modify the export requests in the Exchange Management Shell. Please check the switches and their roles in this cmdlet.

Exporting Exchange mailboxes through the Exchange Management Shell demands a level of technical expertise to ensure the precise execution of intricate cmdlets. Furthermore, users must meticulously manage the necessary permissions to authorize the execution of these commands. It’s worth noting that certain commands, such as the one mentioned, are exclusive to on-premises Exchange deployments. Therefore, for a streamlined and hassle-free Exchange mailbox export process, Exchange administrators may find it beneficial to explore professional solutions like Kernel for Exchange Server.

A highly efficient method for seamlessly backing up Exchange Server mailboxes to Outlook PST files, free from any limitations or intricacies, is to opt for a dedicated Exchange recovery tool. This specialized software not only facilitates the smooth export of Exchange mailboxes but also effectively addresses issues related to EDB corruption and access challenges within the Exchange Server. This tool presents a superior and user-friendly alternative to navigating the complexities of Exchange Management Shell cmdlets.

• Exports both corrupt and healthy EDB mailboxes
• Supports both Exchange on-premises and Exchange Online mailbox export
• A direct and simple procedure of export
• Flexible data saving with multiple selection options and filters
• Export Exchange public folders and archive mailboxes
• Destinations include Outlook PST, Outlook profiles, live Exchange and Microsoft 365
• Free version for trial

Conclusion

Exporting Exchange mailboxes can be a complex task when using Exchange Management Shell cmdlets. This complexity often requires modifications and subsequent reruns. However, when employing specialized tools such as Kernel for Exchange Server, the process of mailbox export becomes effortlessly straightforward.