winstonsmith84

Anyone know how to stop the patch management and vuln mgmt from flagging as a red alert when it's not on if we aren't using it anyway?

How do I get Eset to stop flagging our PCs with a red alert because we aren't using this feature? I need these red alert statuses to be because of something serious. Not a feature I'm not using that isn't turned on.

I'm noticing a bunch of endpoints now saying that patch management and vulnerability management are non functional. Is this a new service in Eset? I don't recall seeing this before. Does it require additional licensing cost? If this is something we are not paying for how do we turn off these red alerts? I'd rather not see alerts for a feature I don't have access to anyway since it makes it seem like the endpoint is having an urgent issue. If this is something we are actualy paying for then why would they all stop working and how do I get it working again?

I was able to get the log collector to run as long as I chose to not use the administrator account to run it. Not sure what that was about but I do have the logs now. Attached. ees_logs.zip

A couple of days ago we began getting alerts on all the PCs at one physical location saying Undocumented serious error (210a) I know you will want me to grab log files for this but I can't. The machines with this issue allow me to turn on advanced logging and then try to get an update while the logging is on but I can't get the log files afterwards. When I run log collector I get an error message that says ESET SysInspector executable signature verification failed.

I think maybe I see what could be a part of the problem. Our server environment has a mix of either 2 cores or 4 cores. What it seems like I'm seeing is that quad core servers aren't having the problem but dual core ones are. Is anyone else seeing this? Are these latest updates so CPU intensive that a dual core setup can't start Eset in time? Marcos mentioned low hardware specs probably being a culprit and it seems like dual core CPUs can't get Eset started because of these updates.

Anyone? We have people updating servers and not checking for Eset afterwards and then servers are left to run unprotected until someone just happens to notice days later. We need a notification for when this happens. How do I set this up?

This. How do I get a notification set up to alert me about this? I don't see any built in notifications for this specific scenario.

We have one computer that runs incredibly slow. Every time we check task manager Eset has the disk pegged at 100%. We did a log file for advanced OS logging within Eset if someone needs me to send it in.

Eset keeps sending an alert on one machine in our network saying Module HTTP filter - Threat Alert triggered: hxxp://www.cassiopessa.com/assets/scripts/main.js?1460287547 contains JS/Adware.Agent.R application. The computer in question has no extensions installed in Chrome. The person using the computer says they aren't going to this website.

Nevermind. Event Viewer shows the update never started because permission to stop the Eset Management Service was denied.

Web console says "Login failed: Connection has failed with state Not Connected". I'm assuming I just keep waiting until the web console finally works again but this seems like it's taking a very long time and I don't know how I would even know if it failed or not.

The update has been running for over an hour. I can't log into the web console during this obviously and there is no status update of any kind so I can't tell if this is actually updating or if it failed and just hung. At what point do I give up and assume failure and restore the VM? The tomcat service is running on the server and the eset management service on the server says "stopping". It has said this for a long time now. Is the upgrade actually happening or did it fail?

Unfortunately the error happens sporadically across the network. I never know when it's going to happen and I can't force it to happen.

I get these error messages frequently. "During execution of Update on the computer the following event occurred: File does not exist." If I run the update modules task on the affected computer then it updates. Why does this keep happening and how do I make these computers update themselves without having this error?