4
Sophos Deployment Packager
2 About Deployment Packager
The Deployment Packager creates a single self-extracting archive file from a set of Sophos endpoint setup files, for installing Endpoint Security and Control on Windows endpoints. The packaged file includes configuration options such as silent/interactive installation, installation package choices and setup parameters, update path/credentials and endpoint group membership.
Packages created with the Deployment Packager always attempt to remove other potentially-clashing protection software when installed. For encryption, other potentially-clashing encryption software can be detected, but must be removed manually.
It may be necessary for you to produce several packages, each meeting the requirements of different endpoint types.
You can run the Deployment Packager tool through either its graphical user interface (GUI) or command-line interface (CLI).
■
■
The GUI is easier for one-off deployments.
The CLI is more versatile for repeated deployments.
A string to invoke the command line version with options can be stored in a text file, or regularly run from a scheduled batch file, ensuring that the installation packages are always up-to-date.
So, if you are managing large numbers of computers where there is a need for frequent installation on endpoints, then the CLI is preferable.
2.1 Deployment Packager known issues and limitations
■ If you attempt to install Sophos Anti-Virus using a ready-made installer created by Sophos
Deployment Packager and the logged on user name contains double-byte characters (for example, Japanese, Chinese), the installation does not continue.
When the installer is run, the setup files are extracted to the %temp%/cid_packager_temp directory, but the installation does not continue. No errors are displayed or logged in the event logs.
Workaround: Log on as a user with no double-byte characters in the user name.
■ A "packaging failed" error message may be displayed when you try to create a package using command-line with an obfuscated password, -opwd command. If the error is displayed, ensure the obfuscated password is correct. If it is accurate and continues to display the error, enter a plain text password using the -pwd command or use the Deployment Packager user interface.
