Video Screencast Help

Best solution for PSTDisableGrow breaking Vault client

Created: 15 Jul 2008 • Updated: 21 May 2010 | 3 comments

We are starting our pilot rollout of Office 2007 and we are enforcing group policies to prevent the continuning usage of PST files.  The problem is that the PSTDisableGrow registry setting breaks the Vault client by preventing the retrieval of Vaulted items (can anyone say irony?).  I found the following Tech Document and there are two solutions. 

 

Doc ID: 302038

 

One is allowing PST creation (not an option) or the other is switching to MSG as the default format during retrieval.

 

Are there any downsides to going with option #2?

 

There is another option and that is to have the EV team code the Vault client to create the temporary PST files as "Sharing-Exclusive PST's" which we allow for our users to do in order to work with our Sharepoint environment.


Message Edited by worldzfree on 07-15-2008 12:58 PM
Discussion Filed Under:

Comments 3 CommentsJump to latest comment

MichelZ's picture

Hi

 

Yes, there is a downside.

The EV Servers will need to unpack the .DVS files, this will put some additional load on them.

 

I'm not aware of other major downsides.

 

Cheers

Michel

Hayabusa's picture

Has Symantec actually done this - or is this just a suggestion for something they COULD do? 

It is ironic that EV uses temp PST's files .....

 

Does anyone know if a future release deals with this PST issue?

 

Suggestion or reality??????

There is another option and that is to have the EV team code the Vault client to create the temporary PST files as "Sharing-Exclusive PST's" which we allow for our users to do in order to work with our Sharepoint environment.

 

Thanks!

Hayablusa

MichelZ's picture

This was a suggestion...

 

Cheers

Michel