Jump to content

Marcos

Administrators
  • Posts

    36,501
  • Joined

  • Last visited

  • Days Won

    1,453

Posts posted by Marcos

  1. 1, Activation was never performed automatically. Most likely you had a dynamic group (DG) with not activated clients in ERA and a software activation task assigned to the DG. Do you have the same in ESMC?

    2, Do you have the proxy server set correctly in Endpoint advanced setup under Tools -> Proxy server?

    3, Under Tools -> Proxy server there is a setting "Use direct connection if proxy is not available" which is enabled by default. However, we do not recommend disabling it since a direct connection will only be attempted if the proxy is unavailable for whatever reason.

  2. If you apply a policy with rules with the default action "replace", all rules on clients will be replaced with the rules set by the policy, however, since you also apply rules by policies with append/prepend action, I understand that this is not a solution for you.

    In previous versions of ERA, if a policy was no longer applied, settings set by the policy remained set on the client which allowed for resetting settings to defaults. However, as of ESMC if a policy is no longer applied, previous local settings are used.

    I'm afraid there's no way how to remove default rules from clients completely without uninstalling the security product and installing it from scratch.

  3. The purpose of this forum is to share the knowledge among standard users, advanced users and ESET moderators. It is not meant to serve as a substitute of contacting customer care, especially if an issue is not obvious, easily reproducible, if diagnostic logs are required  and multiple iterations with support or developers are needed. Also this forum cannot track the progress of tricky issues and thus ensure timely response.

  4. Please temporarily lower the sleep time for disks to 5 minutes or even more so that logs are not too big. Then start logging with Procmon as per the FAQ on the right-hand side of this forum, reproduce the issue and then save the log. When done, compress it, upload it to a safe location and drop me a message with a download link.

  5. Since the current (legacy) version of Endpoint for Linux does not support the activation system, it does not connect to edf.eset.com whatsover.

    If you use a proxy server for connecting to the Internet, configure it in the Endpoint's advanced setup (e.g. via a policy) and send a software activation task from ESMC. This will ensure that the legacy connector in agent will add your username and password in the Endpoint's setup and Endpoint will then be able to communicate through the proxy and authenticate against ESET's update servers with the username and password.

    If you plan to update from a mirror, simply set the path to the mirror in a policy. If updating via http, no username/password for authentication will be needed. Otherwise if you update from a remote share, you will need to specify also a username and password for authentication against the machine that creates the mirror.

  6. It's nothing unusual, I have several similar records as well:

    Time;Application;Operation;Target;Action;Rule;Additional information
    5/28/2019 4:38:13 PM;C:\Windows\System32\svchost.exe;Get access to another application;C:\Windows\System32\winlogon.exe;blocked;Self-Defense: Do not allow modification of system processes;Modify state of another application

    So unless you are experiencing issues caused by SD, consider it normal.

×
×
  • Create New...