Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Posts posted by Marcos

  1. I would recommend carrying on as follows:
    - apply an agent policy that will enable trace logging in agent
    - start capturing network communication With Wireshark on the client
    - send a software install task to the client
    - after the task has failed, stop logging with Wireshark and remove the agent policy
    - collect logs with ESET Log Collector from the machine and supply it along with the compressed Wireshark log to your local ESET distributor for perusal. You can also drop me a personal message with a download link so that I can have a look into it myself.

    Is the client behind a firewall or device/appliance that  performs http filtering? Does the client connect to the Internet directly or through a proxy? Are the agent proxy settings configured correctly?

    Is also an ESET PROTECT cimponent upgrade task failing to upgrade agent to v8?

  2. Agent on the client is unable to connect to the repository. Please check https://support.eset.com/en/kb332 for a list of servers and ports that ESET products should be allowed to communicate with.


    You might want to limit connections only to ESET servers:

    Use repositorynocdn.eset.com to connect ESET repository servers only, however in this case the best Internet connection cannot be guaranteed.

    Make sure you have HTTP 1.1 enabled when accessing the repository or ESET update servers via 3rd party proxy.

  3. Even if you enforce SD via a policy, you can activate override mode on a client, temporarily disable SD, reboot the machine and then try to upgrade agent by sending an ESMC component upgrade task to the client.

    If SD is not enforced by a policy, you can disable it in the setup right away, reboot the machine and try to upgrade the agent.

    We must be sure that the issue is caused by SD, hence the test with SD disabled.

  4. 2 minutes ago, anjayani said:

    any plan about adding this information in the future? because some eset user might need it for audit reason.

    As I wrote, this information is not available on clients in the above mentioned registry key. I assume this is also the reason why it's not possible to have this info in reports. @MartinKmay correct me.

  5. On 1/8/2021 at 10:22 AM, Nono said:

    I've generated (a quite huge) dump + log collection. Where/how can I send it to you ?

    You can upload it to OneDrive, Dropbox, Wetransfer, Google Drive, etc. and drop me a pm with a download link.


    I'm still on the situation that some endpoint aren't communicated with the server.

    Please check C:\ProgramData\ESET\RemoteAdministrator\Agent\EraAgentApplicationData\Logs\status.html and trace.log for possible errors.

  • Create New...