We upgraded from Exchange 2000 to 2007. When staff left the company we used Exmerge to create a pst for long term retention and deleted the mailbox. Now with Exchange 2007 there is no ExMerge. I tried the script for Export-Mailbox after installing the 32 bit version on a desktop but that fails during execution. Just does not work Had to install additional software and create a log file path, MS technical articles fail to mention those requirements. Now we have over 150 not needed mailboxes still on out Exchange 2007 servers and have not been able to determine how to export or save then so we can delete the unused mailboxes off the servers. We don't want to spenf thousands of dollars for commercial archive programs that do so much more than we need. Does anyone know how to fix this problem that the Export-Mailbox fails wwhen running? The failure does NOT create an error message in the cmd prompt as before I had learned to create a log file path, it simply stops executing. I am logging in with the proper credentials. This is exceedingly frustrating but I won't rant on Microsoft's failure to provide a tool to save mailboxes after peo[;e leave a company

Well, you can still use Exmerge.That being said, are you saying that export-mailbox fails on every mailbox you try without any error message in the event logs or elsewhere in the migration logs ( Logging\MigrationLogs\) under the Exch dir?

Now with Exchange 2007 there is no ExMerge. Dave,That is a wrong perception. ExMerge is a 32 bit tool and can be used on the exchange server itself, if you are using exchange on a 32 bit version (which is not a supported configuration).If you have a 64 Bit exchange server, all you need to do is just install the management tools alone on a different machine (32 bit machine). From there, you will be able to execute ExMerge just as the way you used to.This should help you out.Let us know.- Nagesh

On Sat, 16-Jan-10 20:24:37 GMT, daveAdmin wrote:>We upgraded from Exchange 2000 to 2007. When staff left the company we used Exmerge to create a pst for long term retention and deleted the mailbox. Now with Exchange 2007 there is no ExMerge. I tried the script for Export-Mailbox after installing the 32 bit version on a desktop but that fails during execution. Just does not work Had to install additional software and create a log file path, MS technical articles fail to mention those requirements. Now we have over 150 not needed mailboxes still on out Exchange 2007 servers and have not been able to determine how to export or save then so we can delete the unused mailboxes off the servers. We don't want to spenf thousands of dollars for commercial archive programs that do so much more than we need. Does anyone know how to fix this problem that the Export-Mailbox fails wwhen running? The failure does NOT create an error message in the cmd prompt as before I had learned to create a log file path, it simply stops executing. I>am logging in with the proper credentials. This is exceedingly frustrating but I won't rant on Microsoft's failure to provide a tool to save mailboxes after peo[;e leave a company Does this registry key exist on the machine you're running theexport-mailbox cmdlet?HKEY_LOCAL_MACHINE\Software\Microsoft\Exchange\Exchange MigrationIf it does, does the account you're running with have full control onthat key?---Rich MatheisenMCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

On Sat, 16-Jan-10 21:16:19 GMT, AndyD_ wrote:>Well, you can still use Exmerge.That being said, are you saying that export-mailbox fails on every mailbox you try without any error message in the event logs or elsewhere in the migration logs ( Logging\MigrationLogs\) under the Exch dir? The first time I tried export-mailbox on a clean install virtualmachine running the 32-bit E2K7 admin tools it barfed. Once because ofthe missing migration directory and then, after creating thedirectory, it just blew up. From memory, it says something like"Powershell stopped working". That was becasue of a missing registrykey.I can see where it's frustrating to try something and have it utterlyfail to work through no fault of anyone but Microsoft. A bit ofgoogling was all it took to get it working but, then again, I'm notone to panic easily. :-)---Rich MatheisenMCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

On Sat, 16-Jan-10 21:16:19 GMT, AndyD_ wrote:>Well, you can still use Exmerge.That being said, are you saying that export-mailbox fails on every mailbox you try without any error message in the event logs or elsewhere in the migration logs ( Logging\MigrationLogs\) under the Exch dir? The first time I tried export-mailbox on a clean install virtualmachine running the 32-bit E2K7 admin tools it barfed. Once because ofthe missing migration directory and then, after creating thedirectory, it just blew up. From memory, it says something like"Powershell stopped working". That was becasue of a missing registrykey.I can see where it's frustrating to try something and have it utterlyfail to work through no fault of anyone but Microsoft. A bit ofgoogling was all it took to get it working but, then again, I'm notone to panic easily. :-)---Rich MatheisenMCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP The only time I have seen you panic is when the in between session snacks run out.

This post talks about using the requirements for using the Export-Mailbox cmdlet: http://msexchangeteam.com/archive/2006/11/28/431669.aspx

Hi,I am curious to know if the command Export-Mailbox creates any pst files as output or not? if yes than what is the size of the PST is it 265 KB or ?Export-Mailbox -Identity john@contoso.com -PSTFolderPath C:\PSTFiles\john.pstRequired permissionsAdd-MailboxPermission -Identity john -User Admin01 -AccessRights FullAccessHow to Export Mailbox Datahttp://technet.microsoft.com/en-us/library/bb266964(EXCHG.80).aspxOne more thing, your exchange server is running SP1 or SP2?Thanks, -GULAB