Nowadays, Outlook application is becoming more popular due to its advanced features. Thus, most users want to switch to Outlook. Exchange users may require to convert their Exchange file to PST.
In this situation, they can use the New-MailboxExportRequest command to export Exchange 2010 Mailbox to PST format. However, sometimes there are chances that users may not identify the new-mailboxexportrequest cmdlet.
Hence, it will show an error message like New-MailboxExportRequest is not recognized in Exchange 2010, 2013, and 2016. Thus, they need a solution to fix the error message that occurs in Exchange Server. First, let’s understand the PowerShell command and its working.
What is New-MailboxExportRequest?
The New-MailboxExportRequest Powershell command is available only in Exchange on-premises. People are using this cmdlet to start the migration of the primary mailbox of Exchange to Outlook.
However, this command is only available in the Mailbox Import Export role. In addition, the role is not assigned to any role groups by default. Hence, if people want to use the new-mailboxexportrequest Powershell command, then they need to add the Mailbox Import Export role to the role group.
Reasons behind New-MailboxExportRequest Failed Problem
There can be various reasons behind this issue. In this section, we discuss some of the most common causes:
- If MS Exchange Server is not up to date with the new version
- Exchange Management Shell doesn’t have administrator rights
- The Exchange Server database might be corrupted or damaged
- The Exchange account does not have the required permission, which is performing the export request
Fix New-MailboxExportRequest is Not Recognized Issue Manually
There are many manual ways to resolve this Exchange error message. Some of them are explained here:
Solution 1:
First, you need to update the MS Exchange Server after installing the SP1 that is required to run the new-mailboxexportrequest command.
After updating the Exchange server, you need to restart the Exchange Management Shell again and again. If you are still facing the error message, then you should try the next resolving method.
Solution 2:
If you have updated your Exchange Server and the problem has not resolved. Then, you should right click on the icon and run the PowerShell cmdlet as an administrator instead of starting the Exchange Management Shell through the shortcut. After that, due to security reasons, the EMS will disable some commands that are not running or logged in as an administrator automatically.
Solution 3:
Another method to resolve New-MailboxExportRequest not working problem is assigning the import export permission to users. If a person has required permissions then they can initiate the migrating process by using the PowerShell command.
For granting the Read and write permission, users need to click on the checkbox. After that, they will be surely able to resolve the error message New-MailboxExportRequest failed.
Limitations with Manual Methods
The Exchange Management Shell commands are sufficient enough to export Exchange Mailbox to Outlook PST file. But, there are some situations where these Exchange export commands fail to accomplish the task due to many possible reasons.
The manual solution needs a high technical expertise because even the smallest mistake can lead to permanent data loss.
Therefore, generally these methods are performed by system administrators who have a high level of skills and experience. But, even they can face the error in Exchange Server which can be outside of their understanding.
An Alternate Way to Resolve New-MailboxExportRequest is Not Recognized Issue
As it is mentioned in the above discussed section, there are many issues with the manual methods during the conversion process. Hence, in order to resolve the user’s problem, users can choose the professional solution like SysTools Exchange Export tool in spite of using the new-mailboxexportrequest for migrating
Exchange data to PST format. Using this commercial tool, the entire conversion process becomes simple and reliable as the users don’t have to face New-MailboxExportRequest not working problem.
Because, the tool provides a facility to transfer entire mailbox data of Exchange to Outlook without altering the contents of it. The application makes the entire migration process trouble free and efficient as it also supports both bulk and selective migration.
Wrapping Up
The Powershell New-MailboxExportRequest cmdlet is used to export the Exchange contents to a PST file. But, sometimes these cmdlet does not work and displays error message like New-MailboxExportRequest is not recognized as the name of the cmdlet.
Therefore, in this post, we have covered three manual ways to resolve this error message. But it has some limitations. Thus, we have also discussed a trouble free solution to transfer Exchange EDB file to PST format. This solution can overcome the drawbacks of manual procedure.
