New Mailbox Export Request Returns Access Denied

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.

4 responses to “New Mailbox Export Request Returns Access Denied”

  1. […] must grant MYEXSERV at least Read+Write/Modify permissions to \servernamesharename. See New Mailbox Export Request Returns Access Denied. Reply With […]

  2. Greg says:

    Thank you sir.

  3. James says:


Leave a Reply

Your email address will not be published. Required fields are marked *