Posted by on April 12, 2012

The New-MailboxExportRequest (and New-MailboxImportRequest) cmdlet requires a UNC path for the FilePath parameter. In other words, you can’t use “New-MailboxExportRequest -Mailbox MailboxName -FilePath C:\output.pst”. You have to use “New-MailboxExportRequest -Mailbox MailboxName -FilePath \\servername\sharename\output.pst”. However, if the share and NTFS permissions aren’t set correctly on the destination path, you could get an error like this one.

[PS] C:\Windows\system32>New-MailboxExportRequest -Mailbox MailboxName -FilePath \\servername\sharename\output.pst
Unable to open PST file ‘\\servername\sharename\output.pst’. Error details: Access to the path ‘\\servername\sharename\output.pst’ is denied.
+ CategoryInfo : NotSpecified: (0:Int32) [New-MailboxExportRequest], RemotePermanentException
+ FullyQualifiedErrorId : D7BD75A8,Microsoft.Exchange.Management.RecipientTasks.NewMailboxExportRequest

The problem is that the New-MailboxExportRequest and New-MailboxImportRequest cmdlets don’t run in the user context, but in the machine context. You need to give the Exchange server access to the shared drive. So if you are running the cmdlet on ExServer01, add ExServer01 to the share and NTFS permissions for \\servername\sharename so it can read and write data.


  1. anon
    November 28, 2012

    Leave a Reply


  2. Greg
    November 19, 2013

    Leave a Reply

    Thank you sir.

  3. James
    February 1, 2017

    Leave a Reply


  1. Exchange 2010, exporting mailboxes to .pst. - [...] must grant MYEXSERV at least Read+Write/Modify permissions to \servernamesharename. See New Mailbox Export Request Returns Access Denied.…

Leave a Reply

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>