Jump to content

Leaderboard

Popular Content

Showing content with the most kudos on 04/07/2021 in all areas

  1. Just to be sure, but by "only check in when they are turned on" you mean that do connect only once, after they are started, and another connection attempt is made after reboot? If so, I would double-check configuration of interval, especially in case "cron" based configuration was used. Also as mentioned, troubleshooting of such device connectivity will be required, as issue might be also related to network configuration, which might prevent subsequent connections, especially in case there are other security/VPN products used or strict firewall configuration is applied.
    1 point
  2. I'd recommend opening a ticket with your local ESET distributor. Trace logs from 1-2 troublesome clients as well as from the server will be needed for a start. It's possible that the logs will need to be generated with trace / debug verbosity but we'll see, maybe standard logs will be enough.
    1 point
  3. Yes, you are right, it's Windows 8.1. I found out that the problem happens just after on-demand computer scan. The first time was the March 28th, after scan, the usage of RAM reached 821 Mb and 25% of RAM. I uninstalled the ESET product in Safe Mode and reinstalled it. Immediately after installation the use of RAM was 164 Mb (normal) which grew to stop at 340 Mb. (This hapened last March 29th.) Yesterday I did a new scan and RAM usage reached over 700 Mb. I switched off the computer, waited more than 13 hours before switching on. No, like the previous time , more than 13 hours later and memory
    1 point
  • Newsletter

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