12.1

Table 2-1
Package creation process
DescriptionTask
Product modules contain the installation binary and product
template files that are needed to create a custom installation
of the product.
See “Importing a product module” on page 18.
Import product modules into
Symantec Packager.
You can select the features that you want your users to have,
add preconfigured data and configuration files, and set
default installation options for each product.
See “Customizing product settings” on page 18.
Configure products.
Custom commands let you add additional functionality that
is not supported in the product templates, such as including
a third-party program or batch file.
See “Creating a custom command” on page 35.
Configure commands that
you want to include in a
package.
You can bundle one or more product configurations and
custom commands in a package. You can further customize
the package by setting package installation options, product
installation order, and other settings.
See “Creating installation packages” on page 36.
Configure packages.
When you build a package, Symantec Packager creates an
installation 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.
See “Building product installations and packages” on page 38.
Build custom products or
packages.
You should test packages before deploying them to end users
to ensure proper functionality.
See “Testing packages” on page 40.
Test the package.
The Deploy Packages tab holds the packages that you create,
which you can deploy to your users. Symantec provides a
Package Deployment tool in Symantec Packager and a
Web-based deployment tool on the pcAnywhere CD. You
can also use your current deployment tools.
See “About deployment” on page 41.
Deploy the package.
17Creating custom installation packages
How Symantec Packager works