Symantec Packager, Implementation Manual

Page: 12 / 98

12 Introducing Symantec Packager
How Symantec Packager works
■
Configure the installation package
In the Configure Packages phase, you can use the product configurations
and custom commands that you created in the Configure Products phase
and add them to a package. You can further customize the package by
setting package installation options, product installation order, and other
settings.
When you build a package in the Configure Packages phase, Symantec
Packager creates an installation file that incorporates the product,
command, and package options that you specified.
See
“About the Configure Packages phase” on page 15.
■
Deploy the package
In the Deploy Packages phase, you can deploy packages to your users
through the Package Deployment Tool, the Web-based Deployment Tool, or
a third-party deployment tool, such as Microsoft Systems Management
Server (SMS). The Deploy Packages tab holds the packages that you create.
See
“About the Deploy Packages phase” on page 16.
About the Import Products phase
Symantec releases product module (.pmi) files for products that take advantage
of Symantec Packager functionality, such as Symantec pcAnywhere. Product
module files are comprised of all of the files that are required to recreate a
product installation. These files include a product template (.pdt) file and the
installation binary files for the Symantec product. The product template
contains all of the rules about product feature conflicts and dependencies. It
also tracks the location of the installation binary files on your computer.
When you import a product module, Symantec Packager extracts the product
template from the product module file and displays the product template file on
the Import Products tab. It also copies the product’s installation binary files to
your hard disk.