New-MailboxExportRequest saves an Exchange mailbox as a PST file on a UNC share after your account receives Mailbox Import Export permission.
Exchange 2010 SP1 introduced the cmdlet and Exchange SE still includes it. Grant Read/Write permission on the share to Exchange Trusted Subsystem. Mailboxes must sit in a mounted database.
New-MailboxExportRequest copies an Exchange mailbox into a PST file on a network share. Exports succeed with the right role, a reachable share and a mounted database. Missing pieces produce short errors.
You get the role setup, the share, the date and folder filters and the checks for a New-MailboxExportRequest status that shows a mailbox export request failed message.
What Permission does New-MailboxExportRequest Need?
Mailbox Import Export is the role New-MailboxExportRequest needs. By default Exchange assigns it to no role group, per Microsoft's New-MailboxExportRequest reference.
Choose a role group you belong to, for example Organization Management. Assign the role to that group.
New-ManagementRoleAssignment -SecurityGroup "Organization Management" -Role "Mailbox Import Export"
Log off and log on afterward, because permission changes need a new logon, per Procedures for mailbox exports to .pst files in Exchange Server. Exchange 2010 pages say to restart the Exchange Management Shell instead.
Skip the role and the cmdlet disappears. Without the role, Exchange 2010 reports that the cmdlet does not exist, according to Understanding Mailbox Import and Export Requests.
“New-MailboxExportRequest is the right tool while the server is healthy. Most failed exports we hear about come down to a missing role or a share permission.”
How do You Set up a UNC Share for PST Files?
New-MailboxExportRequest saves the PST through the Mailbox Replication Service, so the path must be a UNC network share that your Exchange servers can reach.
Microsoft lists two UNC forms, \\Server\Share and \\LocalServerName\c$. Drive letter paths do not count as UNC paths.
How do You Export a Mailbox to PST With PowerShell?
New-MailboxExportRequest starts an export with two parameters, -Mailbox for the source and -FilePath for the PST on your share.
New-MailboxExportRequest -Mailbox ayla -FilePath "\\FS01\PST\ayla.pst"
Exchange 2016 CU7 and later take the alias as the easiest mailbox value. Exchange names requests ayla\MailboxExport0 up to MailboxExport9, so add -Name once one mailbox needs more than 10 requests.
Archive mailboxes use the -IsArchive switch.
New-MailboxExportRequest -Mailbox kweku -IsArchive -FilePath "\\FS01\PST\kweku-archive.pst"
Recoverable Items comes along with its Deletions, Versions and Purges subfolders. Add -ExcludeDumpster to skip that folder.
How do You Export by Date or Folder With New-MailboxExportRequest?
Date filters use -ContentFilter and folder filters use -IncludeFolders in New-MailboxExportRequest.
New-MailboxExportRequest -Mailbox tony -ContentFilter "Received -lt '01/01/2025'" -FilePath "\\FS01\PST\tony-before-2025.pst"
New-MailboxExportRequest -Mailbox lena -IncludeFolders "#Inbox#" -FilePath "\\FS01\PST\lena-inbox.pst"
Received matches mail by arrival time and Sent matches it by sending time, as Filterable properties for the -ContentFilter parameter shows. #Inbox# finds the Inbox even when its folder name is localized.
Microsoft's cmdlet page says -ContentFilter cannot export between two dates. Microsoft's Exchange 2013 page above lists a start and end date example, so test a range on a small mailbox before a full export.
| Parameter | What it controls | Exchange versions |
|---|---|---|
| -ContentFilter | Exports messages that match an OPATH filter | 2010 to SE |
| -IncludeFolders | Exports listed folders only | 2010 to SE |
| -ExcludeFolders | Skips listed folders | 2010 to SE |
| -IsArchive | Exports the archive mailbox | 2010 to SE |
| -BadItemLimit | Sets how many bad items are allowed | 2010 to SE |
| -CompletedRequestAgeLimit | Sets how long completed requests stay | 2013 to SE |
How do You Check and Remove Export Requests?
New-MailboxExportRequest queues requests, Get-MailboxExportRequest lists them and Get-MailboxExportRequestStatistics shows progress.
Get-MailboxExportRequest | Get-MailboxExportRequestStatistics
Get-MailboxExportRequest -Mailbox ayla | Format-List Name,FilePath,Mailbox,Status
Get-MailboxExportRequest -Status Completed | Remove-MailboxExportRequest
Status accepts 10 values including Queued, InProgress, Completed and Failed. Microsoft says CompletionInProgress and AutoSuspended do not apply to export requests.
Export time depends on PST size, network bandwidth and MRS throttling. Microsoft warns of several hours. MRS orders requests by server health, status, priority and last update time.
Exchange SE plus versions 2016 and 2019 delete completed export requests after 30 days by default while failed requests stay, per Procedures for mailbox exports to .pst files in Exchange Server. Remove-MailboxExportRequest clears them sooner.
| Symptom | Cause | Fix |
|---|---|---|
| Cmdlet not found | Role missing or no new logon | Assign Mailbox Import Export then log on again |
| No connection to PST file | Exchange Trusted Subsystem lacks Read/Write permission | Grant Read/Write permission on the share |
| Status stays Queued | MRS orders requests by health and priority | Check progress in the statistics output or raise -Priority |
| Failure on bad items | -BadItemLimit defaults to 0 | Set -BadItemLimit to 10 or lower |
| 11th request refused | Exchange creates only 10 default names per mailbox | Add a unique -Name or remove old requests |
How do You Fix a Failed Mailbox Export Request?
Check why a mailbox export request failed by adding -IncludeReport to Get-MailboxExportRequestStatistics.
Get-MailboxExportRequest -Status Failed | Get-MailboxExportRequestStatistics -IncludeReport | Format-List
Microsoft says a bad item is a corrupt item that cannot be copied and that 0 is the default limit. Set -BadItemLimit to 10 or lower. Try New-MailboxRepairRequest when too many items fail.
Four New-MailboxExportRequest messages appear below with their documented causes.
| Error text | Cause | Fix |
|---|---|---|
| Couldn't find the Enterprise Organization container | Mailbox Import Export role missing from your account (Exchange 2010 SP1 and SP2) | Assign the role with New-ManagementRoleAssignment |
| File could be locked | Wrong server or share name in the path or another request using the same PST | Check the UNC name and use one request per PST file |
Microsoft's article Error when you run New-MailboxExportRequest confirms the container error for Exchange 2010. The Microsoft Q&A thread Mailbox Export Request Error details: File size (16384) is less than header size (17408) covers the file size error.
Resume-MailboxExportRequest restarts suspended or failed requests, per Procedures for mailbox exports to .pst files in Exchange Server.
When does New-MailboxExportRequest Not Work?
New-MailboxExportRequest works only on Exchange servers you host. Four cases leave the cmdlet without a mailbox to reach.
- dismounted, dirty or damaged database
- server removed or organization retired
- mailbox purged after its retention period
- only an .edb file copied from somewhere
Those cases need the PST to come from the file itself, as How to Convert EDB to PST shows. Mailboxes of staff who left follow a separate process, covered by Export a Disconnected Mailbox to PST. Exchange Recovery Database covers old database copies.
How do You Export Mail Without a Mounted Database?
Offline tools open the .edb file directly, so they need no mount, no role and no share where New-MailboxExportRequest needs all three.
Exchange EDB Converter from Univik bypasses the request queue and converts mailboxes from dirty or dismounted files on a Windows PC. Univik Software outputs a separate PST per mailbox by default and splits PST files above a size you set.

