Newly installed Exchange 2010 server says Export-Mailbox not recognized??
Some syntax has changed, but this throws me for a loop. Some "special" incantation I need to use to get EMS working corrently? [PS] C:\Windows\system32>export-mailbox The term 'export-mailbox' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.SnoBoy
May 19th, 2010 12:57am

You need to add the mailbox import export role as described here: http://technet.microsoft.com/en-us/library/ee633452.aspx Oh, and slaughter a chicken at midnight. Tony
Free Windows Admin Tool Kit Click here and download it now
May 19th, 2010 1:10am

You need to add the mailbox import export role as described here: http://technet.microsoft.com/en-us/library/ee633452.aspx Oh, and slaughter a chicken at midnight. Tony Hi, As Tony said, you must have the correct permissions to import or export mailbox data. Would you please let me know what’s data you want to export? To export data from a .pst file, you must run the Export-Mailbox cmdlet against a 64-bit computer that has the following installed: Microsoft Exchange Server 2010 role 64-bit Microsoft Outlook 2010 More information: http://technet.microsoft.com/en-us/library/ee633478.aspx Please run the cmdlet in Exchange Management Shell. Thanks, RichardYour expertise never fails to impress :)
May 19th, 2010 5:07am

OK, a comment - this is insane! Why tell an admin that the command doesn't exist, instead of your don't have permission to use the command. This is the kind of nonsense that drives administrators crazy! That said, I was merely trying to export a mailbox to a PST. Lots of fun trying to get the cert request done too - changed the syntax and removed several command line parameters versus EX 2007. The notes I kept on 2007 are a pile of poop now! SnoBoy
Free Windows Admin Tool Kit Click here and download it now
May 19th, 2010 6:11pm

And another thing I discovered - if you have your CAS and Mailbox roles on the same server, Export-Mailbox fails! This is a known bug, to be fixed either in Rollup 5 or in SP1, until then you have to set up a separate CAS server or use Outlook to export email. Credit: http://msundis.wordpress.com/ SnoBoy
May 27th, 2010 12:26am

This is just dumb - 64-bit Microsoft Outlook 2010 installed at the server??? I might as well just attach to the mailbox and use GUI Outlook to export. I grow more unhappy with Exchange 2010 each day I work with it.
Free Windows Admin Tool Kit Click here and download it now
May 4th, 2011 5:53pm

SP1 solved this issue, i.e. no more need for Outlook to be installed on the box, however, SP1 also changed all the commands and there is no reference to the original commands, i.e. you just get a stupid error about the command not working. if you are interested in looking at a 3rd party product that can export from live as well as offline Exchange Databases, check out Lucid8's DigiScope http://www.lucid8.com/product/digiscope.aspTroy Werelius www.Lucid8.com
May 4th, 2011 5:57pm

I actually found this thread because I'm trying to export a mailbox to a PST and I'm using SP1. Even after setting up the roles I still can't find the export-mailbox cmdlet. If it's renamed, the new name would certianly be handy to know. EDIT: New-MailboxExportRequest so it would seem.
Free Windows Admin Tool Kit Click here and download it now
May 4th, 2011 6:01pm

Oh yeah that would be handy eh? Its too bad they didn't take the time to cross reference the old commands into the new ones, it certainly wouldn't have been that hard to do as part of the SP. Anyway, here you go The new command is New-MailboxExportRequest http://technet.microsoft.com/en-us/library/ff607299.aspx I would also suggest that you apply at least up to SP1 RU2 RU3 is good as well but if you are using BES there are additional patches to consider Troy Werelius www.Lucid8.com
May 4th, 2011 6:14pm

Thanks for that. I've successfully done my first export. It only took 3 1/2 hours from start to finish. About 10 minutes for the actual export. The rest of the time was spent hunting down a plethora of wrong command line information. Add in a few minutes for troubleshooting why it wouldn't write to a NetApp CIFS share that as the user performing the export could write too and it's been FUN! (no).
Free Windows Admin Tool Kit Click here and download it now
May 4th, 2011 6:50pm

Happy to assist and sorry you had to chase the wrong path, very aggravating I am sureTroy Werelius www.Lucid8.com
May 4th, 2011 7:04pm

My sugestions for doing an export: new-mailboxexportrequest -mailbox ? -filepath \\server\c$\pst\?.pst Note: You must use a UNC and not a drive letter, even when you are runningit on the server itself. get-mailboxexportrequest |FL This is to find out the name of the Identity for the command below and it is the easiest way to find out if it is completed or not - keep running it until it says completed Remove-MailboxExportRequest -identity "what you found above" I have found the the "statistics" command is so picky, that I just let the job run for a while and use the get-mailboxexportrequest | fl command to see when it says "Completed."SnoBoy
Free Windows Admin Tool Kit Click here and download it now
May 5th, 2011 9:46am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics