New mailboxexportrequest не распознано как имя командлета
Trying to run New-MailboxExportRequest cmdlet on Exchange 2010 SP1 or later and getting following error.
The term ‘New-MailboxExportRequest’ is not recognized as the name of a cmdlet, function, script file, or operable program.
The most likely reason is that your user account doesn’t have Mailbox Import Export role. To add it run:
New-ManagementRoleAssignment -Role «Mailbox Import Export» –User domain\user.name
Restart Exchange Management Shell and you should be good to go.
New-MailboxExportRequest is not recognized in Exchange Server
We need to export a mailbox to PST file. The problem is that we are getting an error after running the New-MailboxExportRequest cmdlet. The term ‘New-MailboxExportRequest’ is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. After the error, it did not export the mailbox to PST in Exchange Server. In this article, you will learn why this is happening and the solution to New-MailboxExportRequest is not recognized.
Table of contents
New-MailboxExportRequest is not recognized
Run Exchange Management Shell administrator. Run the New-MailboxExportRequest cmdlet, including -Mailbox and -Filepath parameters.
After running the cmdlet, the output gives us the following error:
New-MailboxExportRequest : The term ‘New-MailboxExportRequest’ is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
Why do we get this error, and what is the solution for new mailbox export request is not recognized?
Get role Mailbox Import Export
Let’s find out who is assigned to the role Mailbox Import Export. Make use of the Get-ManagementRoleAssignment cmdlet.
What if you have a long list and you like to filter the result? Let’s search and filter on the account name.
If you inspect closely, you will find that the assignment grants Organization Management members like you only delegation rights. This allows you, as an organization administrator, to decide who can run Mailbox Import Export cmdlets.
Why are these roles not assigned to anyone by default?
When you assign the role “Mailbox Import Export”, it also grants full access rights to all mailboxes in its scope. Since this can be a security issue, it is not assigned to anyone by default.
Note: By default, nobody has access to import and export mailboxes in Exchange Server.
Solution for New-MailboxExportRequest is not recognized
In my example, the Administrator account is assigned to a Role Group called Organization Management. That group has access to the role Mailbox Import Export Delegating. We have to add the admin account to the role.
If the admin account is not added to the role, you are not able to run the cmdlet. This will not give you access to export mailboxes to PST.
We have two options:
- Add admin account directly to the role
- Create a new role group and add admin account to that group (recommended)
Important: After assigning the permissions, close Exchange Management Shell and rerun it for changes to take effect.
Option 1. Add admin account directly to the role
Run the following cmdlet to give the admin account access to the role.
The account is successfully assigned to the Mailbox Import Export role.
Verify the permissions
You can double-check if you have access to the role with the first cmdlet in this article.
The admin account is Direct assigned to the role. Restart Exchange Management Shell and run the Mailbox Export cmdlet. The New-MailboxExportRequest is not recognized error is gone.
Option 2. Create a new Role Group and add admin account to that group
Run the following cmdlet to create a new role group and assign the admin account to that group.
The role group is successfully created, and the admin account is a member of the role group.
Verify the permissions
Go to Active Directory and open the OU Microsoft Exchange Security Groups in the root domain of the forest. A new Universal Security Group is created with the name Exchange Mailbox Import Export.
You will also notice the admin account we specified has been added to Members.
Now that you have the permissions, read the article Export Exchange mailbox to PST with PowerShell.
Remove permissions from the role
Security-wise, it’s good to remove the permissions after you’re done with the mailbox to PST export.
If you followed option 1, remove the admin account from the role.
If you followed option 2, I recommend keeping the role group and only delete the admin account from it.
If you need to export a PST in the future, you can always add the admin account to the group.
If you want to remove the created role group, run the following cmdlet.
Conclusion
You learned why New-MailboxExportRequest is not recognized in Exchange Server. Add the admin account directly to the Mailbox Import Export role. After assigning the permissions, restart Exchange Management Shell. Don’t forget to remove the assigned role permissions when the PST export is finished. The Microsoft Exchange team has written about this.
Did you enjoy this article? You may also like DFSRDIAG POLLAD is not recognized. Don’t forget to follow us and share this article.
ALI TAJRAN
ALI TAJRAN is a passionate IT Architect, IT Consultant, and Microsoft Certified Trainer. He started Information Technology at a very young age, and his goal is to teach and inspire others. Read more »
What Others Are Reading
We recommend enabling TLS 1.2 on Exchange Server 2013/2016/2019 and disabling TLS 1.0, TLS 1.1,…
The Exchange mail.que file is getting large in size. You get an alert that your…
An Exchange Server is already up and running in the organization. Before installing a second…
This Post Has 7 Comments
Your posts are amazing. Thanks a lot for this. It worked perfect.
For everyone that is reading; You really need to restart Exchange Management Shell for the changes to work (as shown in the post). I thought I mention it again just in case!
Thanks for this Ali. Very useful article and has helped me achieve my aim.
As a heads up, because this is the #1 google return for this question and others might try it- these instructions do NOT work anymore. As of Date 10/2020. PSVersion=5.1.14393.3471 / azure AD module 2.0.2.4, even if you have the above rights, you still receive command not found.
This article is for Exchange on-premises. It will not work for Exchange Online. Use eDiscovery to Export Office 365 mailbox to PST.
New-MailboxExportRequest is not a recognized Cmdlet
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.
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 Administrator
After 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.
About The Author
Ravi Singh is a Senior Writer at Stellar®. He is an expert Tech Explainer, IoT enthusiast, and a passionate nerd with over 7 years of experience in technical writing. He writes about Microsoft Exchange, Microsoft 365, Email Migration, Linux, Windows, Mac, DIY Tech, and Smart Home. Ravi spends most of his weekends working with IoT (DIY Smart Home) devices and playing Overwatch. He is also a solo traveler who loves hiking and exploring new trails.
New MailboxExportRequest is not recognized in Exchange Server – The Term Solved
The Exchange Administrator can use Exchange Management Shell to run several commands that provide a greater control and more in-depth reach towards the Exchange mailbox data. There are is great set of cmdlets that the Administrator can run and perform any action. Sometimes, the cmdlets show some problems while running in forms of several errors or warnings. These problems can cause corruption and deletion in the Exchange database and the Administrator should tackle these errors smartly.
You can also convert Exchange EDB Mailbox to PST using third party tools, but the present article focuses on removing the MailboxExportRequest cmdlet error while trying to transport or export the Exchange mailboxes to PST file. The article will show why does the error occur and how the Exchange Administrator can troubleshoot it.
What is the error?
The error that we are going to discuss basically in words is displayed like this –
“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 times when a user or organization requires moving the EDB data to PST file. The common reason for EDB to PST export is creating a backup of the Exchange database in PST file format which is easily accessible than the EDB file format in difficult times like data loss, Server crash, Exchange under maintenance, etc. One can also use free methods to convert Exchange EDB to PST file.
Microsoft Exchange Server 2010 and Exchange Server 2013 utilize the Exchange Management Shell commands to migrate the Exchange mailboxes to PST format. The EMS command that is being used by the Exchange Server 2010 for exporting the Exchange mailboxes is as given below:
Provide the correct respective values with Domain Controller name, Fully Qualified Domain Name mainly responsible for writing configuration changes to Active Directory.
This command creates a mailbox request and converts EDB mailboxes to PST with some more commands usage. This execution of the Exchange Management Shell commands certainly requires technical knowledge but is useful in exporting EDB data to PST. But there are situations when this mailbox-request becomes failed and in turn the user received the error message as mentioned above.
To reach the solution for this error, first it is important to know about the causes for it.
Why this error occurs?
In a simple manner, some of the effective reasons for the NewMailboxExportRequest is not recognized in Exchange Server are mentioned below:
- The user is using a shortcut for EMS rather than running it as an administrator
- Required permissions are unavailable with the account performing the execution
- Exchange Server requires an update
- Using Windows PowerShell in place of Exchange Management Shell
- Error(s) in spellings while writing commands
- Corruption in EDB files
- Compatibility issue with Windows System bit versions
Possible Solutions
1st Method – Assign the necessary role group
The MailboxExportRequest cmdlet is available to run in the on-premises Exchange Server only. It can export the content from primary mailbox and archive mailbox to a PST file. But, this cmdlet is active in Mailbox Import Export Role only. This role is not a member of any role group by default. If you are an Administrator, then you need to add the Mailbox Import Export Role in the Role Group.
- In the Exchange Admin Center, go to Permissions, then choose Admin Roles.
- Select the Role Group where you want to add the role and click Edit.
- In the Role section, choose Mailbox Import Export Role and save the changes.
- Save the Changes in the Admin Roles and come out of the wizard.
2nd Method – Use the proper parameters
If the cmdlet is stuck in the process due to problems in the source mailbox, then there are several parameters that can solve them. Some of the important parameters are-
- -AcceptLargeDataLoss: The parameter will allow the cmdlet to run even if a large number of items in the source mailbox can’t be copied. You do not need to input a number of items in the switch.
- -BadItemLimit: Bad Items Limit shows the corrupt items in the source mailbox that can’t be copied in the PST file. The parameter will set a number of bad items that are allowed before the request will fail. You can set the bad item limit and manage the faulty items in mailbox.
3rd Method
- One solution that you can try is choosing the ‘Run as Administrator’ by right clicking on EMS icon rather than using a shortcut for it. After that ensure that login credentials are also accurately written. EMS runs only with administrator rights with correct login credentials.
- Install SP1 and update Exchange if not done earlier as this is required to run the mailbox request command. Once updated, restart the EMS to see any difference.
- While writing the commands, check the credentials are accurate without any error in spellings. Domain Name has to be specified correctly within the command.
- The account should be given the ‘Import Export Mailbox’ role for the export request.
- Assign the permission with this command
Here provide the respective details like – domain, username, server, location, filename, etc. as per assigned to the account in the Exchange Server for all of the above commands.
The solutions which are explained above may solve the error or work if it is not much severe. Sometimes, Exchange Database files are heavily corrupted or damaged, or permissions have some issues, or there are compatibility problems. So EMS commands are always not sufficient enough to export Exchange EDB data to PST file. Also, it would be hard for a non-technical user to execute such technical, complex commands. Data loss would be an issue with minor carelessness. And importantly, only system administrators have the right to perform the execution of the EMS commands. Exchange administrators and users have option to perform the export of EDB mailboxes to Outlook PST file more conveniently and securely by adopting a perfect professional tool that additionally supports recovery of Exchange mailboxes along with its export to PST and more destinations including Office 365 directly. Follow the next section to get an introduction about such EDB recovery tool.
Better Alternative Solution
To export the Exchange mailboxes to PST, use a professional, third-party Exchange Recovery tool for errorless both EDB recovery and migration. The tool is incorporated with the innovative features and friendly user-interface allowing exporting each file item of Exchange mailbox data to Outlook PST file. One can perform bulk mailboxes migration and even choose data for export via filters. The tool extensively supports all Exchange Server and Outlook versions. It would be best if user visit the software website to know about this tool in detail.
Conclusion
The discussion has been made over the error – NewMailboxExportRequest not recognized in Exchange Server, its causes and solutions. In the end, it has been experienced that the ultimate quick and easy solution to fix this error is using a third-party tool for the export of Exchange mailbox files to Outlook and more destinations flawlessly.
Comments
I am trying to export my mailbox with other employees and then this error occurs, to handle this problem I used this blogs methods. It becomes helpful and I am able to access my EDB mailbox with Exchange server.
