asked on

Exchange 2010 PST export with PowerShell

Trying to do a simple Export on a newly acquired acquisition.

Trying to do a mass export of their users mailboxes when the time comes. AS a test I went on with our admin account.

Added the Role to my admin account with the:
New-ManagementRoleAssignment -Role "Mailbox Import Export" -<username>

I also went to the share located on another part of the network and added the Exchange Trusted Subsystem to have full control.

When I run the command to test an export I get this error stating perms aren't right:
Unable to open PST File '\\Server\path\etc\email.pst'. Error details: Access to the path '\\Server\path\etc\email.pst' is denied.

+ CategoryInfo : NotSpecified: (0:Int32) [New-MailboxExportRequest], RemotePermanentException
+ FullyQualifiedErrorId : DD5314F3,Microsoft.Exchange.Management.RecipientTasks.NewMailboxExportRequest

Anyone know what I am missing?

This is Exchange Server 2010
Microsoft Corporation
Version: 14.03.0181.006

Windows Server 2008 R2 Enterprise, SP1

Seth Simmons

does your account have write rights to that folder both at the share and ntfs level?

Bembi

What is to use ExMerge or ExFolder(newer version) to do it?
You need permissions of ourse to the mailboxes.

Seth Simmons

exmerge has a 2gb file limit
exfolders is a ported version of pfdavadmin and just isn't the right tool for this; wasn't designed for mailbox export but for managing message and folder items. with a lot of mailboxes it isn't practical.

besides, the export utility works - this is a straight-forward ACL issue on the destination share

SOLUTION

Simon Butler (Sembee)

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Missoulait

ASKER

I did set everyone to full control, set my specific user account to full control, etc...

Still getting the same error. =(

SOLUTION

Simon Butler (Sembee)

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Missoulait

ASKER

This was an administrative share. I just shared the folder and added the permissions to the share so its on there for that along with the NTFS permissions. Again same error.
This is strange.

Missoulait

ASKER

I see some audit failures. I they possibly have some other security software?
Not sure what else it could be.

ASKER CERTIFIED SOLUTION

Simon Butler (Sembee)

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Missoulait

ASKER

So come to find out it wasn't permissions blocking, or atleast that I can tell. Instead of using the absolute path, I used a DFS path. Same folder, same server just different way to attach to it? Is it possible I don't have permission to use that type of path from PowerShell?

Still unsure why using the namespace worked in the path rather than the servers name.
However I can export now and it is all working.

Thanks for the suggestions people, I feel this is environmental due to their set up.

Missoulait

ASKER

I've requested that this question be closed as follows:

Accepted answer: 0 points for Missoulait's comment #a40001958

for the following reason:

So come to find out it wasn't permissions blocking, or atleast that I can tell. Instead of using the absolute path, I used a DFS path. Same folder, same server just different way to attach to it? Is it possible I don't have permission to use that type of path from PowerShell?

Still unsure why using the namespace worked in the path rather than the servers name.
However I can export now and it is all working.

Thanks for the suggestions people, I feel this is environmental due to their set up.