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

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 Reply Children
No Data