| Point | New-MailboxExportRequest | Univik Software |
|---|---|---|
| Server requirement | Live Exchange server | None |
| Database state | Mounted | Mounted, dismounted or dirty |
| Output | PST | Cloud upload plus MBOX, EML, MSG, PDF, HTML, CSV index and PST |
| Mail preview | None | Message by message |
| Trial | Free | 10 messages per folder |
| Price | Free | From $99 for 2 PCs |
- Assign Mailbox Import Export to a role group and log on again before New-MailboxExportRequest.
- Point the export at a UNC share where Exchange Trusted Subsystem has Read/Write permission.
- Use -ContentFilter for dates, -IncludeFolders for folders and -IsArchive for archives in New-MailboxExportRequest.
- Add -IncludeReport to the statistics cmdlet when a mailbox export request failed.
- Switch tools when the database is dismounted, because New-MailboxExportRequest needs it mounted.
Browse mailboxes of a dismounted .edb in Univik Software when New-MailboxExportRequest cannot reach them. Trial edition saves 10 messages per folder. Licences start at $99 for 2 PCs.
Free Download See all featuresQuestions About New-MailboxExportRequest
Does Exchange Online include New-MailboxExportRequest?
No. Microsoft says the cmdlet works only on Exchange servers you host yourself. Exchange Online admins download mailbox items as PST files through eDiscovery, per Export search results in eDiscovery.
Does New-MailboxExportRequest handle all mailboxes at once?
Yes. Create one request per mailbox with its own PST file name. MRS queues the requests and handles several PST files at the same time, per Mailbox imports and exports in Exchange Server.
Is a date range export possible?
No, according to New-MailboxExportRequest, which says -ContentFilter exports from a date or to a date but not both. Its older Exchange 2013 properties page shows a Received range example, so test your range on a small mailbox first.
Does New-MailboxExportRequest work on a dismounted database?
No. New-MailboxExportRequest exports mailboxes from databases that Exchange serves, so dismounted or damaged files need an offline tool. Univik Software accesses dismounted databases offline on Windows PCs without Exchange Server or a request queue.
Does New-MailboxExportRequest change the source mailbox?
No. Microsoft describes exported items as copied to the target PST, so the mailbox keeps them.
How large can the exported PST be?
Microsoft recommends New-MailboxExportRequest exports under 50 GB, because 50 GB is the largest PST size current Outlook versions support. Split a larger mailbox into several requests with folder or content filters, per Mailbox imports and exports in Exchange Server.
Is a local drive path allowed for -FilePath?
No. Microsoft says to use a UNC network share, either \\Server\Share or \\LocalServerName\c$ for the server itself. Mailbox imports and exports in Exchange Server lists both forms.
Does Exchange remove finished export requests by itself?
Yes for completed requests, which Exchange removes after 30 days unless -CompletedRequestAgeLimit says otherwise. New-MailboxExportRequest leaves failed requests in place until you remove them with Remove-MailboxExportRequest, per Procedures for mailbox exports to .pst files in Exchange Server.