labynko

Hello. ESET Endpoint Security 9.1.2057.0 does not show built-in firewall rules in override mode https://streamable.com/kpgtvz

baran https://content.invisioncic.com/Meset/monthly_2022_08/2022-08-03-22-16-09.mp4.620ad701c89cfff7df3593cf199d6522.mp4

The information in the article contradicts the current requirements: https://help.eset.com/protect_install/91/en-US/database_requirements.html

First of all, I would not want this error in future versions, since a similar problem is already encountered a second time (in the previous case, the problem was with the status of another component that was not installed). Now, of course, the easiest way to solve the problem is to install all the "required" components and disable them through policies.

The protected machine does not have Internet access. I understand what web protection is for. When all web protection components are not installed, the anti-phishing status cannot be configured.

ees_logs.zip

Forgot to attach a picture.

Hello. ESET PROTECT 9.1 reports that Anti-Phishing protection is a firewall component. It's right?

Hello. I installed ESET Endpoint Security 9.1.2051.0 without any web and mail scanning components, but the program reports a problem: "Anti-Phishing protection is disabled". 2022-07-19-23-53-35.mp4

avielc, it looks like it. I have a fast drive and the database update may have gone quickly. Is your current version of the database application on the list of supported by ESET PROTECT 9.1?

I migrated to JDK 17 according to the official article: https://support.eset.com/en/kb7088-install-esmc-web-console-using-jdk There is currently no warning about an outdated JDK version.

I also encountered the same authorization error after upgrading to ESET PROTECT 9.1. Restarting the Tomcat9 and EraServerSvc services helped me. After restarting the services, I waited for some time, because the task manager showed that the database service was loaded at that moment. Then I tried to connect via the web interface, and everything went well.

1. Does ESET Protect 9.1 support Microsoft SQL Server 2017 RT Standard Edition (64-bit) 14.0.3445.2? 2. Why is Java Runtime Environment 1.8.333 deprecated by ESET Protect 9.1?

Hello. I tried to implement using HIPS in EES 9.1.2051 such a scenario as blocking the launch of any applications from a specific folder except those allowed. Is such a scenario even possible? To do this, two rules were created in HIPS. The first rule allows all applications to run programs at C:\New folder\write.exe, and the second rule blocks all applications from running programs at C:\New folder\*. This setting results in the fact that each time C:\New folder\write.exe is launched, one processor core is loaded, the resources of which begin to be consumed by the parent application. After that, the parent application cannot be terminated in any way. Also, the problem repeats if you simply specify the path as C:\New folder\write.exe in the blocking rule. 2022-07-03-23-05-35.mp4

Marcos, this is a local folder like c:\updates I tested the same set of updates with the previous version 9.0.2046, and the update works in this way in it.

Hello. Can EES 9.1.2051 be updated from a mirror of EES 9.0.2046? When trying to update EES 9.1.2051 from an EES 9.0.2046 mirror, an error message is displayed:

Hello. In ESET PROTECT 9.0.10.3 firewall settings incorrectly display paths that use environment variables. Environment variables must not be converted when displayed.

mathisbilgi, I don't know about EFSW, but I'm using ESET Mirror Tool 1.0.1258.0. An example of running a program with parameters: Filter file (filter.txt) content example (the filter is configured to load only one product):

Wouldn't it be nice if in Windows 10 ESET Endpoint Security, before upgrading to a new version via the PCU, monitored that the user chooses to shutdown rather than restart, and at the same time turn off "Fast startup" until the next startup.

It is strange, but good at the same time, that this warning is not displayed in ESET PROTECT 9.0.10.1.

P.S. This notification cannot even be disabled locally.

Do I understand correctly that the notification that "Endpoint Security can't connect to Push Notification Service" cannot be disabled via policy? If so, will such an opportunity appear in the future?

Hello. If you execute the command: MirrorTool.exe --repositoryServer AUTOSELECT --filterFilePath filter.txt --dryRun test.csv with the following contents of the file "filter.txt": { "products": [ { "app_id": "com.eset.apps.business.ees.windows", "version": ">=8.1.2037.2", "languages": ["en_US"], "os_types": ["windows"], "platforms": ["x64"] } ] } then the results will also include products com.eset.tools.installers.bootstrapper_era and com.eset.apps.business.era.agent. Why so?

Yes, I confirm. I updated it manually.