Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 12 replies
  • Subscribers 1 subscriber
  • Views 22614 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Some clients not reporting back the status of scheduled scan

Rheden

Hi,

In our environment we have scheduled scans (full scan) every week, but in one group we have 3 servers. One of those servers is reporting when it has finished it scheduled scan, the other 2 do not.

So I checked the policy just in case, but it says it scheduled. Also on the machines, Windows added a scheduled scan task. When I run the task manually, it runs and is successfully. But it still reports that the last successful (scheduled) scan was about 2 months ago.

I tried to reinstall the client on those two servers, but no luck :|

Anyone know why just these two servers or not reporting the scheduled scan back? "The last message received from computer" is also very current, reported an hour ago, so no issues there..

:48646


This thread was automatically locked due to age.
Parents
  • 0

    Hello Rheden,

    you findings suggest that the status in SEC is correct - apparently the scans haven't finished (at least not in an expected way). AFAIK the actual scan is performed by one or more threads in SavService.exe. The local GUI shows a running scan on the left (a small pane labeled Activity appears) - dunno if the information survives the "recycling" if the SavService due to an update (Note: This is not the same as restarting the service from service control in which case the scan is silently aborted) although the scan normally runs to completion.

    As it is not a reporting issue but the scans apparently don't complete (or internal communication breaks), and furthermore we can rule out the the service is manually restarted or the servers rebooted, I can only suggest that you contact Support - guess it is possible to monitor the scan. Please follow up if you have more information.

    Christian

    :48690
Reply
  • 0

    Hello Rheden,

    you findings suggest that the status in SEC is correct - apparently the scans haven't finished (at least not in an expected way). AFAIK the actual scan is performed by one or more threads in SavService.exe. The local GUI shows a running scan on the left (a small pane labeled Activity appears) - dunno if the information survives the "recycling" if the SavService due to an update (Note: This is not the same as restarting the service from service control in which case the scan is silently aborted) although the scan normally runs to completion.

    As it is not a reporting issue but the scans apparently don't complete (or internal communication breaks), and furthermore we can rule out the the service is manually restarted or the servers rebooted, I can only suggest that you contact Support - guess it is possible to monitor the scan. Please follow up if you have more information.

    Christian

    :48690
Children
No Data