How to Use Exchange PowerShell Set-MailboxExportRequest Cmdlet? Get Solution

  author
Written By Andrew Jackson
Anuraag Singh
Approved By Anuraag Singh
Published On August 25th, 2022
Reading Time 5 Minutes Reading

Summary: This write-up explains and guide users on how to use the PowerShell Set-MailboxExportRequest in the Exchange Management Shell to recover from the failed export request as well as to change the export request options after creating the request.

Microsoft Exchange Administrator or users use the Exchange New-MailboxExportRequest PowerShell command to bulk export mailbox to PST Exchange 2010, 2013, 2016 but sometimes Exchange mailbox request doesn’t work properly or fail due to some reason. In that case, users can use the set-mailboxexportrequest cmdlet to change the export request.

Note: To use the command it is necessary that you should assign the Mailbox Import Export Role. This cmdlet only applies to the MS Exchange Server 2019, 2016, 2013, 2010 and available only in on-premises Exchange.

How Does Exchange Mailbox Export Request Fail?

There are various reasons due to which the mailbox export request fail. Here are most common reason given below:

  1. Damaged / Corrupted / Unhealthy database
  2. Large MS Exchange database mailbox size
  3. Bad items in Exchange mailboxes that user trying to export
  4. Inadequate permission to run the Mailbox Import Export command

Syntax to Execute Exchange PowerShell Set-MailboxExportRequest Cmdlet

Insert the syntax given below to change the mailbox export request

Set-MailboxExportRequest [-Identity “MailboxExportRequestIdParameter”] [-AcceptLargeDataLoss “SwitchParameter”>] [-BadItemLimit “Unlimited”] [-BatchName “String”] [-CompletedRequestAgeLimit “Unlimited”] [-LargeItemLimit “Unlimited”] [-Priority “RequestPriority”] [-SkipMerging <skippablemergecomponent[]>] [<common parameters>]

There are various parameters given below that users can used in the Set-MailboxExportRequest Command.

1. -AcceptLargeDataLoss

This switch specifies that the Exchange mailbox export request should continue even if the data loss occurs in large amount. It doesn’t need for users to specify the value in this parameter.

Syntax:

Set-MailboxExportRequest -Identity "Kevin\MailboxExport21\" –AcceptLargeDataLoss

2. -BadItemLimit

Users can use this switch that specify the maximum no. of bad item which can be skip during Exchange mailbox export before the request fail. The damaged, corrupted or bad items cannot be stored in the resultant Outlook PST file.

Syntax:

Set-MailboxExportRequest -Identity "Kevin\MailboxExport21\" -BadItemLimit 10

3. -BatchName

This switch is used to specify the name of the batch

Syntax:

Set-MailboxExportRequest –BatchName “InsertNameOfBatch”

4. -CompletedRequestAgeLimit

This switch is used specify the how long user will kept the completed request befor it being automatically removed.

Syntax:

Set-MailboxExportRequest -Identity "Kevin\MailboxExport21\" –CompletedRequestAgeLimit 25

5. -Confirm

The parameter is used to specify in the command to hide or show the confirmation prompt.

Syntax:

Set-MailboxExportRequest -Identity "Kevin\MailboxExport21\" -BadItemLimit 10 –Confirm:$True

6. -LargeItemLimit

It is used in the cmdlet to specify that how much maximum number of large item are allowed before request fail.

Syntax:

Set-MailboxExportRequest -Identity "Kevin\MailboxExport21\" -LargeItemLimit 10

7. -Priority

You can use this switch to set the priority of Exchange mailbox export request such as: Normal (It is the default value), Lowest, Lower, Low, High, Higher, Highest, & Emergency.

Syntax:

Set-MailboxExportRequest -Identity "Kevin\MailboxExport21\" –Priority Low

8. -WhatIf

By using this parameter in the given command users can view what are the changes would occur after applying the changes. There is no need to specify any value in this switch.

Syntax:

Set-MailboxExportRequest -Identity "Kevin\MailboxExport21\" –Priority Lowwst –WhatIf

Syntax to Confirm the Exchange PowerShell Set-MailboxExportRequest Command Worked

Use the command given below to check if the command is successfully worked or not.

Get-MailboxExportRequestStatistics -Identity "Insert_the_Mailbox_Parameter_Name" | Format-List

Note: However, if the command does not change the request or the Exchange mailbox request fail to export the mailbox data to the Outlook Data File. In that case, user can use advanced software provided by SysTools i.e. EDB to PST Converter Software that easily export Exchange database mailboxes to the Outlook PST file format.

Download purchase

This utility supports private and public offline/dismounted Exchange EDB file & export to PST file in bulk. Users can extract mailbox from EDB file Exchange 2016/2013 along with data items (mails, contacts, notes, tasks, calendars, journals) to the Outlook Data File in a simplified manner.

The software provides dual scanning option i.e. Quick & Advanced scan that automatically recovers and repair EDB file along with mailboxes without using any PowerShell command. It provides an interactive graphical interface that makes it easy for users to export the mailboxes to Outlook PST and multiple file-formats: EML, HTML, MSG, MBOX, PDF.

export edb mailboxes

Also, the advance scanning mode recover purged Exchange database mailboxes and data items from offline EDB file. Users can easily use this option to recover deleted mailbox after retention period. After conversion, the software creates an export report in CSV file format which stores the success and fail count of exported Exchange data.

It is also compatible with all versions of Exchange Server (2019, 2016, 2013, 2010, 2007, 2003), Office 365, and Windows OS.

Bringing It All Together

Now users have detailed information on how to use the Exchange Set-mailboxExportRequest command. In case if the cmdlet doesn’t work and leads to data loss of mailboxes and items then the users can use the trustworthy software which easily recovers & repair Exchange mailbox and EDB file from corruption. After recovery, export the Exchange mailboxes to the Outlook data file in a hassle freeway.

  author

By Andrew Jackson

I am SQL DBA and SQL Server blogger too. I like to share about SQL Server and the problems related to it as well as their solution and also I do handle database related user queries, server or database maintenance, database management, etc. I love to share my knowledge with SQL Geeks.