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
MissoulaitAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Seth SimmonsSr. Systems AdministratorCommented:
does your account have write rights to that folder both at the share and ntfs level?
0
BembiCEOCommented:
What is to use ExMerge or ExFolder(newer version) to do it?
You need permissions of ourse to the mailboxes.
0
Seth SimmonsSr. Systems AdministratorCommented:
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
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

Simon Butler (Sembee)ConsultantCommented:
I usually just set the permissions to everyone full control on both the share and NTFS, rather then trying to set specific permissions. Use a hidden share and it is usually fine.

Simon.
0
MissoulaitAuthor Commented:
I did set everyone to full control, set my specific user account to full control, etc...

Still getting the same error.  =(
0
Simon Butler (Sembee)ConsultantCommented:
To be clear - that is on both the share and the NTFS permissions?
Do you see anything logged on the source server when you do the export?

Simon.
0
MissoulaitAuthor Commented:
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.
0
MissoulaitAuthor Commented:
I see some audit failures.  I they possibly have some other security software?
Not sure what else it could be.
0
Simon Butler (Sembee)ConsultantCommented:
Try creating a share on the Exchange server itself and doing a test export there.
That should work - if that doesn't, then either you are making an error in the command, the permissions structure isn't default or something is blocking it.

Simon.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
MissoulaitAuthor Commented:
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.
0
MissoulaitAuthor Commented:
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.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.