labynko

ESET Bridge will not work if DNS server is not specified in the system.

Hello. All previous versions of ESET Management Agent before 10.1.1288.0 upgraded correctly over an existing installation, but now the installation fails with error 1603. I have found that disabling password protection in a policy helps resolve the issue. Is this strange behavior documented?

Description: add tag editor (rename) to ESET PROTECT Detail: If I'm not mistaken, there is no way to rename tags in ESET PROTECT. Because in ESET PROTECT the use of tags is a very convenient and powerful mechanism, it would be nice if there was an option to rename tags.

Description: in ESET PROTECT add sorting by "TARGET NAME" column in the policy assignment section Detail: In ESET PROTECT, it is very inconvenient to check to whom a policy is assigned, because no sorting by "TARGET NAME" column

Description: add automatic update of ESET Management Agent via PCU. Detail: if I'm not mistaken, there is currently no mechanism for updating ESET Management Agent via PCU. If so, it would be nice to add this feature.

Hello. I still do not understand: can ESET Endpoint Security be updated automatically via PCU from 9 to 10 version?

Description: in ESET Endpoint Security, in the firewall rule settings, when selecting an application, add the ability to use a template Detail: many network applications change their path when updated, such as WhatsApp, Opera's update checker, and many others. C:\Users\User\AppData\Local\Programs\Opera\95.0.4635.46\opera_autoupdate.exe C:\Users\User\AppData\Local\Programs\Opera\94.0.4606.65\opera_autoupdate.exe The template could look, for example, as follows: C:\Users\User\AppData\Local\Programs\Opera\<n>.<n>.<n>.<n>\opera_autoupdate.exe

Description: "Logging severity" column missing in ESET Endpoint Security firewall rules table Detail: It is very common to debug firewall rules, and setting the "Logging severity" option in one or more of the rules with a non-default value makes it difficult to find the rules where it is configured. Of course, you can first go to the firewall log and find the names of all the rules for which logging is configured there, but this is extremely inconvenient. In this regard, it would be very good if ESET Endpoint Security had a "Logging severity" column in the firewall rules table.

Description: "does not contain" filter is missing in ESET PROTECT's report template filter settings Detail: In ESET PROTECT, there is a rather limited choice in the report template filter settings. For example, it is not possible to create a filter condition to exclude the occurrence of any string ("does not contain" condition).

Description: add firewall functionality to ESET Server Security Detail: ESET Endpoint Security has a firewall, but no support for Windows server operating systems, ESET Server Security is exactly the opposite.

Description: add support for Windows server operating systems to ESET Endpoint Security Detail: ESET Server Security does not have a firewall, but ESET Endpoint Security does, but ESET Endpoint Security does not have support for Windows server operating systems.

Description: adding automatic update of ESET Endpoint Security via PCU to new versions installed on server versions of Windows OS Detail: current versions of ESET Endpoint Security installed on Windows Server OS cannot be upgraded to new versions via PCU, which is a strange limitation. It would be nice if there were no such restriction.

Description: Disable automatic installation blocking of ESET Endpoint Security on server versions of Windows OS. Detail: Current versions of ESET Endpoint Security cannot be installed automatically on server versions of Windows. In this regard, the wish is that such a restriction be removed completely or that a special command line parameter be added that would allow to bypass this restriction.

Description: additional criteria required to exclude network detections. Detail: ESET PROTECT 10.0.14.0 has a strange limitation with criteria options for excluding network detections. The allowed combinations of criteria do not at all meet the current security requirements: the criteria are quite broad and do not allow you to specify an exception more precisely. Currently valid exclusion criteria are: - detection, application, IP address - IP address - Detection - Application Often when an attack is detected, the application is not identified and thus only two options are left for selection. Optimal missing set of criteria: - detection, IP address But it would be nice to add other combinations: - Application, IP address - Detection, Application

Performing even such a task as starting a service results in an error Is there anything known about this issue?

Hello. In ESET PROTECT 10.0.14.0, in the Log Collector section, files are deleted at the start of a new day. How can I increase the storage time of files in the Log Collector section?

I didn't know, but the tasks have a history, and there is detailed information there. The "trace message" column for the problematic task contains the following information: Also, information about this error appears in the trace.log: P.S. In ESET Management Agent 9.0.1141.0 the error does not appear. In ESET Management Agent 10.0.1126.0 the error appears. I have attached the agent log collected in trace mode with traceAll. trace.log

I didn't know, but the tasks have a history, and there is detailed information there. The "trace message" column for the problematic task contains the following information: Also, information about this error appears in the trace.log:

Hello. In ESET PROTECT 10.0.14.0, when performing similar tasks, in one case the result is successful, and in the other case it is not. If you run these commands, the task will end with the Finished status: If you run these commands, the task will end with the Failed status: The processes specified in the commands do not exist and can be absolutely anything. Computers running ESET Management Agent 10.0.1126.0.

Hello. ESET Endpoint Security for Windows 10.0.2034 displays incorrect settings status. 10.0.2034: 9.0.2046:

Informatics To exclude one more computer, just add another condition like "Computer.Computer". Everything will work correctly.

The research showed that the logic has changed after updates since March 28, 2022 and affects all current versions of ESET Endpoint Security.

The problem appeared after about March 28, 2022.

Hello. Until a certain point, everything worked correctly, and ESET PROTECT received events from allowed actions, such as a firewall, with the Warning status, but now this only happens for blocked actions. I assume that these changes happened with the release of ESET Endpoint Security 9.0.2046.0. And how now to send events about the action of, for example, allowed firewall rules of the latest version of ESET Endpoint Security to ESET PROTECT?

Hello. ESET Endpoint Security 9.1.2057.0 does not save new firewall rules in override mode.