PST Migration

[FLX]

I know that in Microsoft best practise PST-Files should not be on Network Shares...but in practise we never had really issues with that. Client-Driven Migration should work now with files from shares

Tech Note has been changed now.

https://www.veritas.com/support/en_US/article.TECH68805

https://www.veritas.com/support/en_US/article.v13133852_v89941664

It should be possible now, my VSA and User has full control to the share, and my VSA is also in Administrative group of the Shareserver. Firewall is not active.

But in Outlook 2013 Import PST Process I receive the error message "pst file is either write protected or access denied"

Does anybody have an idea? thanks in advance

[GertjanA]

Hello,

I have not tried, but you might want to check:

The article you mention specifies tthat VSA needs to have full access to the Administrative share, not the Share itself. As example (I think...) The share is \\fileserver\PSTs, the actual location is on the fileserver, E-drive\PSTs. Verify you can access \\fileserver\E$ with the VSA

If granting that level of access is not an option, then make sure those pors mentioned (139 and 445) are open.

Furthermore, create an Outlook profile for the VSA, open Outlook, and see if you can open the offending PST. If that works, verify the user can open the same PST. Then check again.

If that fails, you can trace the EVClient on the workstation to see what is happening.

[CConsult]

Hi,

you mean EV Import PST right?

 Yout steps should be:

Open the pst in Outlook.

If there is a problem check

• Check Windows Eventlog for errors
• Password protection of PST
• Access rights (effective permissions)

otherwise check

• Is Read only set on PST?