Marcos

Please carry on as follows: Enable advanced logging under Help and support -> Technical support Reproduce the issue Stop logging Collect logs with ESET Log Collector and upload the generated archive here.

The verification email was sent to the license owner's email address saxxxxxxxxxro@sxxo.pt who must click the verification link to enable you to add the license to your ESET HOME account.

What about using a filter like this in the report?

It appears that you have attempted to add a misused Afghan license in your ESET HOME account. Please purchase a license from an authorized ESET distributor or reseller.

Since we could not find any issue in the attached logs, please raise a support ticket. A logging version of the Safe banking and payment module will need to be installed to get more information.

ESET is a reputable security company that has been on the market for more than 30 years already. Out products do not perform any malicious actions nor do contain a remote control function. Even the remote management agent cannot control the machine and merely maintenance connection between Endpoint and the ESET PROTECT server. Also running a script cannot be considered malicious unless the script is malicious. Many legitimate programs and also Windows itself may run script for legitimate purposes. The best would be if you could provide some screenshots for illustration but I'm sure there must be some misunderstanding of what you were seeing.

During agent replication the connection is initiated by agent on clients, not by the ESET PROTECT server.

This rundown of 10 cyberattacks against the sports industry shows why every team needs to keep its eyes on the ball when it comes to cybersecurityView the full article

It has not been released yet but it's available on the pre-release update channel already.

Please remove: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Security Center\Provider\Av\{DF8BEACB-94C9-218A-73AD-A78362A8C516} HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Security Center\Provider\Fw\{E7B06BEE-DEA6-20D2-58F2-0EB69C7B826D}

Notifications about upcoming license expiration cannot be disabled, otherwise it could happen that users will remain unprotected and may get infected if they don't renew the license on time. If you don't auto-renew your license, you could suppress all desktop notifications by disabling them in the advanced setup:

My understanding is that the instructions for Linux apply also for the Linux-based VA: https://support.eset.com/en/kb7857. If not, please raise a support ticket for assistance.

Please raise a support ticket for help with configuration of LDAPS.

Please follow the instructions at https://support.eset.com/en/kb7856.

If you plan to perform migration while retaining the current IP address of the PROTECT server, follow these instructions: https://help.eset.com/protect_install/11.0/en-US/clean_installation_same_ip.html?migrated_database_same_ip.html In that case you won't need to reinstall the ESET Inspect Server. If you plan to use a different IP address, you would need to reinstall it while specifying the new IP address during installation.

This is expected. Scanning the registry takes long. The information about the path is informative, it should show the last path that was scanned. Startup scans run after a module update and when the system starts are faster as they scan only autostart registry locations. Please switch to the pre-release update channel in the advanced setup to upgrade your ESET to v17.1.9 which has this fixed.

Are you able to reproduce it after uninstalling ESET and installing the latest version 17.0.16 from scratch without importing previous settings?

You can add a report like this on the dash board:

If you are using a self-signed certificate generated by ESET, it's expected to get a warning like this:

Please elaborate more on the issue and post a screenshot for clarification. What website are you referring to?

Could you test it also with Firefox? Please provide logs collected with ESET Log Collector while a browser is running.

If you open the console via https, did you previously use your own certificate issued by a trusted CA with the CA certificate present in the trusted root CA cert. store?

Unfortunately I have no clue why authorization would fail when updating from a local directory. Please raise a support ticket.

I didn't see the above logs from the other machines so it's impossible to tell if it's the same issue or a different one.

I would add that the option is not available if sample submission is disabled in the advanced setup.