We recommend that you run the command on a dedicated Exchange server that doesn't have any mailboxes." pst file, you must run the Export-Mailbox cmdlet against an Exchange server that has the 64-bit version of Microsoft Outlook 2010 installed. pst file, the 64-bit version of Outlook 2010 or later must be installed on the server to which you are connecting ()."įollowing that error I looked up the Export-Mailbox TechNet documentation, and found this:
I changed my mind as soon as I saw the error export-mailbox returned on Exchange 2010: Having written an article on setting up these cmdlets in Exchange 2007, I was uncertain if there would be any need to revisit this topic. Replacing ExMerge by Import-Mailbox and Export-Mailbox It Started with an Error! In the past we dedicated three articles discussing the setup requirements in different scenarios: This was the intricate procedure in getting the functionality to work. Most notably it brought Unicode support and the ability to have PSTs larger than 2GB.ĭespite the advancements, the Exchange 2007 cmdlets still shared a common characteristic with ExMerge. Exchange 2007 SP1, apart for filling this void, also addressed some major ExMerge limitations. ExMerge, the tool of choice in Exchange 2003 and earlier, was on its way out making space for the new export-mailbox and import-mailbox cmdlets. From ExMerge to Import-Mailbox/Export-Mailboxĭo you remember the time when Exchange 2007 was released and Service Pack 1 was not yet available? In those days, many were angry for not having a supported method to export/import mailboxes to/from PSTs. Nevertheless, the occasional need to transfer mailbox content to/from PSTs is unlikely to go away completely. This is likely to cause a decline in demand for brick level backups.
Exchange 2010 made significant advancements in providing out-of-the-box Archiving, together with improved High Availability and Resilience functionality.
0 kommentar(er)
