Due to the immense popularity of Microsoft Outlook nowadays, most of the users are now switching their email application. Even the Exchange users are moving their mailbox data to Outlook so that they can use Outlook as their primary email client. Thanks to the New MailboxExportRequest command which made the entire conversion process even easier. Users can use this command to transfer their mailbox data to Outlook but sometimes there are chances that it shows errors like New MailboxExportRequest Not Working or Failed in Exchange 2010, 2013, 2016. In such situations, users can take help of the third party application to export Exchange Mailbox to PST format which will make the entire task easy and secure.
Microsoft Exchange 2013 / 2010 uses Exchange Management Shell commands to move users mailbox data into Outlook PST format. These commands prove to be quiet helpful for import/export purposes and several other uses. Implementing these commands needs a good level of technical knowledge but are free to use.
The New-MailboxExportRequest cmdlet is primarily used to initiate the transfer process. This command’s basic working is to create a mailbox export request which is then followed by several other commands to migrate Exchange mailbox data. This command can be used to create more than one export request per mailbox in which every request should have its unique name. Sometimes, this command fails to execute and throws errors such as New-MailboxExportRequest is not recognized due to which users have to face issues during the conversion process.
Factors Behind New MailboxExportRequest Not Working Error
There can be various reasons behind the issue but we have discussed the most common reasons in the following segment:
- Microsoft Exchange is not up to date.
- Not running EMS commands having administrator rights.
- The account which is performing the export request does not have the necessary permissions.
- The Exchange database might be corrupted or damaged.
Users can analyze why New MailboxExportRequest failed to execute in Exchange 2016, 2013, 2010 and then use one of the solutions explained in the following section to rectify the error.
Manual Method to Fix New-MailboxExportRequest is Not Recognized Error
- Users can update Microsoft Exchange by installing SP1 which is necessary to run the command. Once it is updated, restart Exchange Management Shell again and try running the command again. If it doesn’t works, then you can try the next solution.
- Instead of starting EMS through shortcut, users should run it as an administrator by right-clicking on the icon. Make sure that you are logged in using the administrator credentials. The EMS automatically disables some commands if not running or logged in as an administrator due to security reasons.
- The account must have the “Import Export Mailbox” role so that the user has required permissions to initiate the process.
If the above fixes work for you, then you can resolve New MailboxExportRequest not working error and complete the migration process easily.
Limitations of Manual Procedure
However, the EMS commands are sufficient enough to perform import/export and several other Exchange operations. But, in some situations, these commands fail to accomplish the task due to many possible reasons. Moreover, these require high technical expertise as the smallest of mistake can lead to permanent data loss. Usually, these tasks are performed by system administrators who have a high level of skills and experience. But, even they can face New-MailboxExportRequest is not recognized error in Exchange 2010, 2013, 2016 which can be beyond their understanding.
Error Free Solution to Resolve New-MailboxExportRequest Failed Issue
As there are many issues which a user has to face during the conversion process. Users can use the professional solution using which makes the entire process simple and reliable. This software enables users to transfer entire mailbox data without altering the contents of it. It allows users to preview emails in 8+ view options using which users can ensure that their data is in a healthy state. After that, the data can be exported into 7 file formats such as PST, PDF, MSG, EML and several other formats. The application makes the entire migration process trouble free and efficient as it also supports bulk migration.
It is pretty clear that the slightest of issues such as missing updates or unassigned permissions can bring the task to a halt. Therefore, a user should keep Microsoft Exchange up to date and should have necessary permissions. If the user still gets New MailboxExportRequest not working error in Exchange 2016, 2013, 2010 or other below versions, then they can go for the third party application which will the migration process simple and reliable.