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

    on my legacy Mac the Do-Action (and the resulting scan) doesn't sen a message to the AV log. But the scan (if started) writes its log to /Library/Logs/Sophos Anti-Virus/Scans/SEC Full System Scan/ (a named scheduled scan would write to a folder with its name). Dunno though where you would see why a scan isn't started.

    Christian

    :54073
Reply
  • 0

    Hello Vlad,

    on my legacy Mac the Do-Action (and the resulting scan) doesn't sen a message to the AV log. But the scan (if started) writes its log to /Library/Logs/Sophos Anti-Virus/Scans/SEC Full System Scan/ (a named scheduled scan would write to a folder with its name). Dunno though where you would see why a scan isn't started.

    Christian

    :54073
Children
No Data