These days, more and more people are using Outlook because of its extensive features. So, most people desire to move to Outlook. People who use Exchange might need to change their Exchange file to a PST file.
In this case, they can use the New-MailboxExportRequest command to send the Exchange 2016 Mailbox to PST format. However, there are situations when users might not know what the new-mailboxexportrequest cmdlet is.
So, it will say something like “New-MailboxExportRequest is not recognized in Exchange 2010, 2013, and 2016.” So, they need a way to resolve the error notice that shows up in Exchange Server. First, let’s learn what the PowerShell command does and how it works.
What does New-MailboxExportRequest do?
You can only use the New-MailboxExportRequest Powershell command on Exchange on-premises. People are using this cmdlet to start moving the main mailbox from Exchange to Outlook.
But you can only use this command in the Mailbox Import Export role. Also, the role is not automatically assigned to any role groups. So, those who wish to use the new-mailboxexportrequest Powershell command need to add the Mailbox Import Export role to the set of roles.
Why the New-MailboxExportRequest Failed Problem Happened
There could be a number of explanations for this problem. We talk about some of the most typical causes in this section:
- If the new version of MS Exchange Server isn’t installed yet
- The Exchange Management Shell doesn’t have admin rights.
- There may be problems with the Exchange Server database.
- The Exchange account doesn’t have the right authority to do the export request.
Make it right Not Recognized: New-MailboxExportRequest Manually Issue
There are a lot of manual approaches to fix this Exchange problem message. Here are some of them:
First, you need to upgrade the MS Exchange Server after installing the SP1 that is needed to conduct the new-mailboxexportrequest command.
You have to restart the Exchange Management Shell over and over again after updating the Exchange server. If you still see the problem notice, you should attempt the next technique to fix it.
Solution 2: If the problem is still there after you updated your Exchange Server, After that, instead of using the shortcut to open the Exchange Management Shell, you should right-click on the icon and run the PowerShell cmdlet as an administrator. After that, for security concerns, the EMS will automatically turn off some commands that are not executing or logged in as an administrator.
Solution 3: Giving users the import and export permission is another way to fix the New-MailboxExportRequest not functioning problem. People that have the right permissions can start the migration process by using the PowerShell command.
Users need to select the checkbox to give permission to read and write. They will definitely be able to fix the error message after that. The New-MailboxExportRequest didn’t work.
Problems with Manual Methods
You may export an Exchange Mailbox to an Outlook PST file with just the Exchange Management Shell commands. However, there are times when these Exchange export commands don’t work because of a number of different causes.
The manual solution requires a lot of technical knowledge because even the tiniest mistake might cause data to be lost forever.
So, most of the time, these tasks are done by system administrators who are very skilled and knowledgeable. But even they sometimes run across problems with Exchange Server that they don’t know how to fix.
An Alternative Way to Fix the New-MailboxExportRequest Not Recognized Problem
As was said in the section above, there are a lot of problems with the manual approaches during the conversion process. So, to fix the user’s problem, they can use a professional application like GainTools Exchange Export instead of the new-mailboxexportrequest for migrating.
Change data to PST format. With this commercial program, the whole conversion process is easy and dependable because users don’t have to deal with the New-MailboxExportRequest not working issue.
Because the program lets you move all of your Exchange mailbox data to Outlook without changing any of it. The app makes the whole migration process easy and quick because it can handle both bulk and selective migration.
To finish
The Powershell You can use the New-MailboxExportRequest cmdlet to copy the contents of an Exchange mailbox to a PST file. But sometimes these cmdlets don’t work and show an error message that says “New-MailboxExportRequest is not recognized as the name of the cmdlet.”
So, in this post, we’ve spoken about three approaches to fix this error message by hand. However, it does have some problems. So, we have also spoken about an easy way to transform an Exchange EDB file to PST format. This technique can get over the problems with doing things by hand.
- How to Fix the New-MailboxExportRequest Not Recognized Error
- they can use the New-MailboxExportRequest command to send the Exchange 2016 Mailbox to PST format. However, there are situations when users might not know what the new-mailboxexportrequest cmdlet is.
- edb to pst
