I have looked at all the similar posts to the issue and non have helped me with my issue. I was able to export the mailbox while the user (me!) was on the Exchange 2007 mailbox before moving and it worked fine. Running command: export-mailbox "username" -baditemlimit 100 -pstfolderpath c:\pst\username.pst Error was found for User(user@domain.edu) because: Error occurred in the step: Approving object. An unknown e rror has occurred., error code: -2147221219 + CategoryInfo : InvalidOperation: (0:Int32) [Export-Mailbox], RecipientTaskException + FullyQualifiedErrorId : BF19A92E,Microsoft.Exchange.Management.RecipientTasks.ExportMailbox I have tried fixmapi - no help. I have logged into the server with several different accounts, including the one I was trying to export (my own account and I am an Exchange Admin). I have Outlook 2010 x64 installed onthe server, lack of that was a common problem cited. What else is there to check?SnoBoy

Are your trying to Import or Export on the Exchange 2010? Do you have both CAS and Mailbox roles on this server? If so, this can be cused by a known bug. I have blogged about this so you can find more information here: http://msundis.wordpress.com/2010/05/25/error-when-doing-export-mailbox-and-import-mailbox-in-exchange-server-2010/ In short, you need to do the exports on a server without the CAS role installed. Martin Sundström | Microsoft Certified Trainer | MCITP: Enterprise Messaging Administrator | http://msundis.wordpress.com

Yep, sure do! Good to know that it is a known bug, bad that it hasn't been more widely publicised. THis is going to delay my rollout - I have to export a lot of email when users leave and I hate the speed issues in using Outlook to export.SnoBoy

Yes its annoying when you hit a show-stopper like that in the middle of a project. Is it possible for you to set up a temporary Exchange Mailbox server and do the import/export there? This could be a low performance virtual machine for example.Martin Sundstrm | Microsoft Certified Trainer | MCITP: Enterprise Messaging Administrator | http://msundis.wordpress.com

The other big hang up we ran into is that apparently DPM 2007 cannot fully backup Exchange 2010, and rolling out DPM 2010 is a huge undertaking. We bought "appliance" solutions with Windows 2003 Storage and DPM 2007 rolled into a package. DPM 2010 requires Windows 2008 so it isn't going to be easy and quick to get the updates done to support Exchange 2010. So, while I could get another license and set up another virtual machine, we have the backup show stopper too. My current motto in rolling out things from Microsoft is, "It is never anywhere near easy to roll it out." Sigh! SnoBoy

The "problem" with implementing new products that has been changed a lot. But i hope that in the end, you will think that the improvements and new functionality compensates for the larger rollout process... Martin Sundstrm | Microsoft Certified Trainer | MCITP: Enterprise Messaging Administrator | http://msundis.wordpress.com

I really appreciate your help on this. I am adding your Blog to my list of resources for Exchange. Now I have the fun of setting up Forefront Client Security. This won't be simple either. :DSnoBoy

Im just glad I can help and thanks for reading the blog! Good luck with the implementations, you seem to have your hands full!Martin Sundstrm | Microsoft Certified Trainer | MCITP: Enterprise Messaging Administrator | http://msundis.wordpress.com