This is currently one of the functions in the policy settings of Webroot. However, I have found out the hard way that several of the settings (IE cache, Chrome cache, and microsoft office recent document history) are not available to manage as part of the policy settings. Turning off the central management of the system cleaner does not rectify the situation -- the settings are left in place. The only way to change them that I've found is to set the machines in question to unmanaged policy, make the necessary changes, and switch it back to it's normal policy. I've confirmed this is a bug with support, and they let me know it's went to development but no eta on a fix.
Has anyone else run into this? If so, what did you do to resolve the problem? I spent some time combing the registry and looking for settings elsewhere to see if I could find where Webroot stores the settings for the policies, but I couldn't find what I was after. I did see quite a few settings out there for other things though. Support says the policies govern what Webroot shows in the window, but if it's set to unmanaged, it has to be pulling it from a local copy somehow.
I'm just trying to avoid having to do this by hand on the large number of computers I will likely have to adjust.
Only solution is to manually open the interface on "each" individual machine and uncheck all the items under advanced > system cleaner. This is what I was told today by support - with no mention of it being under scrutiny for development.
Why can't it just be one setting that either checks the items for cleaning or unchecks them all, not just specific common ones - from the management console.
This will burn up several hours of my time fixing as we have some very annoyed clients.
Has anyone tried just leaving it enabled but disabling it from running on any day? Mine was set for Mon/Thu and today (Fri) I recieved several complaints about it happening. I just took off Mon/Fri and left it enabled. Hoping it wont ever auto-run as a temporary fix instead of trying to go by hand onto a hundred desktops, and one might assume this is set per user even so even worse ..