The Exchange Administrator is able to use the Exchange Management Shell to run different commands to provide more complete and precise access to Exchange mailbox information. There’s a fantastic set of cmdlets the Administrator can run to perform any task. Sometimes, they display certain issues while running in the instances of multiple warnings or errors. These issues can lead to destruction and corruption of the Exchange database, and the administrator should be aware of these issues and take action accordingly.

There is also the option to change the format of Exchange EDB Mailbox in to PST by using third-party tools, however, the present article is focused on getting rid of this mailboxexportrequest cmdlet error that occurs when you attempt to export or transfer Exchange mailboxes into a PST. This article will explain the reason for this error and how an Exchange Administrator can resolve the issue.

What’s the problem?

The mistake we’ll be discussing generally in terms of words appears as follows:

“The Term ‘New-MailboxExportRequest’ is not recognized as the name of a cmdlet, function, script file, or operable program” this indicates that you have not been provisioned with the role.”

There are occasions when an individual or company has to move the EDB data into a PST file. The main purpose behind EDB to PST conversion , the creation of an archive to Exchange database Exchange Database in PST format, which is much more easily accessible than EDB file format during challenging circumstances such as loss of data, server crash, Exchange under maintenance, and so on. You can also utilize no cost methods for converting Exchange database files to PST files.

Related Post: How do I import the Outlook 2010 PST file in Outlook 2016?

Microsoft Exchange Server 2010 and Exchange Server 2013, respectively, to use the Exchange Management Shell actions to transfer Exchange mailboxes into PST format. The EMS command that is utilized by Exchange Server 2010 to export the Exchange mailboxes follows the format below:

New-MailboxRepairRequest [-Mailbox | -Database ] – CorruptionType [-DetectOnly][-DomainController]

Make sure you provide the right values along with Domain Controller name, Fully qualified domain name that is responsible for writing configuration changes into Active Directory.

This command generates an email request that converts EDB mailboxes into PST with additional commands. The execution of Exchange Management Shell commands certainly require technical expertise but can be useful when exporting EDB information to PST. However, there are times where this request for mailboxes fails and the user receives an error message mentioned above.

To find the answer to this issue, it is essential to learn about the reasons behind it.

Why does this error occur?

In a simple manner, some of the effective reasons for the NewMailboxExportRequest is not recognized in Exchange Server are mentioned below:

• The user is running the shortcut to EMS instead of operating it with an administrator
• The required permissions are not available on the account responsible for the execution
• Exchange Server requires an update
• Utilizing Windows PowerShell in place of Exchange Management Shell
• Error(s) in spelling while writing instructions
• Corruption is a problem in EDB files
• Compatibility issue Windows System bit versions

Possible Solutions

1. Designate the appropriate role group

The MailboxExportRequest cmdlet can be used to be used in an on-premises Exchange Server only. It can export content of the primary mailbox as well as archive mailboxes to the PST file. This cmdlet is available in the mailbox Import Export Only in the role. This role isn’t part of any groups by default. If you are an administrator You must include an Export Mailbox Role to the Role Group.

• Within the Exchange Admin Center, go to Permissions, and then select the Admin Roles.
• Choose your Role Group where you want to include the role, and then click Edit.
• Within the role section select the Export Role for Mailbox and save the modifications.
• Save the Changes to the Administrator Roles and exit to the end of the wizard.

2nd Method: Use the correct parameters

If the cmdlet has become stuck because of problems with your source mailbox there are many options to solve them. The most important parameters include:

• -AcceptLargeDataLoss: The parameter will allow the cmdlet to run even if a large number of items in the source mailbox can’t be copied. There is no need to input any number of items to the switch.
• -BadItemLimit: Bad Items Limit displays the items that are corrupt that are in the original mailbox which cannot be copied into the PST file. The parameter sets the number of bad items which are permitted before the request is rejected. You can define the limit for bad items and monitor the items that are in error in the mailbox.

3rd Method

1. One option you could test is selecting “Run as Administrator” option by clicking the EMS icon, rather than using a shortcut to it. Make sure that the login credentials are accurately written. EMS operates only when an administrator has access and the correct login credentials.
2. Install SP1 and then update Exchange If not already done since this is necessary to execute the command to request a mailbox. Once you have updated the EMS, reboot the EMS to observe any change.
3. When writing the commands, make sure that the credentials are valid with no spelling errors. Domain Name should be entered correctly in the command.
4. The account must be assigned the ‘Import Export’ Box in order to fulfill an export-related request.
   1. Give the permission using this command

New-ManagementRoleAssignment -Role “Mailbox Import Export” -User \

1. Then run the export cmdlet. Save local path with this cmdlet

New-MailboxExportRequest -Filepath \\\location\.pst

1. Check your .pst export progress by executing the following command

Get-MailboxExportRequest | Get-MailboxExportRequestStatistics

1. When export is at 100%, take out the any pst move request that is in the queue by using this command

Get-MailboxExportRequest | Remove-MailboxExportRequest

In this section, provide the relevant information such as domain name, username, server filename, location and so on. Exchange Server for each of the commands above.

The solutions described above might fix the issue or may work if the problem isn’t too severe. There are times when Exchange Database files are badly damaged or corrupted or permissions may be in trouble or there are compatibility issues. Thus, EMS commands are not sufficient to convert Exchange EDB data to PST file. Additionally, it is difficult for an untrained user to perform such technical, complicated commands. Data loss could be an issue if you make a mistake. In addition the system administrator is the only person who has the authority to execute the execution of EMS commands. Exchange administrators and users have the an option of performing the transfer of EDB mailboxes to an Outlook PST files more easily and securely with the help of an efficient professional tool that can also assist in recovering Exchange mailboxes, as well as their exports into PST and other destinations, including Office 365 directly. In the next section, learn more about this EDB recovery tool.

Better Alternative Solution

To convert your Exchange mailboxes into PST make use of an expert 3rd-party Exchange Recovery tool that is error-free for both EDB Recovery and Migration. The tool has the latest features and a friendly interface for users to export every element of Exchange mailbox data to an Outlook PST file. It is possible to perform bulk mailbox transfer and also select the data to export using filters. This tool is extensively compatible with the entire range of Exchange Server and Outlook versions. It is recommended that you visit the official website to find out more information about this program in greater detail.

Conclusion

The discussion has been made over the error -NewMailboxExportRequest not recognized in Exchange Server, its causes and solutions. In the final analysis, it was discovered that the most efficient and simple solution to fix this issue is to use an alternative Exchange Recovery tool for the export of Exchange mailboxes to Outlook and other destinations with ease.