Client-driven PST issue
Updated: 23 May 2010 | 1 comment
I've seen an unresolved post about an open issue with client-driven pst ingestion when it come to "Sharepoint Links.pst" files. I didn't know until today either that when Outlook is linked to a SharePoint Calendar that it'll drop a PST on the machine. I've found the PstMigratorTask.exe.config file, but there isn't anything currently listed on excluding a file name. Nor can I find any documented settings that could be added.
I really really want to exclude "Sharepoint Links.pst" from attempting to be ingested by client machines. Thoughts anyone?
Discussion Filed Under:
Comments
I have just come across this
I have just come across this issue today as well. I'm not aware of anything out-of-the box that can help us here.
We are planning on doing client side migrations and to also delete the PST files.
One thing that we could do is to monitor the PSTFile table for these entries and immediately mark tham as do not migrate. Not a fantastic solution, but we may need to resort to this as a last resort.
Ben
..
Would you like to reply?
Login or Register to post your comment.