-
Posts
36,418 -
Joined
-
Last visited
-
Days Won
1,448
Posts posted by Marcos
-
-
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 cybersecurity
-
7 hours ago, Zardoc said:
There is a new version 17.1.9.0 Is there a download link plz ?
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:
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.
-
4 hours ago, Fredinpa said:
I am seeing the same issue. Scan runs and after short time hangs for 30+ minutes at: \REGISTRY\MACHINE\SOFTWARE\Classes\htafile:FriendlyTypeName hta file in the registry
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.
4 hours ago, Fredinpa said:In addition the timer running also freezes and does not increment.
Please switch to the pre-release update channel in the advanced setup to upgrade your ESET to v17.1.9 which has this fixed.
-
7 hours ago, pukko said:
same problem
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.
-
Perhaps changing the priority of the output chain would help. If you use "filter" priority (alias for 0), change it to -102.
If that doesn't help, please raise a support ticket.
-
As I wrote, you should submit the sample to ESET first. Without it, it's impossible to tell if the detection is correct or not. However, it's unlikely that so many detections reported on application files would be false positives.
-
Please raise a support ticket for further assistance with the migration.
-
Please raise a support ticket for help with finding the root cause of the issue.
-
Administrator's confirmation about detected cloning required.
I assume the problem is unresolved detected cloning question: https://help.eset.com/protect_cloud/en-US/vdi.html
If that doesn't turn out to be the case, please raise a support ticket.
-
Please raise a support ticket. The only thing that occurs me is that the program is crashing and egui is restarted so further investigation will be needed.
Zscaler + ESET Issue
in ESET PROTECT On-prem (Remote Management)
Posted
During agent replication the connection is initiated by agent on clients, not by the ESET PROTECT server.