webbdj

Ditto to this question. I have been rolling out ESET6 with the RA appliance as a number of my larger customer sites. Several of my customers are annoyed that their servers are showing up on the problem computers list. I applied the "Antivirus - Real Time Scanner Only" to several of our servers that are performance sensitive. We rarely every access the internet from these servers, but they do utilize API interfaces to partner entities that a https scanner and/or Phishing module may interfere with.. MichalJ comment about purposefully disabling anti-phishing via a policy has not changed the reporting status in ERA that these servers "Anti-Phishing protection is disabled" in the "red alerts" ... On a semi-related note.. the servers were also showing a warning about the "protection grid" until I logged into each one and clicked the checkbox ... One of my sites has over sixty servers, so having to go back and do this for each one is also a bit annoying..

So here is my perspective on this: Years ago, we were a Mcafee house. Till Mcafee go really bad at stopping any real threats, and kept killing our windows updates and legitimate programs. During the Mcafee ERA, they had EPO. EPO was ok for our large enterprise clients who could afford for us to spend most of a day getting it setup and tweaked, but completely sucked for our small business clients who had less than 50 workstations. At least Mcafee listened for a while, and released Protection Pilot. That held us for a few years until they decided to ditch that product as well. And so we ditched them. (We sent numerous emails warning them, they didn't listen to their clients). When we moved to ESET, it was a refreshing change. I can complete the installation and deployment of ESET (removal of other antivirus vendor products non-withstanding), in about an hour or less! I can complete upgrades of the entire ESET5 solution in under an hour. For my smaller clients, I could put the ESET console/server on one of our domain controllers or auxiliary servers, and because it didn't require SQL server, it was small, unobtrusive, and out of the way. Then ESET6 happened. We started playing with it for one of our Enterprise level clients who had about 600+ workstations. Spent two days dinking with it, and rolled it out to the IT department computers (about 20 or so). Within two weeks, we gave up. Uninstalled it, and returned all 20 workstations back to our ESET5 server. We have been watching ESET6 with interest, but up to this point have advised all of our clients to remain on ESET 5 for now. The requirements that ESET6 now imposes on us are unacceptable for many of our clients. If ESET doesn't listen to their clients, and work on a solution that is more inline with what ESET5 provided, we will be shopping for a new solution for our entire client base. For us, this is somewhere in the neighborhood of 5000 client workstations, and 200-300 servers. So I implore ESET management, on behalf of ourselves, and everyone else in this thread who has commented, PLEASE PLEASE PLEASE reconsider your current solution, and work on an alternative for small business clients who cannot justify dedicated servers just to manage their antivirus solution. Regards -DJW Chief Systems Engineer for a Midwest IT Support company with about 500 client companies.