Jump to content

Marcos

Administrators
  • Posts

    35,860
  • Joined

  • Last visited

  • Days Won

    1,429

Everything posted by Marcos

  1. I mean there is nothing like code emulator or generic unpacker known as Advanced heuristics on Windows. However, we use generic detections on Android, Linux and MacOS a lot too.
  2. After updating kernel you must sign the ESET kernel module again by running: sudo /opt/eset/eea/lib/install_scripts/sign_modules.sh -a
  3. The file http://repository.eset.com/v1/com/eset/apps/business/eea/windows/v11/11.0.2044.0/uPCU/2814754195439616/eea_nt64.dup.changelog.html is available and can be downloaded. It's most likely a problem with permissions for the folder in which the tool downloads mirror files.
  4. You can generate ELC logs as suggested above and upload the generated archive here. To contact technical support, click https://go.eset.com/contact-support and go through the support wizard. At the end it will offer an option to contact technical support.
  5. Actually we didn't do anything. There must have been a glitch with the server that was fixed in the mean time.
  6. Please perform migration to a new VA as per https://help.eset.com/protect_deploy_va/11.0/en-US/va_upgrade_migrate.html.
  7. Agent 10.x can be installed on Windows 7 SP1 with latest Windows updates (at least KB4474419 and KB4490628): https://help.eset.com/protect_install/10.1/en-US/windows.html
  8. Unfortunately protection and detection capabilities are limited on Android which are caused by OS limitations, battery consumption, CPU performance, etc.
  9. First of all please check C:\ProgramData\ESET\RemoteAdministrator\Agent\EraAgentApplicationData\Logs\status.html and trace.log for errors. You can upload them here, attachments are available to ESET staff only.
  10. The management agent is automatically upgraded as well: https://help.eset.com/protect_admin/11.0/en-US/agent_autoupgrade.html
  11. Please provide logs collected with ESET Log Collector for a check.
  12. Please use the ESET PROTECT all-in-one installer to upgrade all components. 3rd party components cannot be upgraded via an ESET PROTECT component upgrade task.
  13. Please provide logs collected with ESET Log Collector. Are you able to reproduce the issue after uninstalling ESET and installing v16.0.17 from scratch without importing previous settings?
  14. Must be set to "warning", otherwise it won't be sent to ESET PROTECT.
  15. To accomplish that, you should: 1, Set the warning severity for the appropriate Device control block rule 2, Create a desired Device Control report, e.g.
  16. What logs are you interested in? Information about detections is available in the Detections panel, other data is typically available via reports. Diagnostic logging can be enabled in client details and generated records can be viewed there.
  17. If eset_proxy.exe is running then the icon must appear too. if it's not hidden, then it's probably a problem in Windows. I'd recommend raising a support ticket to find out.
  18. What is the website in question? Please do not post links to Google drive but the url in an obfuscated non-clickable form.
  19. Windows XP and Windows Server 2003 are not supported. If I remember correctly, the last version with Window XP support was Endpoint 6.5 that reached EOL in 2022: https://support-eol.eset.com/en/policy_business/product_tables.html. Please use a supported version of Windows 10 or Windows 11. For server OS please refer to the list of supported systems: https://help.eset.com/efsw/11.0/en-US/system_requirements.html. The newer you use, the better and the longer support it will get.
  20. Please carry on as follows: When the issue occurs, enable advanced operating system logging under Tools -> Diagnostics -> Advanced logging in the advanced setup After 1-2 minutes stop logging Collect logs with ESET Log Collector and upload the generated archive to a safe location (e.g. OneDrive, Dropbox,...) and drop me a personal message with a download link.
  21. Unfortunately it is not clear what you mean. Please create a new topic and post there also some screenshots for clarification.
  22. When does agent stop replicating? After upgrading the ESET PROTECT server? What version did you have before and after upgrade? The version of Endpoint does not matter as long as agent replication is concerned. If you are referring to the version of modules used by Endpoint, then the answer is protection can be ensured only with up to date modules. If you meant the version of Endpoint, older versions may miss some protection features or may not provide as effective protection as current versions. We recommend keeping Endpoint as well as its modules always up to date. If it's not possible to always use the latest version of Endpoint, use one that has full or at least limited support (https://support-eol.eset.com/en/policy_business/product_tables.html). We recommend using the auto-update feature that also enables administrators to control what maximum version the product can upgrade to automatically. Should you have more questions, please sign up first and post in the appropriate product forum here.
  23. You will have to re-deploy the management agent using current ESET PROTECT server settings and certificates.
  24. The file may be in a subfolder of system32 since the whole path is not visible in the screenshot. I assumed it was directly in system32.
×
×
  • Create New...