One of my colleagues hit me up the other day when he ran into a problem trying to export a mailbox to a .pst file using the New-MailboxExportRequest cmdlet. The *-MailboxExportRequest cmdlets are new in Exchange 2010 SP1, and there is a great article over here on Steve Goodman’s blog if you need more details on how the import/export process works in SP1. Anyway, my colleague was receiving the following error when trying to perform a mailbox export from the shell:

Couldn’t find the Enterprise Organization container.
+ CategoryInfo : NotSpecified: (0:Int32) [New-MailboxExportRequest], OrgContainerNotFoundException
+ FullyQualifiedErrorId : AB0EB1E4,Microsoft.Exchange.Management.RecipientTasks.NewMailboxExportRequest

After a quick Google search I didn’t find anything relating to this error and mailbox export requests, so I went to my lab to see if I could reproduce the problem. As it turns out, this is one of those misleading errors that can possibly send you down the wrong troubleshooting path. The problem is actually related to a lack of permissions on the shared folder being used as the target for the .pst file. To solve the issue, ensure you have:

  1. NTFS Permissions. Make sure the Exchange Trusted Subsystem group has at least read and write capabilities on the share being used as the target for the .pst file.
  2. Share Permissions. Of course, you need share permissions as well. Make sure that Exchange Trusted Subsystem group has at least read and change share permissions.

For example, the bare minimum NTFS and Share permissions permissions for the “data” folder are shown below:

Once the permissions are set, you should have no problems exporting a .pst to the share.