Read time 5 minutes

Summary: Exchange Server administrators can export mailboxes to PST files for data preservation. This process can encounter errors, such as “Couldn’t find the Enterprise Organization container,” when the Mailbox Import Export Role is not assigned. This role can be assigned through Exchange Admin Center or Exchange Management Shell. If issues persist, Kernel for Exchange Server offers a reliable solution for data recovery and migration. Ensuring the correct assignment of the Mailbox Import Export role is crucial for successful mailbox exports.

Within an Exchange Server configuration, administrators have the capability to establish multiple databases to house and manage mailboxes. These mailboxes operate in accordance with various rules and permissions granted by the Exchange environment, which includes robust security measures to safeguard their content within the database. However, the integrity of the database can be compromised due to factors such as hardware failures, network issues, or user errors. Therefore, an integrated manual process is available to facilitate the direct export of mailboxes to a PST (Personal Storage Table) file. This method ensures data preservation and recovery in the face of potential database corruption.

Exchange Server mailboxes can be exported to Outlook PST file in two different ways – using Exchange Admin Center or using Exchange Management Shell.

Note: Users must have export permissions to perform Exchange mailbox export to a PST file.

While using the Exchange Admin Center, go to recipients>mailboxes, and then select a single (or more than one) mailbox for the export. Then, click on the 3 dots and select the option Export to a PST file option from the drop-down list.

Note: The PST saving folder should be a network shared folder.

This export operation can also be performed by running a New-MailboxExportRequest cmdlet in the Exchange Management Shell. The command syntax is as below:

New-MailboxExportRequest -Mailbox <username> -FilePath <PST File Path>

The main requirements in the above command are the mailbox username and the network shared PST folder path.

But, both the processes of exporting Exchange mailboxes to PST files often experience a hurdle in the form of an error. Instead of initiating the export process, the Export option in the Exchange Admin Center or the New-MailboxExportRequest command throws this error-

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

This error can be encountered in any of the Exchange Server version and must be resolved to continue with the mailboxes export process.

Troubleshooting the Error

The error indicates that it “Couldn’t find the Enterprise Organization container.” This error can be analyzed in detail by visiting its Event ID. Exchange experts have found out that the main cause behind the occurrence of this error is that the Mailbox Import Export Role is not assigned to the user. It is a built-in role in the Role Based Access Control permissions. This Mailbox Import Export Role is the Management role provided by Exchange Server to allow the Exchange administrators to import/export Exchange mailboxes. With this, Read/Write permissions are provided to the Exchange administrator for the export of concerned mailboxes to complete the procedure.

Assigning Mailbox Import Export Role

The Mailbox Import Export role can be assigned through the Exchange Admin Center interface as well as the Exchange Management Shell.

  • Through Exchange Admin Center
    1. Login to your Exchange Admin Center using the administrator credentials.
    2. Navigate to permissions>Organization Management.
    3. Now, go to the Roles section, click the plus icon and select Mailbox Import Export option and then under Members section, add the account.
    4. Finally, click on OK to complete the Role assignment.
  • Through Exchange Management Shell
    Go to your Exchange system and run the Exchange Management Shell as an administrator. To assign the Mailbox Import Export Role, execute this command as follows.

    New-ManagementRoleAssignment -Name “name” -SecurityGroup “security_group_name” -Role “Mailbox Import Export

    Provide the bolded information in the above command as per your Exchange Server account.

    After assigning the Mailbox Import Export, it is recommended to export mailboxes command or perform the export process through the EAC.

The Best Solution for Fixing Exchange Errors

If you find that you’re still not achieving the expected outcomes despite having assigned the Mailbox Import Export Role and initiating the Export process, it becomes apparent that a professional solution is required to address the Exchange error and successfully export the Exchange mailboxes to a PST file.

Kernel for Exchange Server offers a comprehensive Exchange recovery solution designed to effortlessly retrieve data from Exchange EDB mailboxes. This versatile software empowers users to securely save their recovered EDB mailboxes in various destinations, including live Exchange, Microsoft 365, and Outlook PST file format. Notably, it extends its functionality beyond standard mailboxes, enabling the export of public folders, shared mailboxes, and archived mailboxes from Exchange database files. This software boasts compatibility with all Exchange Server versions, efficiently resolves a wide array of errors, and facilitates smooth EDB data export to PST or any preferred destination. Opting for this Exchange conversion tool ensures a seamless and hassle-free export of your Exchange Server mailboxes, making it a prudent choice for administrators seeking reliable data recovery and migration solutions.

Summing Up

Exporting Exchange mailboxes to PST files is a crucial administrative strategy for safeguarding Exchange data. However, this process can encounter issues when the Mailbox Import Export role is not properly assigned to the Exchange account, leading to frustrating errors. To address this issue, it is imperative to ensure the correct assignment of the Mailbox Import Export role.

Kernel for Exchange Server