Building Product Installations And Packages; Building A Product Configuration File - Symantec PCANYWHERE - ADMINISTRATOR GUIDE V12.1 Administrator's Manual

38 Creating custom installation packages

Building product installations and packages

Building product installations and packages

Building a product configuration file

4 Click Open.
The Estimated package size changes to reflect the product or command that
you include.
5
Repeat 2 through
6
In the Package Editor window, do one of the following:
Click OK to save your changes and close the Package Editor window.
Click Apply to save your changes and continue the package definition.
7
If prompted, type a file name, and then click Save.
After you define the contents and installation options for the package definition
file, you must build the package definition to create the installation file. When
you build a package, Symantec Packager creates a self-extracting .exe file that
incorporates the product, command, and package options that you specified.
Alternatively, Symantec Packager lets you build a product configuration file,
which creates a Microsoft Installer (.msi) file for a single product installation.
Building a product configuration file lets you create an .msi file that you can use
for testing or installation. Symantec Packager supports MSI installation for
pcAnywhere product modules only. You do not need to build a product
configuration file to include it in a package.
Symantec Packager stores the .msi files in the Symantec Packager data directory.
You can view these files on the Deploy Packages tab if you edit the Symantec
Packager preferences to list supported .msi files.
You can use an industry-standard, third-party deployment tool to deploy the
pcAnywhere .msi file. The Symantec Packager Deployment Tool does not support
deployment of .msi files.
4 to add more products or custom commands.