This article explains how to create a standalone or custom installer package, or off-site installer, that will install endpoint software, without needing an active connection to the updating server or Sophos.
Applies to the following Sophos product(s) and version(s) Enterprise Console 5.1.0 and above
If you wish to create a package that includes one or more preconfigured policies, you will need to export each policy (using ExportConfig.exe) into a distribution point. These XML files must then be applied to the distribution point (Using ConfigCID.exe).
Refer to: Using ExportConfig.exe to create XML configuration files and Using ConfigCID.exe to implement configuration file changes for further details.
Note: The updating policy (sauconf.xml) cannot be used in conjunction with this tool.
"%programfiles%\Sophos\Enterprise Console\exportconfig.exe" -type AU -policy [PolicyName] -output "%userprofile%\Desktop\savinst\SAVSCFXPXML\sau\sauconf.xml"
"%programfiles%\Sophos\Enterprise Console\SUM\configcid.exe" "%userprofile%\Desktop\savinst\SAVSCFXPXML"
See also Command line parameters used by Setup.exe if you would like to customize the setup parameters. For the purpose of this article WinRAR will be used, but any other tool that accomplishes the same job is acceptable.
Run the self-extracting installer on all machines where SESC is to be deployed.
* Known issue
If you attempt to install SAV via a ready made installer created by Sophos Deployment Packager and the logged on user name is made up of double-byte characters (e.g. Japanese, Chinese) then the install does not continue.
No errors are generated but nothing seems to happen. The files do get extracted to the %temp%/cid_packager_temp directory but the install never occurs. There is no sign of SAU and nothing is logged to the event logs.
Every comment submitted here is read (by a human) but we do not reply to specific technical questions. If you need technical support please post a question to our community. Alternatively for licensed products open a support ticket.