Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 12 replies
  • Subscribers 1 subscriber
  • Views 22610 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

    I've been trying to test this during today and what I have observed is:

    • Manually ending the scan on the endpoint reports the fact to the SAV.txt log as well as the individual scan log named after the name of the scheduled scan.  You also get an error to the console.
    • Restarting the SAV service quits the scan and nothing is logged reported.
    • Forcing an update/reinstall causes the scan to pause and pick up again.

    Demo: http://www.screencast.com/t/GyhCZe774

    I'd say that size and amount of files that are being scanned (i.e., the long scan length) is a factor.  According to my observations above the most like is that the SAV service is being restarted or there is a similar like event occurring.

    I'd suggest breaking the scan down a bit and scanning a part of the drive.  Maybe Mondays some folders, Tuesdays other, etc.

    If you decide to raise a ticket ensure you include a link to this thread to save time and post back what you find out.

    :48710
Reply
  • 0

    I've been trying to test this during today and what I have observed is:

    • Manually ending the scan on the endpoint reports the fact to the SAV.txt log as well as the individual scan log named after the name of the scheduled scan.  You also get an error to the console.
    • Restarting the SAV service quits the scan and nothing is logged reported.
    • Forcing an update/reinstall causes the scan to pause and pick up again.

    Demo: http://www.screencast.com/t/GyhCZe774

    I'd say that size and amount of files that are being scanned (i.e., the long scan length) is a factor.  According to my observations above the most like is that the SAV service is being restarted or there is a similar like event occurring.

    I'd suggest breaking the scan down a bit and scanning a part of the drive.  Maybe Mondays some folders, Tuesdays other, etc.

    If you decide to raise a ticket ensure you include a link to this thread to save time and post back what you find out.

    :48710
Children
No Data