Read time 4 minutes
This article explains the use of the “Set-Mailbox Export Request” cmdlet in Exchange Management Shell.
Many Exchange users are aware of the “New-Mailbox Export Request” cmdlet to export Exchange mailboxes as PST files. Exchange administrators must have assigned the Mailbox Import Export Role to carry out this export operation in the Exchange Management Shell.
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.
These export requests do not always become a success but sometimes remain incomplete or get failed. The chances of the export failure are there with factors like incorrect or nil assignment of the export permissions, over-sized messages, bad items, corrupt Exchange database, etc. Here are some information about Repair 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
How to use the Set-MailboxExportRequest cmdlet?
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.
- 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 - 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
- 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
- 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
- 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.
| SWITCH | ROLE |
| BatchName | To specify the batch name |
| Confirm | To specify if to show or hide the confirmation prompt |
| DomainController | To specify the domain controller to read data or write from the Active Directory |
| Identity | To specify the identity of the export request |
| InternalFlags | To specify optional steps in the export request |
| RehomeRequest | To specify the requests to move to the same database from which it is exported |
| WhatIf | To view what changes would occur after applying modifications |
Exporting Exchange mailboxes using Exchange Management Shell requires technical skills to execute the complex cmdlets accurately. Apart from this, users must take care of all the required permissions to execute the commands. Some commands like this one are limited to on-premises Exchange only. So, to simplify the process of Exchange mailbox export, Exchange administrators can try professional tools like Kernel for Exchange Server.
Simplify Exchange mailbox export using Kernel for Exchange Server
A smart way to backup Exchange Server mailboxes to Outlook PST file without any restrictions or complications is by choosing the professional EDB recovery tool. It not only helps in exporting Exchange mailboxes but also in dealing with EDB corruption and access problems in Exchange Server. The tool is a better alternative for the complex 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
Exchange mailbox export is complex when performed with Exchange Management Shell cmdlets. So, one sometimes has to modify and rerun it later. But while using professional tools like Kernel for Exchange Server, Exchange Mailbox export is an easy affair always.
