Symantec Packager, Implementation Manual

Page: 8 / 98

8 Introducing Symantec Packager
What you can do with Symantec Packager
footprint. It also lets you tailor products to adhere to your security policy, which
lets you give users full access to all features or limit access where appropriate.
Customize standard product installations
Typically, a product installation lets you select standard options, such as the
user and company name, installation directory, and whether the installation is
compact or complete. Although these options offer some flexibility, they are not
custom installations. Symantec Packager lets you select only the features and
options that you want your users to have, which lets you create a true custom
installation.
Table 3-1 lists examples of how you can use Symantec Packager.
See “Configuring custom products” on page 35.
Include custom commands with product installations
If a product that you want to deploy is not supported by Symantec Packager, you
can create a custom command that contains the product installation and include
that custom command in a package installation.
Table 3-1 Examples of product customization options
Goal Solution
Reduce deployment bandwidth
and application footprint. Symantec Packager lists optional and required
features so that you can select minimal features for
low-bandwidth deployments. Fewer features also
decrease the application footprint and memory usage
on the target system.
Tailor installation to specific
users. Once you import a product in Symantec Packager,
you can customize that product into as many
different installations as you need.
For example, for your administrator users, you can
include all features. For temporary personnel or
other users who should have limited access, you can
exclude the features that you do not want them to
use.
Reduce installation complexity. Relying on end users to configure product options
can result in lost productivity and increased costs for
support personnel. Symantec Packager lets you
include preconfigured data files so that you do not
have to configure the product manually after
deployment.