The Sophos Community will be offline for scheduled maintenance this Saturday, May 27th, at 13:00 UTC for approximately 1 hour. Apologies for any inconvenience caused.
"Wanna" ransomware outbreak. Please see this Sophos article sophos.com/kb/126733 for advice on how to protect your organization. Immediate action recommended.
This article provides information that applies to Sophos installations on either physical or virtual systems.
Applies from the following Sophos product(s) and version(s) Sophos Endpoint Security and Control 9.7
For Sophos installations that are running on a physical (i.e. non-virtual) machine or system:
You can perform customized installations of endpoint software (Sophos Anti-Virus, Sophos Remote Management System and Sophos Client Firewall) on Windows computers by running the setup.exe program from a command line. This allows you to deploy endpoint software to your network using a startup script and the installation method of your choice, as well as invoking some of the special features described below.
For Sophos products installed on a virtual machine or system:
You can embed an installation of endpoint software on Windows computers by running the setup.exe program from a command line. This allows you to deploy to your network using a startup script. This will ensure that when you create a new virtual machine from the template library that it installs the specified anti-virus software, helping you ensure that all new virtual machines are properly protected. See also Best Practice guide to running Sophos on virtual systems
By default, setup.exe is located in the root directory of each update location. In Enterprise Console this is \\servername\Sophos Update\CIDs\Sxxx\SAVSCFXP
NOTE: The setup.exe file version that comes with the standalone installer package of Sophos Endpoint Security and Control does not support extra parameters.
Example: SETUP [-mng yes|no] [-scf] [-crt R] [-hmpa] [-updp <path>] [-user <username>] [-pwd <password>] [-mngcfg <RMS config path>] [-compname <computername>] [-compdesc <computerdescription>] [-domain <domainname>] [-G <groupname>] -s -ni -?
Installs Sophos Exploit Prevention Notes:
Specify a computer name to override the one used in Windows. This name will appear in Enterprise Console.
Specify a computer description to override the one used in Windows. This description will appear in Enterprise Console.
Specifies the group (set up in Enterprise Console/ Manager) to which the computer will belong. The path:
Setup.exe can return one of the following values:
Note: If you run an unknown parameter, the following error message will be displayed:
Setup Could not find resource string 122 If you do not click 'OK', this message will close automatically after 60 seconds.
setup.exe requires a directory named 'sau' to exist in the same directory as itself. This directory must contain a valid Sophos AutoUpdate package including manifest.dat (required by setup.exe) and cidsync.upd (required by the AutoUpdate installation).
setup.exe creates the file 'Sophos ES setup.log' in the %TEMP% directory of each installed computer, where information and errors are logged. Information generated by the Windows Installer during the installation of AutoUpdate is also logged here. Each time setup is run, any previous log file is deleted.
The following table shows a few examples on how to construct a command line installation of Sophos endpoint security software.
setup.exe -mng yes -scf -crt R -updp \\myServer\Sophos\CIDs\S000\savscfxp\ -ouser SIhvF6vRtcGyG0mpJWdvIAc= -opwd EIhvI6vRtcEyG0mpKWdvIAc= -s -ni
setup.exe -mng yes -scf -crt R -updp \\myServer\Sophos\CIDs\S000\savscfxp\ -ouser SIhvF6vRtcGyG0mpJWdvIAc= -opwd EIhvI6vRtcEyG0mpKWdvIAc= -s -ni -patch http://myServer/
setup.exe -mng yes -scf -crt R -hmpa -updp \\myServer\Sophos\CIDs\S000\savscfxp\ -ouser SIhvF6vRtcGyG0mpJWdvIAc= -opwd EIhvI6vRtcEyG0mpKWdvIAc= -s -ni -patch http://myServer/
Todos los comentarios enviados son leídos (por una persona), pero no podemos contestar a preguntas técnicas específicas. Si necesita soporte técnico, publique una pregunta en nuestra comunidad. Como alternativa, en el caso de los productos con licencia, abra una solicitud de soporte.