Jump to content

Camilo Diaz

Members
  • Posts

    42
  • Joined

  • Last visited

About Camilo Diaz

  • Rank
    Newbie
    Newbie

Profile Information

  • Location
    New Zealand

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hi Marcos, what's the signature ID / Engine version?
  2. It seems like the client is not pickup up the policy correctly and it keeps displaying the Eset icon in the Dock. I have confirmed the the policy is configured correctly and applied to the device... See attached screenshots. I am also getting reports that the Client is displaying the OS updates notification, but we have it configured it to NOT display those... See screenshots.. MacOS Monterey 12.3.1 EEA 6.11.202.0
  3. Policies -> Settings -> (Web and email) Web access protection -> web protocols -> Ports used by HTTP protocol
  4. Hey Marcos, as mentioned by other members, as soon as an user logs in, Real-Time protection start working again, so I don't think it will be feasible to get the logs from a device experiencing the issue...
  5. My Bad. Have sent you a link with the full logs.Thanks
  6. Hi Marcos, we are experiencing exactly the same issue in about ~1000 workstations. all upgraded via Installation Task from ESMC . I have enabled FULL dump for logs and attached the results here. btw. it's only affecting EEA 7.3.2041.0 eea_logs.zip
  7. Hey Marcos, I do see some resolved but other ones remain not resolved. Some of them running EEA 7.3.2041.0.
  8. Can your clients telnet to your new ESMC server on port 2222? If not then there's highly likely a firewall stopping the connection. (assuming the new server is working as expected). What about new clients? Can they connect to the new server?
  9. ESET Security Management Center (Server), Version 7.2 (7.2.1278.0) ESET Security Management Center (Web Console), Version 7.2 (7.2.230.0) We are currently managing the Antivirus detection by adding the endpoints to a Dynamic Group and running a Scan Task which if successful it resolves the detection. My understating is that for the 'Firewall' Module detection, this has to be manually resolved. (Is there any insight of improvements on this?) For the 'Web protection Module' we have a fair amount of blocked detection 'attempt to connect to URL - Blocked by PUA blacklist/Blocked by Internal blacklist'. We'd like to auto-resolve/close this if the status is 'blocked'. Is this possible? Thanks, Camilo.
  10. Hi Marcos, I was experiencing the same with a few clients and after a reboot the warning is gone for good . Cheers
  11. We have experienced the same issue again, eset_proxy process consuming 100% CPU and blocking somehow the network on the affected devices. Running Eset Endpoint Security 6.90.0. All affected devices are running macOS 10.14 (Mojave). Have reported it to ESET so hopefully we'll get an answer soon. Thinking to upgrade to 6.90.3 but not sure if it will make any difference at this stage.
  12. Ok problem solved. I had missed that notification which explains it will attempt to upgrade as much as it can (in my case, the agent). I can also select a dynamic group. Thanks!
×
×
  • Create New...