New-mailboxexportrequest Exchange 2010 – Add Skills to Knowledge
The basic question that toggles one’s mind before reading the article is why would one need to perform it? So, users should go through the content properly to get the answer. There are occasions when an administrator wants to export Exchange 2010 mailbox to PST Outlook. The most popular comprises of migrating on-premise mailboxes to Exchange and then extract one or many mailboxes from database. It is a rare case, even many times one needs to export the saved data from an infected or corrupted EDB.
From the stanza mentioned above, users are clear with the need of conversion and why it becomes compulsory at times to perform. In the write up, users would get to know how to perform conversion of EDB data to PST format. The most important factor is that users will get to know the manual method i.e. New-mailboxexportrequest Exchange 2010 due to which, they can easily perform export Exchange 2010 mailbox to PST using PowerShell command. But if one is in a mood to go for expert solution, stick to the article for it.
MS Exchange Server 2010 introduced set of PowerShell cmdlets to fulfill the task i.e. New-mailboxexportrequest Exchange 2010. One more thing, PowerShell scripts are helpful in exporting and importing data. But, it has a drawback too. It cannot be performed in 64-bit machine. If the EDB files are corrupted, infected dismounted or disconnected, one can perform the same through EDB to PST converter in bulk but, independent from Exchange Server in both 32 bit as well as 64 bit system.
One can export mailbox to PST Exchange 2010 by following 4 steps mentioned below:
1. Give vital permissions and roles
The very first step one has to follow is to permit full rights to the user i.e., the one performing the New-mailboxexportrequest Exchange 2010. No account has the permission by default. Hence, one needs to configure them manually. In EMS, type the command mentioned below:
New-ManagementRoleAssignment –Role “Mailbox Import Export” –ABC Administrator
In command mentioned above, ABC is username. If one is logged in already with username, restart EMS session and one will be granted access to new cmdlets.
2. Create a Network Share that store exported PST files
There are many CAS in network and any network can process import mailbox request. Thus, one must ensure that path of target PST file is suitable. This path should be UNC not local. The best suited method is creating a new Network Shared folder and grant read/write permission to Exchange Trusted Subsystem group.
3. Export mailbox to PST Exchange 2010
Everything when properly configured, the PowerShell cmdlets New-mailboxexportrequest Exchange 2010 is executed.
To import user’s primary mailbox to Outlook PST follow the command
New-MailboxExportRequest –Mailbox <ABC> -FilePath <pstFilePath>
Here, ABC is the user name and one can change it accordingly.
<pstFilePath> refers to the imported PST file. The command does not generate any new directory, so make sure the path one is referring exists otherwise, the command will fail.
From the stanza mentioned above, users are clear with the need of conversion and why it becomes compulsory at times to perform. In the write up, users would get to know how to perform conversion of EDB data to PST format. The most important factor is that users will get to know the manual method i.e. New-mailboxexportrequest Exchange 2010 due to which, they can easily perform export Exchange 2010 mailbox to PST using PowerShell command. But if one is in a mood to go for expert solution, stick to the article for it.
New-mailboxexportrequest Exchange 2010
To move mailbox or archive data to Outlook PST file, one ought to create mailbox export request. Every request comprises of a unique name and one can set up to ten unique requests. At a time, only one request is executed. Outlook PST file are marked as in-use when request is executed. In addition to it, EMC i.e. Exchange Management Console runs cmdlets for the different Exchange tasks. EMC is not used to make a mailbox move request. One needs to switch to EMS i.e., Exchange Management Shell to perform the same.MS Exchange Server 2010 introduced set of PowerShell cmdlets to fulfill the task i.e. New-mailboxexportrequest Exchange 2010. One more thing, PowerShell scripts are helpful in exporting and importing data. But, it has a drawback too. It cannot be performed in 64-bit machine. If the EDB files are corrupted, infected dismounted or disconnected, one can perform the same through EDB to PST converter in bulk but, independent from Exchange Server in both 32 bit as well as 64 bit system.
Steps to Run New-mailboxexportrequest Exchange 2010
One can export mailbox to PST Exchange 2010 by following 4 steps mentioned below:
1. Give vital permissions and roles
The very first step one has to follow is to permit full rights to the user i.e., the one performing the New-mailboxexportrequest Exchange 2010. No account has the permission by default. Hence, one needs to configure them manually. In EMS, type the command mentioned below:
New-ManagementRoleAssignment –Role “Mailbox Import Export” –ABC Administrator
In command mentioned above, ABC is username. If one is logged in already with username, restart EMS session and one will be granted access to new cmdlets.
2. Create a Network Share that store exported PST files
There are many CAS in network and any network can process import mailbox request. Thus, one must ensure that path of target PST file is suitable. This path should be UNC not local. The best suited method is creating a new Network Shared folder and grant read/write permission to Exchange Trusted Subsystem group.
3. Export mailbox to PST Exchange 2010
Everything when properly configured, the PowerShell cmdlets New-mailboxexportrequest Exchange 2010 is executed.
To import user’s primary mailbox to Outlook PST follow the command
New-MailboxExportRequest –Mailbox <ABC> -FilePath <pstFilePath>
Here, ABC is the user name and one can change it accordingly.
<pstFilePath> refers to the imported PST file. The command does not generate any new directory, so make sure the path one is referring exists otherwise, the command will fail.
4. Preview and Clean up
In last step, the import process must be cleaned up. To check status of active export jobs, run the command mentioned below:
Get-MailboxExportRequest | Get-MailboxExportRequestStatistics
When mailbox export request is complete, to clean up, eliminate all assigned permissions.
Remove-ManagementRoleAssignment "Mailbox Import Export-<ABC >"
One should also remove the completed mailbox from the server.
Get-MailboxExportRequest | where {$_.status -eq "Completed"} | Remove-MailboxExportRequest
Recommended Solution:
From the above commands, one is clear that it is very difficult to perform New-mailboxexportrequest Exchange 2010 PowerShell cmdlet. If a single mistake happens, one can lose the entire data and face corruption of data. So, we suggest users to try our Exchange Recovery Software for the same.
Final Words
From the above article, one is clear regarding the necessity of export Exchange mailbox to PST. If one finds the above method difficult, he/she should go for an automated solution. So, one should try EDB to PST converter for the purpose which is the best alternative to New-mailboxexportrequest Exchange 2010. The tool can migrate the files easily without any hassle.
Comments
Post a Comment