labynko

Strange, but in two registry sections information about the old version remains, but the files are updated. Old version (11.0.503.0): New version (11.2.2076.0):

Hello. After updating ESET Management Agent from version 11.0.503.0 to 11.2.2076.0, ESET PROTECT 11.1.14.0 still shows the old version 11.0.503.0. The problem is only with one computer. How can I fix this without reinstalling ESET Management Agent?

Hello. When updating ESET Management Agent manually, no need to disable password protection, but if you install a new version over the network via Msiexec, the installation will fail with error 1603 without disabling password protection. Why is this? Network installation example:

Hello. ESET Endpoint Security 11.0.2044 in troubleshooting network access in the tooltip does not fully show the full path to the process.

Example for the current version. Rec 0003.mp4

Maybe this example will help. My example uses an old version of ESET Endpoint Security. In the current version, you can select not only paths, but also files. Rec 0002.mp4

Hello. Why isn't ESET Management Agent listed as a product on the latest versions page? https://help.eset.com/latestVersions/ Why does the download page show version 11.0.503.0 as the latest version of ESET Management Agent, but not 11.1.1152.0? https://www.eset.com/int/business/download/eset-protect/#standalone Can I install ESET Management Agent 11.1.1152.0?

A terrible bug, you can’t normally change the settings of many policies, you have to create them again. When is this issue expected to be fixed?

Hello. In EESET PROTECT 11.0.14.0, you cannot enable a disabled firewall rule in policies. Rec 0004.mp4

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.