labynko

ESET PROTECT installer does not allow upgrading from 8.1.13.1 to 8.1.13.2. Why so?

If, when installing ESET Endpoint Security 8.1.2037.2, in the context menu, select the "Entire feature will be unavailable" item for the "Web and mail" components, and then enable all nested components using the "Will be installed on local hard drive" context menu item, then after installing the program, there will be problems in the operation of almost all components of "Web and mail". Details of the problem can be seen in the video: https://streamable.com/f0xdt5

The problem appeared with the release of ESET Endpoint Security version 8.1.2031.0. If you install ESET Endpoint Security without component "Web access protection", the program will constantly display a warning that this component is not enabled. Is this a bug? Is there any way to solve this problem?

Ankit Upadhyay, if you are using ESET PROTECT, please update the program to the latest version and then re-create the policy for ESET Endpoint Security.

Marcos, two weeks passed. When should we expect a new release?

Why doesn't ESET Endpoint Security 8.0.2028 install uPCU update to version 8.0.2039 from the local repository? I see that ekrn is loading metadata from repository (http:\\192.168.1.1\v1\com\eset\apps\business\ees\windows\metadata3), but nothing further happens.

A month (if not more) has passed since the release date of ESET Endpoint Security 8.1.2031.0 and it is still not clear how the MicroPCU update mechanism works and whether it works at all.

The latest working versions for Windows XP SP3 are: ESET Management Agent 8.0.1238.0 ESET Endpoint Security 7.0.2100.4

While the developers are working on fixing the problem, you can activate the program using the ESET RMM mechanism. 1. You must enable ESET RMM using policies and add the command line application (c:\Windows\System32\cmd.exe) as a permitted program. 2. Then you need to place the license file on a web server (a proxy server installed with ESET PROTECT is a good fit for this) and create a task to run a command, the contents of which should be something like the following:

The Print Spooler service uses a port from the dynamic range and is allocated by default in Windows Vista and newer, starting at 49152. To block it correctly, you need to change the dynamic range to your own. Here is an example of the range from 9000 to 9099: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc\Internet] "Ports"=hex(7):39,00,30,00,30,00,30,00,2d,00,39,00,31,00,35,00,31,00,00,00,00,00 "PortsInternetAvailable"="Y" "UseInternetPorts"="Y" After reboot, the Print Spooler service will reserve a port in the range 9000 - 9099. This range will need to be blocked for incoming connections.

Of course, without this option, importing the license file is not possible. From ESET PROTECT. Local activation works correctly.

Hello. I acknowledge the problem. Used software versions: ESET PROTECT 8.1.13.0 ESET Management Agent 8.1.1223.0 ESET Endpoint Security 8.1.2031.0

Hello. StefanL4, you don't know about the even more interesting behavior of the program with the network. When a firewall is configured (when only specific connections are allowed to ekrn.exe process), if you go to "Network protection troubleshooting" in ESET Endpoint Security, you can see that ESET Endpoint Security itself (C:\Program Files\ESET\ESET Security\ekrn.exe) tries to establish outgoing connections with different devices on the network using such TCP ports like 62078, 445, 80 and UDP ports 1900, 5353, 137, 3702. This means that if there were no deny rule, then the ekrn.exe process could establish all these connections!

Hello, Marcos! I share the requested log.ei_log.txt