- “ExMerge” no longer exists. As of 2007, this functionality has been integrated into Exchange’s Management Shell Cmdlet’s (available in SP1 and SP2).
- Cmdlets is NOT compatible with 64-bit servers ONLY 32-bit. I will describe a “work-around” I used in detail below.
- The CMD you will need to know and use is called: Export-Mailbox.
- One notable advantage of “Export-Mailbox” over “ExMerge” is it does NOT have issues exporting mailboxes over the 2GB PST limit.
- Export-Mailbox will include “Dumpster” data on Exchange 2007. On Exchange 2010 is does NOT…!
- Just like ExMerge, before you can use Export-Mailbox, you need the proper account rights.
- Local Administrator rights.
- Exchange Server Administrator Role on the target Exchange 2007 mailbox server.
- Full access to the mailboxes against which the import/export operation is run.
- It is quite cumbersome, but STILL possible to install Exmerge on a client machine and connect to Exchange 2007 remotely. A tutorial on this procedure is here: www.exchangeinbox.com/article.aspx?i=88
The work-around I followed to the 64-bit limitation was quite simple:
1. Because I could not export to PST but still had the ability to export to a mailboxes, we created a “dummy” mailbox and exported to this mailbox. For example, the below command will export ALL e-mail from the “firstname.lastname@example.org” identity to the “MyData” folder in the “DummyMailbox”.
Export-Mailbox -Identity email@example.com -TargetMailbox DummyMailbox -TargetFolder MyData
2. After we exported the data to a “DummyMailbox” we authenticated to the mailbox with Outlook.
3. Manually created a new “Local” Outlook Data File (PST file).
4. Manually copied over all e-mail from the Exchange “DummyMailbox” to the “Local” PST file.
Now, if you are working with a 32-bit Exchange server, this is the command you need to use to export the contents of a Exchange mailbox to a local PST file:
Export-Mailbox -Identity firstname.lastname@example.org -PSTFolderPath C:\PSTFiles\davnads.pst
Dav Nads the Exchange Guy.