Jump to content

j-gray

Members
  • Content count

    239
  • Joined

  • Last visited

  • Days Won

    3

j-gray last won the day on April 12

j-gray had the most liked content!

Recent Profile Visitors

1,244 profile views
  1. j-gray

    ESET scans and forceful termination.

    I would definitely take a look at the clients and see what all is being scanned. Also verify your scan settings and exclusions: Are they scanning network drives? Do they have external/USB drives that are getting scanned? Are other synced items getting scanned (e.g. Google Drive, etc.).
  2. That's a good question. In the AV policy under Tools > Privileges, there are options for 'Privileged groups' and 'Privileged users' which is similar to the password protection option for Windows clients. Presumably if root has not been added there, it will not have permissions to modify ESET. You would obviously need to have an admin group (that excludes root) or another local admin account in lieu of root. I don't believe there are any protections for the agent, though. Hopefully someone from ESET support can clarify.
  3. I ran a standard upgrade task from ERA to upgrade an OS X client to the latest release. During the upgrade process, is popped the ESET splash screen to the logged on user (me). ERA policy for these clients is set to disable the splash-screen at startup. Are there any options to suppress the splash-screen during upgrade?
  4. j-gray

    OS X - Update already in progress

    @Peter Randziak; Any idea if this issue is caused by the agent or the AV client? I upgraded to the latest version AV (6.6.800.1) yesterday and just got the same 'update in already in progress' warning pop-up just now.
  5. I'd recommend first making sure your DNS is working flawlessly and rule out it as the cause of the mismatches. Then verify you have the 'Rename Computers' server task configured to run periodically. Also, if computers are frequently renamed in AD, or happen to get disjoined and rejoined, this can cause issues, as well
  6. j-gray

    Scanning for days

    I'm going to guess that this (Scanning in progress) is a bug:
  7. What step is giving you trouble? Were you able to successfully deploy the agent via GPO to newly joined workstations?
  8. j-gray

    Scanning for days

    The OS X client does not have the option of idle state scanning like the Windows client does...
  9. j-gray

    Scanning for days

    A little fishy, right? And it was still scanning today when I came in, so it's been going almost a week. We don't scan network drives/shares and my local drive is not that large. The GUI still shows 'Scanning in progress' with '0' files scanned. I rebooted several times and both scheduled scans still show 'Scanning in progress'. The icon is not animated, so as far as I can tell it is not scanning presently. There's nothing logged under 'Events', either. It's empty. Anyone have any suggestions where to look to figure out 1) is it scanning currently, 2) what has it been scanning Also wondering if it is expected behavior to start a new scan if one is already running. Also, when/how often is the 'Scanned' count updated in the GUI? Only when the scan is completed or interrupted? Appreciate any insight.
  10. j-gray

    OS X - Update already in progress

    Great. Thank you.
  11. j-gray

    Scanning for days

    Full scan is scheduled for Wednesday afternoons. Typically it is still running days later. Today is no exception as it is Friday afternoon and has been running since Wednesday. The GUI gives no useful information. Apparently the scan from last week is still 'in progress', as is this weeks scan. But two days later it apparently still has scanned zero files. Where can I look to determine what's up with the scan?
  12. j-gray

    OS X - Update already in progress

    The error message randomly drops down from the ESET app icon in the OS X menu bar at the top of the screen then disappears in only a few seconds --unfortunately not enough time to grab a screenshot. Again, would be handy if the app logged errors by default and didn't have to have a separate application running to log errors...
  13. j-gray

    OS X - Update already in progress

    I've been running the latest RC for a week or so. Just got the "update already in progress" pop-up again, so does not appear to be fixed. And of course I was not logging at the time. I did find that a short logging session generated a 250MB file when zipped up. Hopefully it doesn't get larger than that after time.
  14. The agent seems prone to corruption. There are a more than a few threads with similar findings/experience on both Windows and OS X. Assuming the issue is not firewall, the only fix we've found is to uninstall the agent via msi. You have to use a third-party product, as once the agent is broken ERA tasks are useless. Once the agent is uninstalled, you can redeploy using ERA console. Activation and AV install both rely on Internet connection, so verify that your endpoints have connectivity and aren't blocked.
  15. j-gray

    OS X - Update already in progress

    Unfortunately, it is a very random pop-up. It frequently goes days without appearing and I don't think my drive is large enough to collect logs for that duration. One would think that errors in the application would be logged natively without having to jump through hoops. While I do see log files under the ESET application folder, they are all .dat files and not readable. Is there anywhere else I can look that would have any useful information?
×