--- title: Using New-MailboxExportRequest in Powershell slug: using-new-mailboxexportrequest-in-powershell published: 2024-10-03T03:10:54.000Z updated: 2024-10-17T03:09:58.000Z feature_image: /blog/images/using-new-mailboxexportrequest-in-powershell/new-mailboxexportrequest-syntax-microsoft-learn.1600.webp feature_image_alt: Microsoft Learn documentation for the New-MailboxExportRequest cmdlet showing its PowerShell syntax author: James Futhey author_slug: james meta_description: Learn how to efficiently export mailbox data using the New-MailboxExportRequest cmdlet in PowerShell for secure backups and migrations. status: published --- **Exporting mailbox data to a .pst file** is a common task for Exchange administrators, whether it's for backup purposes, legal compliance, or migrating data to another system. However, it can be a bit challenging. One of the most efficient ways to do this in an Exchange environment is by using the **New-MailboxExportRequest cmdlet in PowerShell.** In this article, we'll walk through the key steps and considerations for using New-MailboxExportRequest, making the process straightforward and accessible even for those new to PowerShell. ## What is the New-MailboxExportRequest Command? New-MailboxExportRequest is a PowerShell command used in Microsoft Exchange Server to export the contents of a mailbox to a **.pst file.** This command is essential for **tasks like backing up mailboxes, migrating data, or archiving emails outside the Exchange environment.** Administrators use this cmdlet to specify the mailbox and the destination path for the .pst file, allowing efficient data management within the Exchange infrastructure. Here’s the [syntax of New-MailboxExportRequest](https://learn.microsoft.com/en-us/powershell/module/exchange/new-mailboxexportrequest): ```powershell New-MailboxExportRequest [-Mailbox] -ComplianceStorePath -RemoteCredential [-AcceptLargeDataLoss] [-BadItemLimit ] [-BatchName ] [-CompletedRequestAgeLimit ] [-Confirm] [-ContentFilter ] [-ContentFilterLanguage ] [-DomainController ] [-InternalFlags ] [-IsArchive] [-LargeItemLimit ] [-Name ] [-PreferredMessageFormat ] [-Priority ] [-RequestExpiryInterval ] [-SkipMerging ] [-Suspend] [-SuspendComment ] [-WhatIf] [-WorkloadType ] [] ``` ## 3 Use Cases for New-MailboxExportRequest The New-MailboxExportRequest cmdlet can be used in various scenarios within an Exchange Server environment, including the following three: - **Backing Up Mailbox Data:** Administrators can use this cmdlet to create backups of important mailboxes. For example, before an employee leaves an organization, their mailbox data can be exported to a .pst file. This ensures the organization retains access to emails, contacts, and calendar information, even after the mailbox is deactivated or deleted from the server. - **Mailbox Migration:** When an organization is migrating mailboxes from one Exchange Server to another, or even to a different email system, the New-MailboxExportRequest cmdlet is useful. It allows administrators to export the entire contents of a mailbox to a .pst file, which can then be imported into the new server or system. - **Legal or Compliance Requirements:** In some situations, organizations might be required to preserve mailbox data for legal or compliance reasons. For instance, during an internal investigation or in response to a legal hold, specific mailboxes may need to be exported to .pst files to maintain records of communications. ## Prerequisites to Use the New-MailboxExportRequest PowerShell Command To use the New-MailboxExportRequest cmdlet, you need to ensure the following 5 requisites are met: 1. **Permission Assignment:** You need to have the [necessary permissions assigned](https://learn.microsoft.com/en-us/powershell/exchange/find-exchange-cmdlet-permissions) to your account to run the New-MailboxExportRequest cmdlet. Specifically, you need to be part of a role group that has the appropriate permissions, as not all parameters may be accessible without the correct role. 2. **Unique Name for Export Requests:** If you create multiple export requests for the same mailbox, each request must have a unique name. Exchange can automatically generate up to 10 unique names for export requests. However, if you need to create more than 10 export requests, you'll have to manually specify a unique name for each new request. 3. **Granting Permissions to the Network Share:** The group "Exchange Trusted Subsystem" must be granted the correct permissions on the network share where you plan to export the .pst files. Specifically, this group needs Read/Write permission to save exported .pst files to the share and Read permission to import .pst files from the share. 4. **Network Share Availability:** The network share where you plan to store the exported .pst files must be accessible and properly configured. If Exchange is unable to establish a connection to the network share, you will encounter errors when trying to export the mailbox data. 5. **Ability to Remove Existing Export Requests:** If there are existing export requests that you no longer need, it's important to remove them using the [Remove-MailboxExportRequest](https://learn.microsoft.com/en-us/powershell/module/exchange/remove-mailboxexportrequest?view=exchange-ps) cmdlet. This helps avoid confusion and ensures that you can create new export requests with the default or desired request names. ## How to Use New-MailboxExportRequest in 3 Steps Now that we know everything about how this cmdlet works, it’s time to learn how to use it. ### Step 1: Connect to Exchange PowerShell Before executing this command, we need to **connect to the appropriate Exchange environment.** For on-premises servers, use the Exchange Management Shell, and for cloud-based setups, use Exchange Online PowerShell. Start by opening PowerShell with administrative privileges, then enter: ```powershell Connect-ExchangeOnline -UserPrincipalName youremail@meetingroom365.com ``` You will be asked to provide your **credentials** after entering the command. Once authenticated, your session will be connected to the Exchange Online environment, and you'll be ready to proceed. ### Step 2: Prepare a Folder to Save the .pst File To prepare for using the New-MailboxExportRequest cmdlet, you need to have a network share (a folder on a network) where the exported .pst file will be stored. As mentioned earlier, this folder **must be accessible by the Exchange Server**, and it should have the appropriate permissions set to allow the Exchange Trusted Subsystem group to read from and write to it. [According to Microsoft](https://learn.microsoft.com/en-us/exchange/permissions/role-groups?view=exchserver-2019), the folder must be shared on the network, and the Exchange Trusted Subsystem group must be granted **Read/Write permissions to ensure that the Exchange Server can save the exported .pst file there.** This setup is **crucial to avoid permission errors** and ensure the export process runs smoothly, so don’t skip this step. ### Step 3: Run the New-MailboxExportRequest Cmdlet Once everything is set up, you can export the mailbox to a .pst file. For a basic export, you can follow this example: ```powershell New-MailboxExportRequest -Mailbox "james@meetingroom365.com" -FilePath "\\MeetingRoomServer\MailboxExports\MailboxExport.pst"’ ``` This command creates a **request to export the mailbox data** of "james@meetingroom365.com" to a PST file located at "\\MeetingRoomServer\\MailboxExports\\MailboxExport.pst". Here’s another example: ```powershell New-MailboxExportRequest -Mailbox MeetingRoom -IncludeFolders "#Inbox#" -FilePath \\SERVER01\PSTFileShare\MeetingRoom\InPlaceHold.pst ``` This cmdlet creates a request to **export only the contents of the "Inbox" folder from the "MeetingRoom" mailbox to a PST file** at "\\SERVER01\\PSTFileShare\\MeetingRoom\\InPlaceHold.pst". After initiating the export, you can **monitor its progress using the following command:** ```powershell Get-MailboxExportRequest ``` The [Get-MailboxExportRequest](https://learn.microsoft.com/en-us/powershell/module/exchange/get-mailboxexportrequest?view=exchange-ps) cmdlet provides details about the status of your export request, such as whether it's in progress, completed, or failed. If an **export request fails or you no longer need a request, remove it using:** ```powershell Remove-MailboxExportRequest -Identity "ExportRequest Name" ``` In this case, the cmdlet deletes a specific mailbox export request identified by "ExportRequest Name." Using the New-MailboxExportRequest cmdlet in PowerShell is a powerful way to manage mailbox exports in an Exchange environment, offering **flexibility and control over how data is handled.** By following the correct procedures and understanding the necessary permissions and setup, administrators can efficiently **back up, migrate, or archive mailbox data with confidence**