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

Sophos CLI scan goes wrong

AKoenig

Hello dear Community,

i have a problem with the Sophos virus scan using the CLI.

Our company wants me to develop procedures using Kaseya to scan our company Workstations.

To acomplish this, the first thing coming to my mind was scaning the PCs using the CLI command, but here comes the problem.

When I execute the sav32cli.exe with the parameters -DI -P:"C:\Temp\Sophos_Scan.txt" --stop-scan , there is a huge fail, which(i think) is not attended to happen. See attachment for the outcome of the first hour of scaning.

Basicly, what it does, it is going into a structure which is non-existant at all, and decreases the /Anwendungsdaten with every retry, coming down to no /Anwendungsdaten in the structure at all, which should be the right place to scan.

My question here is of corse:

- How do i fix this problem?

-If not fixable, is there any other way to trigger a scan from "remote"?

:55168


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

    Hi,

    Is there a reason the standard scheduled scan in the product is of no use?  

    Is it the condition when to scan you want to influence and reacting to time as part of a schedule is not helpful?  

    Is it the cutomization of options to scan with?  

    Is it that the endpoints don't have SAV installed and you're just copying the command line scanner to the computer to run the scan?

    If SAV is installed on the computer, you can just run the following commands to initate a scan:

    64-bit:

    "C:\Program Files (x86)\Sophos\Sophos Anti-Virus\BackgroundScanClient.exe" {F86EBCD5-687E-40B1-800D-021062361F6C}

    32-bit:

    "C:\Program Files\Sophos\Sophos Anti-Virus\BackgroundScanClient.exe" {F86EBCD5-687E-40B1-800D-021062361F6C}

    This will trigger the default (Scan my computer now).  

    When running scans it is worth considering the user context it is being called under and therefore the files that can be accessed.

    Regards,

    Jak

    :55185
Reply
  • 0

    Hi,

    Is there a reason the standard scheduled scan in the product is of no use?  

    Is it the condition when to scan you want to influence and reacting to time as part of a schedule is not helpful?  

    Is it the cutomization of options to scan with?  

    Is it that the endpoints don't have SAV installed and you're just copying the command line scanner to the computer to run the scan?

    If SAV is installed on the computer, you can just run the following commands to initate a scan:

    64-bit:

    "C:\Program Files (x86)\Sophos\Sophos Anti-Virus\BackgroundScanClient.exe" {F86EBCD5-687E-40B1-800D-021062361F6C}

    32-bit:

    "C:\Program Files\Sophos\Sophos Anti-Virus\BackgroundScanClient.exe" {F86EBCD5-687E-40B1-800D-021062361F6C}

    This will trigger the default (Scan my computer now).  

    When running scans it is worth considering the user context it is being called under and therefore the files that can be accessed.

    Regards,

    Jak

    :55185
Children
No Data