Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 4 replies
  • Subscribers 1 subscriber
  • Views 9619 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

Console initiated Full System Scan issues

VladGuan

Hi All,

We have serveral Windows, Linux and Mac OS X servers/workstations protected by our Sophos server. Full system scans initiated via the SEC gets registered for Windows (7 and 2008 R2) and Linux (Centos) machines but either is not started or not registered on the SEC for Macs and Fedora machines. They are all up to date and have all policies applied.

Anyone know why the Macs and Fedora machines are either not responding the the scan or not reporting back?

Thanks,
Vlad

:53953


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

    Hello Vlad,

    a scheduled scan should appear in the scans list of the endpoint's GUI. The Mac GUI at least in addition shows the last time such a scan has been run. Regardless of the platform the scan's start should be recorded in the AV log apart from the scan-specific log. Unless the scan perishes in some obscure way completion, abort, or cancel should also result in a message written to the log (which is normally also sent to SEC together with alerts and errors - although these are not explicitly associated with the scan, only the "final" message is). BTW - I've tested with an outdated OSX10.4/SAV8.0 installation where the Mac hadn't been rebooted for ages and albeit compliant it didn't start the scheduled scan. After reboot the scans were started according to schedule and correctly reported to SEC.

    Christian

    :53977
Reply
  • 0

    Hello Vlad,

    a scheduled scan should appear in the scans list of the endpoint's GUI. The Mac GUI at least in addition shows the last time such a scan has been run. Regardless of the platform the scan's start should be recorded in the AV log apart from the scan-specific log. Unless the scan perishes in some obscure way completion, abort, or cancel should also result in a message written to the log (which is normally also sent to SEC together with alerts and errors - although these are not explicitly associated with the scan, only the "final" message is). BTW - I've tested with an outdated OSX10.4/SAV8.0 installation where the Mac hadn't been rebooted for ages and albeit compliant it didn't start the scheduled scan. After reboot the scans were started according to schedule and correctly reported to SEC.

    Christian

    :53977
Children
No Data