Jump to content

Tad2020

Members
  • Posts

    4
  • Joined

  • Last visited

About Tad2020

  • Rank
    Newbie
    Newbie

Profile Information

  • Location
    USA
  1. Recently migrated from EP 8.x to 9.x and this has been causing a lot of headaches. In 7.x and 8.x these were considered and shown alerts for statuses. After moving to 9.x, they are not. The dashboard element mentioned and shown does not appear to exist. Closest is a pie chart that is collectively for any and all ESET products, and is generally not helpful in any meaningful way beyond an indicator that "there is one or more things outdated". The other list based dashboard elements aren't very helpful either, they only give client counts for an individual specific product and version. The workflow to go from the dashboard/report to an outdated client is tedious to the point of uselessness. There are dozens of separate report lists to go through, most which only a single client machine. It has literally faster and less work to manually walk over each individual client machine to troubleshoot update failures from the inventory instead of dealing with the annoyances of using countless randomly sorted reports. It seems very counter-intuitive that "Everything is OK" while installed versions are red or even unsupported.
  2. Well, its pretty much all 50+ of them doing it every 2 to 5 days till I disabled protocol filtering so even capturing one in the fault condition is difficult, and lol.
  3. Please supply us with a complete memory dump as asked in my previous posts. There's no known bug on ESET's part that would be causing it; it's a bug in Microsoft Windows Filtering Platform that manifests on unpatched systems if ESET's agent or another application performs full-duplex communication or if application protocols are filtered in a specific manner by a 3rd party driver. We are patched though. Memory dump has not be possible, either because it does not work or that the affected systems are rebooted by the user or their secretary before a dump can be attempted. So far disabling protocol filtering via a policy has prevented any further incidents.
  4. Just wanted to add that we are also having these problems. We installed KB2664888 on 60 endpoints yesterday and already 2 have frozen again. I'm highly disappointed, we just bought this less than 2 weeks ago and its crippling our business worse than the Crypowall infection that prompted the budget approval. A proper fix better be coming soon, the CEO is likely to force me to do a return on the licenses or do a charge-back as the product is unsuitable for use.
×
×
  • Create New...