The term “New-MailboxExportRequest” is not recognized

I was recently attempting to run a mailbox export request to a PST file in Exchange 2010 Service Pack 3, on running the New-MailboxExportRequest cmdlet, I was presented with the following error message:

The term "New-MailboxExportRequest" is not recognized.

In order to resolve this issue I had to grant the account performing the export request the ‘Import Export Mailbox’ role assignment as below.

New-ManagementRoleAssignment –Role “Mailbox Import Export” –User "DOMAIN\USER"

Once I restarted my powershell session, I was able to succesfully run the New-MailboxExportRequest cmdlet.

Advertisements

12 thoughts on “The term “New-MailboxExportRequest” is not recognized

  1. Binh Tang July 22, 2014 / 04:25

    Thanks for that. Had the exact same problem trying to export a mailbox to .pst. I ran your command now it’s all working fine.

    Like

  2. Hemanth August 12, 2014 / 16:58

    Great work and thanks for elaborated step

    Like

  3. Test March 21, 2015 / 15:13

    Thanks for your great TIP

    Like

  4. Josh May 29, 2015 / 22:58

    Very helpful. Thanks!

    Like

  5. Schyler Jones December 16, 2015 / 00:58

    2+ years later and your post is still helping people! Thank you.

    Like

  6. Chris Conlan April 12, 2016 / 21:23

    This saved me big time when having to export old mailboxes to PST’s when our Exchange server went down.

    Like

  7. Jonathan May 20, 2016 / 18:29

    This is very helpful, but I’m looking for a slightly different version. Can New-ExportMailboxRequest be used to export data to a CSV file? Or only PST? I’m trying to export the Contacts folder for all of the users on one small Exchange 2010 SP3 server to CSV files (preferably each user would have their own file, but it could work in one file as long as the output was tagged so I know whose mailbox they came from).

    Thanks,

    Like

  8. Ryan O'Malley December 7, 2016 / 23:15

    I had been searching everywhere to get this solved, and couldn’t find anything. This ended up being the fix. Thank you!

    Like

  9. Govind Verma February 27, 2017 / 19:38

    Very helpful….Just restarted Powershell. Problem Resolved

    Like

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s