Jump to content

Marcos

Administrators
  • Posts

    36,328
  • Joined

  • Last visited

  • Days Won

    1,445

Posts posted by Marcos

  1. First of all, it is a fundamental functionality of an antivirus to scan files that are accessed or executed. Please elaborate more on what kind of scan you mean. Is it that you see an on-demand scan being run under Computer scan in the main gui?

    Note that it's vital to keep automatic startup scan in scheduler enabled. Otherwise it could happen that malware could run undetected, or malware in certain locations, such as the WMI repository, will not be detected and cleaned.

  2. The best would be if you could install Endpoint Security v7 to troubleshoot the issue. With EES v7 installed, carry on as follows:

    - enable both Network protection and Licensing advanced logging in the advanced setup -> Tools -> Diagnostics
    - try to activate the product
    - disable logging
    - collect logs with ESET Log Collector and upload the generated archive here.

  3. Thanks. Since the issue with Web Control is most likely related to Endpoint and to avoid discussing different issues in this topic, please create a new topic in the Endpoint forum and provide a screen shot or two with the errors that you are getting. I've checked the logs you've supplied and there was no mention of an error neither in ESET's event log nor the system log.

  4. In this case it's the PR_TRANSPORT_MESSAGE_HEADERS_W property which is in conflict. The property contains transport-specific message envelope information for email and this modification cannot be avoided. If email is scanned on the mail server, disable integration with MS Outlook.

    As of Enpoint 7.1, processing email messages will be completely revamped and will ultimately prevent sync issues from occurring.

  5. 30 minutes ago, Trooper311 said:

    So for the Windows 7 clients stating that Web Control is not functional is that a false positive basically?

    It can be either an issue registering a WFP callout (e.g. due to issues with BFE or registry permissions), or you disabled protocol filtering which is now indicated by a change of the protection status. Please provide me with logs collected with ESET Log Collector from such machine so that I can check the configuration.

  6. It is necessary to upgrade the server from ERA 6.5 to ESMC. As stated in the documentation, Agent v7 cannot communicate with an ERA Server do to changes in the communication protocol.

    Agent can be upgraded by sending an ESMC component upgrade task to clients.

    As for the notifications that the firewall is disabled, you can suppress them via a policy -> User interface -> Application statuses.

×
×
  • Create New...