jimmy09

We thought about this, but we really don't want it forced for everyone in the company. Just kids using the computers.

I was also able to turn the agent check-in time back down from 25 min to 5 min. They are still connecting over 24 hours later for my 1,400 clients.

To follow up; It has been narrowed down that this is related to IE protected mode. With protected mode enabled, ESET will not filter any sites if IE is ran as a non-admin. If you disable protected mode in IE, ESET filtering works as it should. I'm waiting on followup from ESET to see if there will be a fix, or if I will be forced to disable protected mode for all my users via GPO.

We don't have Google apps or anything google related. We are a O365 shop. Plus, that wouldn't help when a kid logs out of their Google account. In a Sonicwall it is a checkbox; https://www.sonicwall.com/en-us/support/knowledge-base/180629133139284 James

Is there any way to force Youtube restricted mode in EES v7? It looks like other firewalls and web filtering solutions do this; https://kb.k12usa.com/Knowledgebase/YouTube-Restricted-Mode Thanks!

The fix has worked for us as well.

I have applied the patch and disabled the scheduled restart of the service. Time will tell.

Can we get a list of all the known issues with EES V7? I can't seem to find it online anywhere.

Logs from yesterday sent via PM. Waiting on logs from today when it happened.

And now the error is gone on the client. It is very intermittent and seems to happen only to a handful of users.

Better view of the error; and the public license key is 3AA-XKX-S3J

Random clients get this error. It seems to clear itself up after a few min, but annoys the end users with pop-ups. Client versions; When I check the license information for the client, it shows that it is license. What can we do so our users quit getting the errors. Thanks

Most of us are in production environments that don't allow us to install ESMC on a Linux machine without going through a whole change process procedure. The issue I'm having is not related to our firewall at all. This is an issue with the ESMC service hanging. We have sent logs to ESET and we are awaiting their findings. Until then, the scheduled restart of the service has been taking care of the issue for us.

@Pinni3

Still waiting on an ETA from ESET on when this will be resolved.

Just an update. The reboot of the service every 4 hours is working well for me. Just not a long term solution. Hopefully it gets resolved soon.

ESET finally identified our issue as a bug yesterday.

I got tired of contacting support and not getting a resolution. I've listed the support numbers for the issues I've had in this forum post already. I just created a task schedule that restarts the ESMC every couple hours. So far, it has been working. For others that are interested, here is the powershell command I have the task schedule running. Restart-Service -Name EraServerSvc Thanks.

That's what happens for us as well. They all stop connecting at the exact same time until you restart the ESMC service.

Should I start implementing the ERA Proxy? I have about 1,400 clients.

Yes, I have multiple tickets open related to V7 issues. The last ticket I had opened with ESET about this, they closed saying the solution was changing the Agent check-in time to 20 min. My ticket number was 179128 opened with ESET North America support.

I just had to change my agent check-in time to 25 min. Still having to restart the service every couple days.

Yes. It has. They say they can't reproduce, I asked for a call back yesterday and haven't heard a response. The ticket number is #172913. I also have this topic open; https://forum.eset.com/topic/16587-ees-v7-web-filtering-issue/ Thanks, James

We still haven't been able to get web filtering working correctly since our migration to V7.

So to expand on our issue. Web filtering works in Google Chrome for our AD users. But not in IE for our AD users unless the user is an administrator. The only way for web filtering to work on standard users in IE is for the web filtering rule be set to all users or add the user into the local or domain admin group. I'm awaiting a response from US support to submit a log that I've collected.