New-MailboxExportRequest is Not Recognized in Exchange Server 2016, 2013, 2010
Before making prejudgments regarding the error, it is first required to improve the concepts of New-MailboxExportRequest error statement and the probable reasons behind this error. The post mainly explains methods to fix the problem the term New-MailboxExportRequest is Not Recognized as the name of a cmdlet in Exchange Server 2016, 2013, 2010
Microsoft Exchange 2010 and 2013 use the EMS (Exchange Management Shell) commands that easily migrate EDB mailboxes to PST format. EMS command is a quite helpful approach for carrying out import, export procedure and many other tasks executed in Exchange Server. This PowerShell method requires deep technical expertise, but still, most users go for this approach.
However, many times EMS commands fail to achieve their objectives. For example, let us consider a case of “New-MailboxExportRequest”. Admins have complained that while performing import-export operations with NewMailboxExportRequest, often times it displays an error message stating the term New-MailboxExportRequest is Not Recognized in Exchange Server 2010, 2013, 2016. But, there are several reasons behind this issue and it can also be fixed with many possible solutions.
An Overview on Error Statement: New-MailboxExportRequest Is Not Recognized as the Name of a Cmdlet
This cmdlet is used to export primary mailbox to PST file format. The command basically generates a mailbox export request. Then, more commands are added to convert into PST format.
This command is utilized to generate multiple mailbox export requests per mailbox, and here each request should possess a unique name. Moreover, appropriate permissions are needed to execute this cmdlet.
Probable Reasons Behind New-MailboxExportRequest Is Not Recognized In Exchange Server 2013, 2010, 2016 Error
The most prominent reasons for the login server the term are mentioned here:
- The Exchange Server demands an update
- A user is not running EMS as an administrator
- The account which is performing the export request is not granted the required permissions
Depending on the cause, users can choose an appropriate solution explained in the next section.
As discussed there are multiple problems that a user might face while using New-MailboxExportRequest Error. Thus, to overcome all such problems, it will be beneficial if you go for SyTools EDB to PST Converter tool that easily bulk export mailbox to PST Exchange 2010 & various other versions with no data loss.
User can use this utility and extract mailbox from EDB file Exchange 2016, 2013 to Outlook PST and other file formats.
Solutions to Fix the Login Error in the Exchange Server
Users can take the following measures to perform an export operation using the Exchange Server cmdlet:
- Install SP1 to update the Exchange Server. It is essential to execute New-MailboxExportRequest. Once the Exchange Server has been updated, start EMS again to check if the command is working now. If it is not, go to the next fixing strategy.
- Run EMS as an administrator. This can be done by right-clicking on its icon and selecting an option of Run as Administrator. Also, be careful that a user is logged in with the required admin credentials. If EMS runs through its shortcuts or actual itself, much of the commands are disabled. It is because of security reasons.
- The account commencing the export request is required to grant “Import Export Mailbox” role. The role can be granted using the following command:
New-ManagementRoleAssignment –Role “Mailbox Import Export” –User “DOMAIN\USER”
Once the permission is granted, the EMS session can be restarted and try to execute the export request.
What are the Drawbacks Associated With EMS Commands?
Although EMS commands are sufficient to import or export the EDB mailboxes or perform any other task, there are some shortcomings. It may fail to complete tasks in many scenarios. It occurs due to the following reasons:
- Compatibility issue may arise (32-bit and 64-bit)
- The EDB file can be damaged, offline, dismounted or corrupted
- Permission issues can create a hindrance
Other than the technical issues, the EMS commands demand a good technical knowledge. The mistake committed at any stage can lead to loss of data. Even though such tasks are performed by the system administrators. Admins are knowledgeable enough, but they can still face errors which are ahead of their understandings.
Alternative Solution to Opt :
To conquer all the limitations stated above when New-MailboxExportRequest is not recognized, professionals recommend to use a simple but smart utility called EDB to PST converter. This is an automated tool that ensures all the data from EDB files is converted. More than one .edb file can be exported to Outlook PST format. The resultant PST formed is UNICODE PST.
Moreover, users are equipped to selectively export EDB file to PST by applying necessary filters. If any file is corrupted or damaged then this software provides Quick and Advance scan mode option that automatically recover as well as repair EDB file & mailboxes from corruption with no loss of data.
It is clear from the write-up that insufficient permissions and missed updates can interrupt in the export procedure of EDB mailboxes. So, users should make sure that all the prerequisites are ready. Various measures are explained in the write-up to transfer EDB mailboxes to PST. If these manual measures fail and the term New-MailboxExportRequest is not recognized, users can use a third-party tool like EDB to PST converter. It offers an interactive graphical user interface, making it easy for users to work on it.