Jump to content

smarra

Members
  • Posts

    6
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by smarra

  1. I noticed this too. in my case it was an issue with the new eset agent causing high cpu with the wmi service.

     

    To test this, I simply stopped the agent service.  Once I did that, everything returned to normal.  

    started agent service, everything went slow.

     

    I tried to update the agent, but that had no effect.  I sent the logs to eset as requested, but eventually decided to revert back to v5.  

  2. I agree that fulling testing a product before going into production is a must.  Unfortunately, with limited resources, it makes it more difficult.  Some users don't have labs or test environments to use.  With that being said, I didn't encounter most of my frustrations until after deployment!  

     

    So to continue with my frustrations,  I updated my ERA server.  Now it appears that none of the clients are reporting back.  

     

    I think ESET customer care and support is great. The few times I needed help with something, they have been very helpful and responsive.  However, at not fault of ESET, I just don't have the time, staff, or resources to dedicate right now to get back to some basic functionality that was easily available in v5.  

     

    I think that I've made up my mind on rolling back to v5.  I'll use it until its EOL, and then evaluate what to do next when that time comes.  

     

    I think ESET will get v6 where it needs to be, but for the time being, I'm not a fan of v6!  I guess that's the price I paid for trying to be cutting edge! :)

  3. I would like to echo the first post.  

     

    I have been using eset for just over a year.  I loved the product.  The admin console was quick and easy to use. Navigation was simple. Detection was amazing. It was fast, and did bog down the workstations. Everything I hated about symantic, mcafee, etc was gone!  

     

    Then v6 was released...  oh, how I wish I would have spent more time with it in testing before deploying it to production.  I am not happy with v6 at all.  There really isn't much I like about it. I don't care for the web based console.  I don't like the agent approach of the client, I'm seeing it cause some odd issue with WMI service, and consuming cpu.  The deployment of a/v, generating reports, view the panels, just about everything is overly complicated and cumbersome.  Not all is bad, I do like the rouge scanner.  

     

    I'm torn on what to do next. Do I give v6 more time, and maybe grow into it?  Regardless, change is going to happen, but it looks like I'll be changing back to v5!

×
×
  • Create New...