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

    Thanx for all the replied guys..

    Before I tested any further, I cloned one of the servers in our test environment where I can replicate all of the problems that I can see until now.

    So I investigated further and tried to break up the scan in to little pieces. Both servers do not pass the "Master Boot record. drive PHYSICALDRIVE1" section, it always hangs on 2% completed.

    So I uninstalled the Sophos client and reinstalled (with policies etc.), but no luck, still the same problem.

    After that I installed the stand alone version, same thing.

    There were a few things that I know changed after the last succesfull scan on both servers, that is Windows Search and previous versions. So I uninstalled Windows Search, did a reboot but no go.

    After that I did a full offline scan (Sophos boot cd) but no problems are detected.

    Then I booted with the Windows recovery disk to start a commandprompt and start bootrec to fix the mbr, but also no go.

    Then I disconnected on of the disks (d: drive (data)) and added that to another server in my test environment to scan the disk, so I can determine if it's a server or disk issue. But the manual scan gives the same results:

    Items being scanned: Master boot record, drive PHYSICALDRIVE2

    So I am at a loss now, what can I test next to find out where the problem is? Or how can I fix this error?

    :48864
Reply
  • 0

    Thanx for all the replied guys..

    Before I tested any further, I cloned one of the servers in our test environment where I can replicate all of the problems that I can see until now.

    So I investigated further and tried to break up the scan in to little pieces. Both servers do not pass the "Master Boot record. drive PHYSICALDRIVE1" section, it always hangs on 2% completed.

    So I uninstalled the Sophos client and reinstalled (with policies etc.), but no luck, still the same problem.

    After that I installed the stand alone version, same thing.

    There were a few things that I know changed after the last succesfull scan on both servers, that is Windows Search and previous versions. So I uninstalled Windows Search, did a reboot but no go.

    After that I did a full offline scan (Sophos boot cd) but no problems are detected.

    Then I booted with the Windows recovery disk to start a commandprompt and start bootrec to fix the mbr, but also no go.

    Then I disconnected on of the disks (d: drive (data)) and added that to another server in my test environment to scan the disk, so I can determine if it's a server or disk issue. But the manual scan gives the same results:

    Items being scanned: Master boot record, drive PHYSICALDRIVE2

    So I am at a loss now, what can I test next to find out where the problem is? Or how can I fix this error?

    :48864
Children
No Data