Introduction – Why We need to Export Exchange Mailbox to PST?
Today Exchange Environment helps Big as well as Small Organization to manage their messaging, Communication between Internal and External Domain designed by Microsoft. Since Exchange Server offers various features along with messaging, Telephone connectivity with storage and security on different platforms such as Desktop, Web-Based, Smart-Phones, Tabs, which installed on Windows Servers.
But When a user needs to Export these mailboxes items from Exchange Environment then, the user faces some issue that can be discussed in below section thoroughly. As Exchange Environment offers an Export / Import Wizard to move mailboxes via Powerful Power-shell command and Exchange Admin Center but sometimes using these commands and graphical interface, the user still not able to export Exchange mailboxes to PST Format, offered by Exchange to move mailbox items out of the environment.
Error While Converting Exchange Mailboxes to PST File Format
In below section, we discussed, some common error deal by Exchange User’s
1) Export Mailbox Command Not Recognized: The root cause of this Powershell Command error is:
a) Incorrect Path of Source Mailbox, from where a user needs to save the resulted file.
b) No Export-Import Permission granted to Administrator to Export Exchange mailboxes to PST format via Power Shell.
c) The wrong path of the Destination Folder.
2) Export Mailbox MAPI Error Or Unspecified Service Provider in Exchange: In this error user deal with, a prompt message “Export Mailbox MAPI Error Or Unspecified Service Provider” or Error Code: 1056749164″ “or ID no: 00000000-0000-00000000″ or error Code=”0xc1054005″, Event ID: 1008”. The root cause of this Command error is:
3) Mailbox Export Request Stuck Queued: Sometimes after running the Power-shell export command, Exchange user needs to wait for a long time due to “mailbox export request stuck in queued” error and mailbox items do not move from Source mailbox Folder to Destination folder of PST file.
4) Exchange Export Access to the Path is Denied: While using Command “[PS] C :\> New-MailboxExportRequest “userabc” -FilePath “\\MYSERVER\PST\userabc.pst <file://MYSERVER/PST/userabc.pst>” to export Exchange mailboxes to PST, a prompt appear with the message “+ CategoryInfo : NotSpecified: (:) [New-MailboxExportRequest], RemotePermanentException”. This error can arise either due to file path issue or parameter used with the export Command such as [-BadItemLimit], [-IncludeFolders <String>], [-Exclude Folders <String>], [-ContentFilter ] etc.
To avoid above all mentioned error regarding moving Exchange mailboxes to PST File format, either naive user can go for the manual approaches that can lead to sometimes corruption or data-loss or go for the Automated solution offered by SysTools discussed in below section.
Alternative Solution to Export Exchange Mailboxes to PST Format Without Error
As we observe from above section that different errors either related to Power shell Syntax Command or during exporting mailbox items to PST form Exchange environment faced by Exchange naive as well as Expert Administrator.
To avoid all these kind of issue, try an alternative solution offers by SysTools, Exchange Export Tool. A Graphical and User-friendly software that can move mailbox items such as email files, user contacts details, Calendar items, and other task, journal details of Exchange 2016, 2013, 2010, 2007 and below version perfectly without any data-loss and Power shell Commands. Some remarkable features of the utility are given below:
1. Option to Manage Folder Structure or Hierarchy of User Mailboxes
2. Export Mailbox Items such as Task, Journal, Contacts, Calendar, and Mails to PST Format
3. Search Sub-Domain User Created in Exchange Environment
4. Use Date Filter to Export only selected Desired Date-Range Items
5. Split Resulted in PST File to avoid file size issues.
6. Preview Mailbox Name List stored in Exchange Environment and Permission Before Migration Process
Steps to Export Exchange Mailbox To PST Format Without Error
1. First Download Utility From Below Link:
2. Now Launch and Open Software to start the process of Exchange Migration.
3. Now to Access the Desired Exchange Environment, you need to provide the credentials details such as:
a. Admin SMTP Address & Password
b. Active Directory IP & Exchange Server IP,
c. Include Sub-Domain User, Exchange Server Version (2016, 2013, 2010, 2007, 2003)
4. Now Software verifies the Credentials first, after that, you can preview the details of Exchange such as Mailboxes Name and Permission details. Now Check the User Mailboxes in utility to start the process of Exporting mailboxes to PST Format from Exchange 2016, 2013, 2010, 2007 and below vers
5. Now Software displays Preview panel, from where naive as well as Administrator user can select the Mailbox Items such as Mails, Contacts, Calendar, Tasks and Journal Section to save in a .pst file.
6. Select either Complete Mailbox via Radio Button or use Date Filter to select, where you need to provide a range of Date to export only the items of selected dates into a .pst file format.
7. Similarly, use Date Filter for another section to continue the Export process.
8. Now if you want to maintain the “Folder Hierarchy” between the Exchange mailboxes and resulted in PST File, Check the option “Maintain Folder Hierarchy” and if the user wants to save the resulted PST File in multiple PST File, then check option “Split options, for Outlook Data File”.
9. Now Browse the location to save the resulted PST File within the system and view the Live Progress Report of exporting Exchange mailboxes to PST File format.
10. Now, use the resulted PST File as a Backup file or send this file to other users to use. Import the file into Outlook Application via Import / Export Wizard to view the Exchange user mailboxes in the application.
In Exchange Environment, the user’s can Export exchange mailbox items to PST format or vice versa via Power-shell Command and Exchange Management Console, but sometimes user deals with the different kind of export issues such as export-mailbox command not recognized, access Path is Denied, request stuck queued, MAPI errors. Either Exchange user tries the manual approaches to fix the issues or uses an automated solution offered by SysTools Exchange Exporter to directly migrate mailbox items from exchange environment 2016, 2013, 2010 and below versions of Outlook PST file format without data-loss.