Summary: New-MailboxExportRequest is an Exchange Management Shell (EMS) cmdlet that is used to export the Exchange database to PST. It helps Exchange administrators to export the primary mailbox contents or archive to .pst file for backup and migration purposes. However, sometimes the New-MailboxExportRequest cmdlet may not work and you may experience an error, such as ‘The term New-MailboxExportRequest is not a recognized cmdlet’. This may happen due to various reasons. In this post, we’ve discussed steps to resolve this error. In addition, we’ve mentioned a third-party tool that you can use if the New-MailboxExportRequest cmdlet fails to export EDB to PST.
Contents
In Exchange, the New-MailboxExportRequest cmdlet is used to export mailboxes from the Exchange database to PST files. The cmdlet can be used to export single or multiple mailboxes to PST format at the desired location. Also, it is often used to create mailbox backups for data protection and migration needs. However, you require additional permissions and roles to run this cmdlet in Exchange Management Shell for mailbox export.
If the necessary permissions or roles are not assigned to the user account that is used to create mailbox export requests, you may experience errors such as, ?The term ‘New-MailboxExportRequest’ is not recognized as the name of a cmdlet.? In such cases, the export request is not created. Besides permissions, the error may also occur due to various other reasons, which are as follows,
- Typo while typing and executing the New-MailboxExportRequest command
- Running the New-MailboxExportRequest in PowerShell window instead of on Exchange Management Shell (EMS)
- Executing the command in Exchange versions before Exchange 2010 SP1
- EMS is not running with administrator rights
- Read/Write permission
Steps to Resolve ?New-MailboxExportRequest is not a recognized cmdlet? Error
Follow the given steps to fix the New-MailboxExportRequest error in Exchange while exporting the mailboxes. However, if these steps do not help or the New-MailboxExportRequest cmdlet fails to export the mailbox content to PST, you can use an EDB to PST converter software such as Stellar Converter for EDB.
Step 1: Update to Exchange 2010 SP1 or Later
The New-MailboxExportRequest cmdlet is available in Exchange 2010 SP1 and later versions only. Thus, if you are trying to execute the command in earlier Exchange versions, it won?t be recognized. As a result, you will experience such an error message.
The solution is to either update or upgrade the Exchange to Exchange 2010 SP1 or later versions.
Step 2: Run Cmdlet in EMS as Administrator
Always open the Exchange Management Shell (EMS) as an administrator to avoid any error while executing the cmdlets. To run cmdlets in EMS, you need rights and permissions to access all files and folders on the system.
Otherwise, lack of permissions and access to required files may cause such error in Exchange during mailbox export.
Step 3: Ensure Required Permissions and Roles
To execute and create mailbox export requests by using the New-MailboxExportRequest, you must assign the Mailbox Import Export Role to the user account. By default, this role is not even assigned to the administrator account. Thus, to avoid the New-MailboxExportRequest error, you must assign the required role to the user or add the user to a role group with Mailbox Import Export permissions.
Use the following command in Exchange Management Shell to assign the required Mailbox Import Export role to the user account that you are using for exporting mailbox to PST via New-MailboxExportRequest cmdlet.
New-ManagementRoleAssignment ?Role "Mailbox Import Export" ?User AdministratorAfter this, restart the EMS and then enter and execute the New-MailboxExportRequest cmdlet for mailbox export.
Step 4: Check Command for Typos
When you type or paste a command, there are chances that you paste extra spaces before or in between the command. Sometimes, the copied command may also contain HTML text or special characters, which may lead to the New-MailboxExportRequest is not a recognized cmdlet error.
To avoid this, always check the command before hitting the ?Enter? key. A typo in PowerShell commands can be disastrous in certain situations. So, be careful while working with any command line tool.
Use EDB to PST Converter Software
If the New-MailboxExportRequest cmdlet doesn?t work or fails to create an export request, you can use an EDB to PST converter software to export mailbox data from EDB to PST.
Stellar Converter for EDB is one such reliable and powerful EDB to PST converter software that helps Exchange admins to extract mailboxes from offline or online Exchange database files (EDBs) and save them as PST. Unlike New-MailboxExportRequest, the software doesn?t require additional permissions or roles to export mailboxes. Plus, it provides a simple graphical user interface (GUI) and enables users to export single or multiple mailboxes to PST from the Exchange database in a few clicks.
Additionally, it also recovers deleted mailboxes and mailbox items, such as emails, calendar, attachments, contacts, etc. Further, you can directly import the converted EDB mailboxes data to live Exchange server or Office 365 accounts with the help of this software.
Conclusion
Although New-MailboxExportRequest enables Exchange administrator to export mailboxes from the Exchange database to PST, it requires additional permissions and roles to work. Also, it works in Exchange 2010 SP1 or later versions and that too, only in On-Premises Exchange. Thus, in absence of these conditions, you may face errors, such as New-MailboxExportRequest is not a recognized cmdlet while executing the cmdlet. The error may also appear if you run the cmdlet in PowerShell or Command Prompt instead of EMS.
In this blog, we have mentioned a few steps that you can follow to fix or avoid the error. However, if these steps don?t fix the problem or the cmdlet fails to export the mailbox to PST, use Stellar Converter for EDB software. It will help you extract the mailboxes from Exchange EDB files and save them as PST or export to live Exchange or Office 365 directly. The demo version of Stellar Converter for EDB is free for download and evaluation purposes.
