Hello Steve_,
(disclaimer: I'm not Sophos and have no extended knowledge of SafeClean and scc)
use double quotes in the -bindir= option to target remote 'bins'
Dunno why you'd need double quotes for remote. The usual parsing and passing rules of the cmd shell apply, scc.exe verifies the (already parsed) parameter is a syntactically correct path, that an eventual remote share exists and then uses a standard API to locate the bin. There's one catch though as scc.exe attempts to store to the original location - I haven't tested it but I doubt it will create the path if it doesn't exist.
change EnableSafeClean="yes" to EnableSafeClean="no"
SafeClean takes an encrypted backup when a file is cleaned - move is another option to deal with an infected file (and AFAIK not available with SVRT - note that the Quarantine is "just" a list of threats which have not been dealt with). Thus setting it to "no" simply disables the backup.
Christian
Hello Steve_,
(disclaimer: I'm not Sophos and have no extended knowledge of SafeClean and scc)
use double quotes in the -bindir= option to target remote 'bins'
Dunno why you'd need double quotes for remote. The usual parsing and passing rules of the cmd shell apply, scc.exe verifies the (already parsed) parameter is a syntactically correct path, that an eventual remote share exists and then uses a standard API to locate the bin. There's one catch though as scc.exe attempts to store to the original location - I haven't tested it but I doubt it will create the path if it doesn't exist.
change EnableSafeClean="yes" to EnableSafeClean="no"
SafeClean takes an encrypted backup when a file is cleaned - move is another option to deal with an infected file (and AFAIK not available with SVRT - note that the Quarantine is "just" a list of threats which have not been dealt with). Thus setting it to "no" simply disables the backup.
Christian