I was reading an old thread that I couldn't reply to, from December '11. It appeared to me that the ESET folks were saying that there are too many settings in the policies for them to be all documented. (!) I notice that a very few of them have a very brief blurb on the right there that explains what they do. However, here's a fun one for you: disable the GUI. Doesn't do anything. You have to set other settings for that to work. And I'm still not exactly sure which ones, because there isn't anything explaining how they work. I'm married to ESET because the decision to go with it pre-dates me joining this organization. But until someone can point me to a document that fully describes all of the parameters in those policies, I'll leave it at this: use Sophos Endpoint instead if you have any choice in the matter. The documentation and the support are shockingly good, especially the support. So far dealing with ESET has been about an average experience, at best. Catching attitude from people who appear to think I should just KNOW how this stuff works is IRRITATING. First of all, the very idea of having hundreds of policy settings is, in itself, a design flaw. How do I find the one I want? And of course they'll be tough to document. So how do I find the one I want among hundreds (thousands?) if there isn't any documentation? So far, if I had to offer an opinion, I'd say that whatever the merits of the antivirus engine, as an enterprise solution this is rubbish. Another thing I'm missing now that I have to roll out ESET is the fact that Sophos would uninstall any existing antivirus it found when you deployed it. I, on the other hand, have to create a separate uninstall process and roll it out through GPO to strip off the previous stuff (specific process for each legacy package, which I have to ascertain for every machine in the script), and then push out the ESET package through the clunky remote console. I am growing more comfortable with it, but the attitude from the support folks and the fact that I was so spoiled by years with Sophos Endpoint have left me really disliking this poduct. Barring a significant cost difference, I wouldn't recommend this product to anyone as long as Sophos is still around. If anyone knows where I can find a comrehensive list of all of the policy settings in ESET and what each one does and how they interact with each other, that'd be great. If you're going to tell me that's impossible, I'll ask again: why in the @!#$* was it designed with so many parameters in the first place? Rubbish design. "Good enough" execution. Good thing the engine works.