sdnian

Computers are controlled by a firewall and only a limited number of specific websites are accessible. After installing EEA 7.3.2039, using a browser to connect to https sites is very slow and may even time out. If I turn off the SSL/TLS protocol filtering, it will be back to normal. Does EEA's SSL/TLS protocol filtering feature need to connect to certain IP addresses? Or how can I fix this?

This issue seems to have occurred after I upgraded ESMC 7.2, maybe there is a tweak or something in the new version that is causing this problem.

This is one of the clients that failed to upgrade, the error message is in Chinese, this kind of message also appeared before, why this is an Invalid utf8 leading byte? software-install.log

I run the Client Task from ESMC for Software Install to Upgrading EEA 7.3, most Clients succeeded in the upgrade, but a few failed and one of them displayed the Trace Message as follows: What does that mean? ESMC Server 7.2.1266.0, Agent 7.2.1266.0, Client OS: Windows 7/10

Disable QUIC fix this issue.

I'd like to block https://www.youtube.com/. In URL ADDRESS MANAGEMENT, I add a record *.youtube.com. I've tried IE/Firefox/Vivaldi, https://www.youtube.com/ been blocked. But if I use Chrome to browse https://www.youtube.com/, EEA don't block it. If I block others domain, for example: *.facebook.com, then https://www.facebook.com/ been blocked in IE/Firefox/Vivaldi/Chrome. EEA version: 7.2.2055 How can block YouTube form Chrome?

No other language version?

@Marcos Why are the contents of these two files different? hxxp://repository.eset.com/v1/com/eset/apps/business/ees/windows/v6/6.5.2132.5/ees_nt32_enu.msi hxxp://download.eset.com/com/eset/apps/business/ees/windows/v6/6.5.2132.5/ees_nt32_enu.msi

About 7 hours ago, there is a new version fixing tool. It works these versions now: 6.5.2094.0 6.5.2094.1 6.5.2107.0 6.5.2107.1 6.5.2118.0 6.5.2118.1 6.5.2118.2 6.5.2118.3 6.5.2118.4 6.5.2123.5 6.5.2123.7 6.5.2123.8 6.5.2128.0 6.5.2132.1 6.5.2132.2 Read this: https://support.eset.com/en/alert7396-legacy-products-startup-issue

If I have ESET Endpoint product 6.5.2132 running on Windows XP. After use the fixing tool, do I need to upgrade 6.5.2132.5 ?

I've few EEA 6.5.2132.2 (XP SP3), run this tool failed. The message is "Can't rename ekrn.exe!" How to resolve? Others work well.

This issue only occurs with 6.6.0.0-6.6.2063.x. 6.6.2089 can be updated normally.

How Windows XP / Server 2003 solves this problem?

Thanks for your reply, I know how to manage the new exclusions.

I've two questions about policy settings.. 1. The EXCLUSIONS settings of policy in the sam ESMC server, why have different setting items? 2. The 'Detection exclusions' setting, if the client is EEA/EES < 7.2, could apply this settings?