Solved

Exchange 2010 PST export with PowerShell

Posted on 2014-04-14
12
1,021 Views
Last Modified: 2014-04-17
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
0
Comment
Question by:Missoulait
  • 5
  • 3
  • 2
  • +1
12 Comments
 
LVL 34

Expert Comment

by:Seth Simmons
Comment Utility
does your account have write rights to that folder both at the share and ntfs level?
0
 
LVL 35

Expert Comment

by:Bembi
Comment Utility
What is to use ExMerge or ExFolder(newer version) to do it?
You need permissions of ourse to the mailboxes.
0
 
LVL 34

Expert Comment

by:Seth Simmons
Comment Utility
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
 
LVL 63

Assisted Solution

by:Simon Butler (Sembee)
Simon Butler (Sembee) earned 500 total points
Comment Utility
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
 

Author Comment

by:Missoulait
Comment Utility
I did set everyone to full control, set my specific user account to full control, etc...

Still getting the same error.  =(
0
Why spend so long doing email signature updates?

Do you spend loads of your time carrying out email signature updates? Not very interesting are they? Don’t let signature updates get you down. Let Exclaimer Cloud - Signatures for Office 365 make managing email signatures a breeze.

 
LVL 63

Assisted Solution

by:Simon Butler (Sembee)
Simon Butler (Sembee) earned 500 total points
Comment Utility
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
 

Author Comment

by:Missoulait
Comment Utility
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
 

Author Comment

by:Missoulait
Comment Utility
I see some audit failures.  I they possibly have some other security software?
Not sure what else it could be.
0
 
LVL 63

Accepted Solution

by:
Simon Butler (Sembee) earned 500 total points
Comment Utility
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
 

Author Comment

by:Missoulait
Comment Utility
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
 

Author Comment

by:Missoulait
Comment Utility
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

Featured Post

Find Ransomware Secrets With All-Source Analysis

Ransomware has become a major concern for organizations; its prevalence has grown due to past successes achieved by threat actors. While each ransomware variant is different, we’ve seen some common tactics and trends used among the authors of the malware.

Join & Write a Comment

Not sure what the best email signature size is? Are you worried about email signature image size? Follow this best practice guide.
Following basic email etiquette rules will help you write a professional email and achieve a good, lasting impression with your contacts.
how to add IIS SMTP to handle application/Scanner relays into office 365.
Get a first impression of how PRTG looks and learn how it works.   This video is a short introduction to PRTG, as an initial overview or as a quick start for new PRTG users.

771 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

11 Experts available now in Live!

Get 1:1 Help Now