Jump to content

Leaderboard

Popular Content

Showing content with the most kudos since 01/10/2021 in Posts

  1. My Mac was running very sluggish this morning and I could see ESET taking up to 530% CPU. Rebooting seems to have solved it but there definitely appears to be some sort of issue under the hood.
    1 point
  2. Email client protection is not actually protecting email clients using secure ports then? Completely baffling given secure ports are listed by default; even deceptive one might argue. And who uses insecure ports? Not those interested about email client protection I imagine So my takeaway is, users don't actually have the protection that the settings intimate they do, and this has been exposed due to changes in Big Sur which cause said protection that isn't there to crash? In which case, is it that this has never worked, but this was only made evident due to the changes in
    1 point
  3. Ergo, there is no email protection in Big Sur for secure ports? Is this a feature removal?
    1 point
  4. These are the default settings: Are you saying the default settings are wrong?
    1 point
  5. I would also like an answer to this question before we start the upgrade to 7.3 Thanks,
    1 point
  6. And if you attempt to install File Security via "software install task", what is the reported error (as I assume, that such attempt would fail). What I would do in this case, is try to login to the affected machine in safe mode, and execute eset uninstaller, to remove any remains of EFSW installation, and also the EEI, and once the system is "clean", reinstall those components from scratch. It might indicate a corrupted EFSW install. Also, is this machine reporting any events to EEI server, or reporting any functionality problems in EP console?
    1 point
  7. Hi Thomas, My solution is the following: 1.: - I created a dynamic group for collect the computers with error message "Restart required" : 2.: - Then I defined a CRON triggered task for send a pop-up window message into the affected computers: "Hello Collegue, please restart your computer as soon as possible because an ESET software update...bla..bla" or something like this You can configure the CRON for example launch the message hourly, every 10 minutes or as you want It works pretty fine
    1 point
  8. For information, I have the Limited Direct Cloud Connectivity warning message each time I launch Steam. Everything is up to date. I don't really care for myself but it might help you to figure out which port may be problematic.
    1 point
  • Newsletter

    Want to keep up to date with all our latest news and information?
    Sign Up
×
×
  • Create New...