Jump to content

Marcos

Administrators
  • Posts

    35,853
  • Joined

  • Last visited

  • Days Won

    1,428

Marcos last won the day on March 25

Marcos had the most liked content!

About Marcos

Profile Information

  • Gender
    Not Telling
  • Location
    Slovakia

Recent Profile Visitors

64,879 profile views
  1. It has not been released yet but it's available on the pre-release update channel already.
  2. 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}
  3. 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:
  4. 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.
  5. Please raise a support ticket for help with configuration of LDAPS.
  6. 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.
  7. 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.
  8. Are you able to reproduce it after uninstalling ESET and installing the latest version 17.0.16 from scratch without importing previous settings?
  9. You can add a report like this on the dash board:
  10. If you are using a self-signed certificate generated by ESET, it's expected to get a warning like this:
  11. Please elaborate more on the issue and post a screenshot for clarification. What website are you referring to?
  12. Could you test it also with Firefox? Please provide logs collected with ESET Log Collector while a browser is running.
  13. 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?
  14. Unfortunately I have no clue why authorization would fail when updating from a local directory. Please raise a support ticket.
×
×
  • Create New...