The article all focuses on how to tackle or deal with the error that comes while transporting Exchange mailboxes to PST file using New-MailboxExportRequest command.
It suggests the user some easy ways to cope up the situation. At the end of it, the user will get the required solutions for the error observed during execution of Exchange Management Shell (EMS) commands.
What is the error?
The error that we are going to discuss basically in words is 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. Likewise, Microsoft Exchange Server 2010 and Exchange Server 2013 utilize the Exchange Management Shell commands to migrate Exchange mailboxes to PST format. The EMS command that is being used by 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 Exchange Management Shell commands certainly requires technical knowledge for execution but are useful in exporting EDB data to PST. But there are situations when this exporting fails and mailbox-request becomes failed and unable to export Exchange mailboxes to PST. And, in turn the user received the error message 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 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 requires an update
- Error(s) in spellings while writing commands
- Corruption in EDB files
- One solution that you can try is going for 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 mailbox request command. Once updated, restart the EMS to see any difference.
- While writing 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 New-ManagementRoleAssignment –Role “Mailbox Import Export” –User <domain >\ <username >
- Now run the export cmdlet, save to local path in this cmdlet
New-MailboxExportRequest <username> -Filepath \\<server>\location\<filename>.pst
- Look at the .pst export progress
Get-MailboxExportRequest | Get-MailboxExportRequestStatistics
- Once export reaches to 100%, remove pst move request from the queue
Get-MailboxExportRequest | Remove-MailboxExportRequest
Here provide respective details like – domain, username, server, location, filename, etc. as per assigned to the account in Exchange Server.
The solutions that 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, 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. Only system administrators have the right to perform the execution of the EMS commands.
Better Alternative Solution
To export Exchange mailboxes to PST, use a professional, third-party Exchange Recovery tool for errorless EDB recovery and migration. The tool is incorporated with innovative features with friendly user-interface allowing exporting each file item of Exchange mailbox data to Outlook PST file.
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 is using a third-party Exchange Recovery tool for export of Exchange mailbox files Outlook.