03-08-2013 02:17 PM
Solved! Go to Solution.
03-09-2013 07:36 AM
Well the admin doesnt have the ability to go to the registry remotely, so it would be up to the end user to do.
So in which case the best bet is to teach the users how to reset it themselves, but again can lead to data loss and doesn't address the issue of why so much corruption is happening
03-08-2013 03:33 PM
I guess the thing to do would be figure out why you have so many folks with Vault Cache issues.
What version of EV and Client are you using?
03-08-2013 04:19 PM
03-08-2013 04:45 PM
03-08-2013 05:03 PM
03-09-2013 12:51 AM
03-09-2013 07:36 AM
Well the admin doesnt have the ability to go to the registry remotely, so it would be up to the end user to do.
So in which case the best bet is to teach the users how to reset it themselves, but again can lead to data loss and doesn't address the issue of why so much corruption is happening
03-09-2013 08:17 AM
Agreed with JW3, Realistically you can come up with a remote way to do it, but that is just masking a problem. Do you want to keep resetting VC or fix the issue causing the corruption?
03-09-2013 10:53 AM
Have a look at the following document I wrote, it explains how to diagnose client Vault Cache issues and how to fix a number of known issues (including one around file corruption).
It's a living document that we'll try to keep updated with any new fixes/known issues as time goes on.
03-10-2013 08:46 AM
03-10-2013 09:34 AM
Yes, any AV solution could corrupt the Vault Cache.
03-10-2013 10:30 AM
03-11-2013 04:54 AM
Guys, we are actually excluding the Vault when scanning. Also we are on version: 9.0.3.1243
03-11-2013 10:59 AM
I'll chime in here. Are you using SEP? I've seen some situations where SEP will not properly exclude things. Here are some caveats I found about SEP exclusions:
a. When you exclude file types, this is a post process for SEP. It will still scan the files, but will ignore them. Unfortunately, the damage could already be done at that point.
b. Due to SEP scanning at a kernal level, %USERPROFILE% cannot be used since that is only available when a user is logged in.
I would make sure your exclusions are set to specific target locations and not rely on file types if this is the case.
I hope this helps.