labynko

Hello. Using ESET PROTECT 10.1.1283.0. Computers with the following versions of Management Agent and operating systems are not displayed in any dynamic group: ESET Management Agent 8.0.1238.0 + Windows XP SP2 ESET Management Agent 7.2.1266.0 + Windows Server 2003 SP2 Is this normal behavior?

You are mistaken about this. This functionality works fully in many versions, but often, like some other functionality, it stops working in some versions. Here are the versions in which the firewall override works: 9.0.2046.0 10.0.2045.0 10.1.2050.0 10.1.2058.0 Here are the versions in which the firewall override does not work: 9.1.xxxx.0 10.0.2034.0 11.0.2032.0 11.0.2044.0 Yes. Here are typical situations when you may need to change firewall settings in override mode: 1. Temporary creation and change of any rules: locally you can make changes that are valid for no more than 4 hours. If you use a policy, you can accidentally forget about the applied policy, but it will continue to be in effect. 2. Convenient local debugging of firewall rules: no need to wait a minute each time until the policy is applied again. 3. If you need to change the firewall settings without disabling it, when there is no connection with ESET PROTECT, this cannot be done without locally overriding the firewall rules.

This is sad news. It is very, very unfortunate that the functionality in ESET Endpoint Security is degrading.

Users did not break the policies themselves - it was errors in your software that led to this. So why can’t ESET make a tool in this case that would report that the policy is corrupted, or better yet simply correct the errors? And if the user has hundreds of policies, then this requires a lot of effort to fix everything from scratch.

Hello. In ESET Endpoint Security 9.1.2071.0, firewall rules cannot be saved in override mode.

Hello. In ESET Endpoint Security 11.0.2044.0, firewall rules cannot be changed in override mode: almost all parameters are not configurable.

Hello. Config engine module 2092.2 (0.0.2080.0) dated 09/29/2023 does not apply firewall rules through dynamic group policies. I had to downgrade the Config engine module to 2083.3 (0.0.2078.0).

I inform you that the problem indicated in the topic is not resolved in the firewall module 1439.1. After the new version of the firewall module was installed, in my case it was 09/06/2023, a problem arose with Opera at least four times. Sometimes restarting the browser does not help, and you have to restart it again.

Do I understand correctly that the problem has not yet been resolved, and it will be resolved in version 1440 of the firewall module, which will be released on October 21?

Starting from version 10.1.1288.0, agent updates are only possible after password protection is disabled. Is this a new policy? If, when upgrading to version 10.1.1288.0, this can still be explained, but the upgrade from version 10.1.1288.0 to 10.1.1292.0 is not performed without disabling password protection! The update occurs via the command line: msiexec /i hxxp://192.168.0.1:3128/ema/ema_10.1.1292.0_x64.msi /q P_HOSTNAME=192.168.0.1 P_ENABLE_TELEMETRY=0 P_CERT_CONTENT=... P_CERT_AUTH_CONTENT=...

IT-KAV, if you are using ESET PROTECT for Windows, do you get email notifications about changes in dynamic groups?

Almost two weeks have passed, and the firewall module version 1438.2 has been distributed in regular updates and is still being distributed. At the same time, it's funny that if you install ESET Endpoint Security 10.1.2050.0, then the firewall module will have version 1439, and if you upgrade to ESET Endpoint Security 10.1.2050.0, it will be 1438.2. What is the reason for such a delay?

Hello. I did not see in the new version of ESET Endpoint Security 10.1.2050.0 such an improvement as "Added more optional columns to firewall rule list". As seven columns were available, it remained so.

Hello. Created a dynamic group change email notification in ESET PROTECT 10.1.24.1, but it doesn't work. Sending a test email works. Also, emails about viruses and trojans come without problems. ESET PROTECT (Server), Version 10.1 (10.1.1283.0) ESET PROTECT (Web Console), Version 10.1 (10.1.274.0) Update module 1035 (20230718) Translation support module 1980.1 (20230821) SysInspector module 1284 (20230207) SSL module 1078 (20230518) Push Notification Service module 1133 (20230626) Configuration module 2075.6 (20230804)

Does the ESET Endpoint Security scheduler officially support running programs other than exe, such as bat, cmd, etc.?

In ESET Endpoint Security 10.1.2046.0, the task does not start on an event.

This event fires only once for me. Tested with ESET Endpoint Security 10.0.2045.0.

Hello. The scheduler in ESET Endpoint Security allows you to execute a task after a successful module update. Does the Detection Engine module update qualify for this condition?

A month has passed since the release date of the firewall module 1438.2. When will the new version of the firewall module get into regular updates?

Hello. Will there be more new releases of version 9 of ESET Endpoint Security for Windows?

Marcos, how soon will a new version of the firewall module get into regular updates?

Marcos, were you able to reproduce the problem? If so, when can we expect a fix?

I was able to reproduce the issue in a test environment. Rec 0002.mp4 The collected debugging information can be downloaded from the link: https://dropmefiles.com/ObCXq Information for Marcos: the password for the archive is the same as previously sent to private messages.

I note that the problem is observed both on old versions of ESET Endpoint Security 9.1.2063.0 and the current 10.1.2046.0. Does ESET PROTECT have a built-in mechanism that automatically checks if policies are correct? How can I manually check the policy for correctness?

I am using ESET PROTECT 10.1.24.1 and Configuration module 2075.5 (20230713). I create a new empty policy and apply it twice to the same computer and the problem shows up.