07-15-2011 09:22 AM
Don't client-driven PST migrations get PSTs on network shares (home directories)? It's not happening that way for us, but I thought it's worked for me in the past.
A user has the PST listed in the Outlook data files and it shows to be attached in Outlook.
The EV client log shows the PST is found and marked, but it's not being migrated.
Are there any PST tasks besides the PST migration task that needs to be running on the EV server for client-driven migrations?
Solved! Go to Solution.
07-15-2011 10:24 AM
Have you seen this tech note?
Client-Driven PST migration not migrating PST when PST exists on a network share.
http://www.symantec.com/docs/TECH68805
07-15-2011 09:43 AM
I had an issue where the schedule on the PST migrator task was set to Never.
Even though the task was running it would not push the PST up to the holding folder.
Once I set a schedule on the task and restarted. It would push the chunks up to the holding folder.
07-15-2011 10:08 AM
Thanks Jim,
I've had that happen to me before, but the task is scheduled and running.
PST files that were stored locally on the PC were migrated, just not the PSTs located on the network.
07-15-2011 10:24 AM
Have you seen this tech note?
Client-Driven PST migration not migrating PST when PST exists on a network share.
http://www.symantec.com/docs/TECH68805