11-11-2009 12:05 AM
11-12-2009 04:44 AM
11-12-2009 11:34 AM
-Yes since VV is a part of Vault Cache you'll need Vault Cache.
When using this policy, will the VV work on desktops?-Nope, see above
Can I create two policies, to have laptops get the full VV, and the desktops the VV with only metadata?-Sure, two different desktop policys will give you the possibility to have laptop get full download to Vault Cache (VV) and Desktop only header
What should the target be for these policies? (As I do not have the possibility to target users, only machines, I am not sure I can differentiate to have one group get the full VV, and one have the metadata VV)01-08-2010 02:00 AM
http://www.symantec.com/connect/forums/ev80sp23-using-ovenabled-and-virtual-vault-machines-have-oven...
https://www-secure.symantec.com/connect/forums/disable-vault-cache-desktops#comment-3087051
I'm working on this issue at the moment. The OVEnabled regkey isn't the key (mind the pun) for this issue as the default is 1 - enabled. It's going to be a combination of identification (finding laptop users) and the following 2 regkeys;
OVRequireOfflineStore = 1 (Default)
OVContentDownload = 1 (Default)
Everyone will have Vault Cache enabled (i.e. desktop and laptop users), we just need to identify the laptop users and apply those keys. The default for the desktop users will be;
OVRequireOfflineStore = 0 - This will be 0 in the policy for desktop users (not required)
OVContentDownload = 0 - This will be 0 for desktop users (Item headers only)
I will also apply the OVMDCSyncFrequencyInSecs regkey to the desktop users (certainly not laptop users) so that the frequency of VV is better than every 24hours!
For Example;
OVMDCSyncFrequencyInSecs = 300 (5 minutes)
Let me know if you have made any head way with this?
Thanks,
BZ