Jump to content


ESET Staff
  • Content Count

  • Joined

  • Last visited

Profile Information

  • Gender
    Not Telling
  • Location

Recent Profile Visitors

1,777 profile views
  1. Hi Guys, if there is a portion of endpoints which reports some error message please check, if a particular endpoint has EDTD license. Go into ESMC Computers > Show details If you don't have it, for such endpoints you'll need to do a new activation task. We've started to show proper information via module update, that why it's sudden. We're also working on a way how to add such endpoints into Dynamic Group in ESMC so some "join dynamic group trigger" or recurrent activation task can be planned.
  2. Hi Brandobot, you can find logs from installation in /var/log/install.log, however, please know that there is more information than just log from ESET products. I'd strongly recommend contacting support directly - https://www.eset.com/us/support/contact/?intcmp=btn-support-request#/business-support/install-activate-endpoint-product/install-endpoint Thank you
  3. Hi EJ, It works a little weird due to architecture which is solved in v7. Let me explain. By executing OD scan in webGUI or command line "esets_scan", settings from product (esets.cfg) (or ERA policy) are not applied. You'll need to use parameters (check -h). In such case, please use following task: sudo /opt/eset/esets/sbin/esets_scan --exclude="/root" /root executing scan from ERA uses utility /opt/eset/esets/lib/esets_sci which is checking esets.cfg file and in such case it'll exclude what is defined. This is however not usable much for executing via command line as you get no output into console when you use esets_sci Does it make sense for you?
  4. Unfortunately there is nothing smart... as smart I mean that it'll detect automatically what is local drive and what is shared mount. In such case only option (v4.5.x) is to do an exclusion - in ERA/ESMC policy > Antivirus > Exclusions > Files and folders to be excluded from scanning :set there mount points of shared drives. Hopefully if you have multiple servers, they're mounted on the same spot so one policy can solve that issue for all. We're very sorry for inconvenience.
  5. Hi EJ, this function is currently not supported and will be supported with new version 7 (right now it's still not supported in current beta 1). You can however play with it if you like. To sign up for testing, please follow this thread:
  6. Matus

    Issues with OS X client after upgrade

    Yes, it's known and will be fixed in upcoming update. Seems that there is some miscommunication. We're sorry.
  7. Matus

    Issues with OS X client after upgrade

    Hi J-gray, we're looking into these issues and splash screen as well as kernel extension error will be fixed within next update planned for beginning of the new year.
  8. Hi Vqhuy, as vShield is End of Life (https://kb.vmware.com/s/article/2144733), I'd advise you to deploy VMware NSX (only part responsible for AV which is free, not networking stuff). In such case, please find compatibility list here: https://www.vmware.com/resources/compatibility/search.php?deviceCategory=security&details=1&partner=611&page=1&display_interval=10&sortColumn= &sortOrder= What you're interested in Guest Introspection (successor to vShield) with documentation available here: https://docs.vmware.com/en/VMware-NSX-Data-Center-for-vSphere/6.4/com.vmware.nsx.admin.doc/GUID-049EF8ED-224C-4CAF-B6E7-1CD063CCD462.html Long story short, you can deploy newest NSX on vCenter 6.5 with ESXi 6.0 and it'll run fine.
  9. Matus

    EES 6.7.500 Crashes Macs

    Hi Matthew, Please could you submit all logs to support team for further investigation? Have you enabled "Live Grid Feedback system" when installed directly or "Submit anonymous statistics" in ERA/ESMC policy? This would send us crash logs immediately once it happens. Thank you