Jump to content

"Idle-State Scan" policy has no effect


Timotheus
 Share

Recommended Posts

Recently I changed our EES policy to run Idle-state scan.:

grafik.png.75487fff77e47530c41b8eaee7e56471.png

I can see in the EES GUI that the policy is effective, but no scans are happening.

Just in case I made the same changes to our Agent policy. Still no effect.

Does anyone have an idea what might be wrong?

Link to comment
Share on other sites

Additional Information

  • Version of ERA    7.2.2236.0
  • OS of ERA Server:    Virtual Appliance
  • OS of Client device:    Win 10 Pro 64
  • Management Agent    7.2.1266.0
  • EES    7.3.2041.0
Link to comment
Share on other sites

  • Administrators

How did you find out that no idle-state scan was run? Did you actually enable logging, locked the system, logged in and then you checked computer scan logs?

Link to comment
Share on other sites

  • Administrators

Do you always get 0 scanned files even if the system has been locked for several minutes? Could you post a screen shot from the machine?

image.png

Link to comment
Share on other sites

I did not enable logging. I am simply judging by the fact that the last scan time does not change inspite of giving in ample opportunity to run.

The screenshot you asked for looks like this:

grafik.png.9f7d98501fa0af53125a7b48ff277581.png

But that probably does not mean much with logging turned off.

I will turn logging on and see if there is something to be learned there.

Link to comment
Share on other sites

It seems a bit strange to me, but after adding logging to the policy I now see that computers are being scanned on the ESMC dashboard and also in the log file on my test pc. Does that mean that computers were being scanned but because logging was off ESMC did not find out about it?

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...