Symantec 14541094 - pcAnywhere Host & Remote User manual

Symantec™ Packager
Implementation Guide

2
Symantec™ Packager Implementation Guide
The software described in this book is furnished under a license agreement and may be
used only in accordance with the terms of the agreement.
Documentation version 1.3
Copyright Notice
Copyright © 2004 Symantec Corporation.
All Rights Reserved.
Any technical documentation that is made available by Symantec Corporation is the
copyrighted work of Symantec Corporation and is owned by Symantec Corporation.
NO WARRANTY. The technical documentation is being delivered to you AS-IS, and
Symantec Corporation makes no warranty as to its accuracy or use. Any use of the
technical documentation or the information contained therein is at the risk of the user.
Documentation may include technical or other inaccuracies or typographical errors.
Symantec reserves the right to make changes without prior notice.
No part of this publication may be copied without the express written permission of
Symantec Corporation, 20330 Stevens Creek Blvd., Cupertino, CA 95014.
Trademarks
Symantec and the Symantec logo are U.S. registered trademarks of Symantec Corporation.
Microsoft, MS, Windows, Windows NT, Word, and the Office logo are either registered
trademarks or trademarks of Microsoft Corporation in the U.S. and/or other countries.
Other brands and product names mentioned in this manual may be trademarks or
registered trademarks of their respective companies and are hereby acknowledged.
Printed in the United States of America.
10987654321

Contents
Chapter 1 Introducing Symantec Packager
About Symantec Packager .................................................................................... 7
What you can do with Symantec Packager ........................................................ 8
Customize standard product installations ................................................. 8
Include custom commands with product installations ........................... 9
Install multiple products at once ..............................................................10
Reuse product installations in different packages ................................. 10
How Symantec Packager works .........................................................................11
About the Import Products phase .............................................................12
About the Configure Products phase ........................................................ 13
About the Configure Packages phase ....................................................... 15
About the Deploy Packages phase .............................................................16
Where to find more information ....................................................................... 17
Accessing online Help ................................................................................. 17
Accessing the Symantec technical support Web site .............................17
Chapter 2 Installing Symantec Packager
System requirements .......................................................................................... 19
System requirements for Symantec Packager ........................................ 19
System requirements for installation packages ..................................... 20
User rights requirements ........................................................................... 20
Installing Symantec Packager ........................................................................... 21
Installing Symantec Packager from the installation CD .......................21
Starting the Symantec Packager installation program manually ....... 22
Uninstalling Symantec Packager ...................................................................... 22
Chapter 3 Symantec Packager basics
Opening Symantec Packager after installation .............................................. 25
Updating Symantec Packager ............................................................................ 26
Changing Symantec Packager Preferences and view options ...................... 26
Changing Symantec Packager data folders ............................................. 27
Listing supported product .msi files on the Deploy Packages tab ....... 28
Showing or hiding the Symantec logo ......................................................28
Changing the appearance of icons in Symantec Packager .................... 28
Accessing commands in Symantec Packager ..................................................29

4Contents
Chapter 4 Importing products in Symantec Packager
About importing products .................................................................................. 31
Importing product modules ............................................................................... 32
Deleting products from Symantec Packager ................................................... 33
Chapter 5 Configuring custom products
About configuring custom products ................................................................. 35
Working with custom products ......................................................................... 37
Creating custom products .......................................................................... 37
Viewing product details .............................................................................. 38
Deleting custom products .......................................................................... 39
Configuring custom products ............................................................................ 39
Selecting product features ......................................................................... 39
Setting product installation options ......................................................... 41
Adding or removing configuration files ................................................... 42
Building and testing custom products ............................................................. 44
Building custom products .......................................................................... 44
Testing custom products ............................................................................ 45
Chapter 6 Configuring custom commands
About configuring custom commands ............................................................. 47
Working with custom commands ..................................................................... 49
Creating custom commands ....................................................................... 49
Viewing custom command details ............................................................ 50
Deleting custom commands ....................................................................... 50
Configuring custom commands ........................................................................ 51
Specifying command-line parameters and switches ............................. 52
Including files in a command ..................................................................... 54
Specifying operating system support ....................................................... 55
Building and testing custom commands .......................................................... 57
Building custom commands ....................................................................... 57
Testing custom commands ........................................................................ 57
Chapter 7 Configuring installation packages
About configuring packages .............................................................................. 59
Working with package definitions .................................................................... 61
Creating package definitions ..................................................................... 61
Viewing package definition details ........................................................... 62
Deleting package definitions ..................................................................... 62

5Contents
Configuring package definitions ....................................................................... 63
Adding products and commands to a package definition ..................... 63
Changing the installation sequence ..........................................................65
Setting package installation options ........................................................ 66
Building and testing packages ...........................................................................77
Building packages ........................................................................................ 77
Testing packages .......................................................................................... 78
Chapter 8 Deploying installation packages
About deploying packages ..................................................................................79
Installing packages on the local computer ......................................................80
Using the Package Deployment Tool ................................................................ 81
Package Deployment Tool requirements ................................................. 82
Specifying the packages that you want to deploy .................................. 82
Selecting target computers ........................................................................83
Entering deployment authentication information ................................. 86
Viewing deployment status information ................................................. 87
Deploying packages with other programs ....................................................... 90
Glossary
Index

6Contents

Chapter 1
Introducing Symantec
Packager
This chapter includes the following topics:
■About Symantec Packager
■What you can do with Symantec Packager
■How Symantec Packager works
■Where to find more information
About Symantec Packager
Symantec Packager lets you create, modify, and build custom installation
packages that you distribute to target systems. You can use Symantec Packager
to tailor installations to fit your corporate environment by building packages
that contain only the features and settings that your users need.
Symantec products that are included in installation packages are protected by
copyright law and the Symantec license agreement. Distribution of these
packages requires a license for each user who installs the package.
Note: Symantec Packager runs on Windows NT/2000/2003 Server/XP
Professional platforms only. However, installation packages created with
Symantec Packager can be installed on all Microsoft 32-bit platforms except for
Windows 95/NT 3.5.x.

8Introducing Symantec Packager
What you can do with Symantec Packager
What you can do with Symantec Packager
Symantec Packager gives you the flexibility to select only the features that you
require, which lets you reduce the deployment size and the installation
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 1-1 lists examples of how you can use Symantec Packager.
See “Configuring custom products” on page 35.
Table 1-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.

9Introducing Symantec Packager
What you can do with Symantec Packager
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.
Examples of custom commands include running executable files, Microsoft
Software Installer (.msi) files, batch files, and so on. If you can run a command
from the command line, you can create a custom command for it.
In addition to running programs from the command line, you can also create a
custom command that copies files to the end user’s system.
Table 1-2 lists examples of how you can use custom commands.
See “Configuring custom commands” on page 47.
Table 1-2 Examples of custom commands
Goal Solution
Execute a command on the target
system.
If the file or command that you want to execute is
already on the target system, you can specify the
command-line argument to execute it.
For example, you want to uninstall a program on the
target system before you install a new version. You
specify the command-line argument and switches
that execute the uninstallation for that program.
Copy files to the target system. Symantec Packager lets you include files of any type
in a custom command. You can also specify where to
copy those files on the target system.
For example, you want to roll out an updated file for
an application that you use. You include the file in a
custom command and specify the destination on the
target system.
Copy a file and execute it on the
target system.
If the file that you want to execute is not already on
the target system, you include the file in the custom
command, the destination location on the target
system, and the command-line argument to execute
that file on the target system.
For example, you want to include a text file in a
package so that it displays at the end of the
installation. You include the text file in a custom
command and specify a command-line argument that
opens that text file in Notepad.

10 Introducing Symantec Packager
What you can do with Symantec Packager
Install multiple products at once
Symantec Packager lets you combine multiple product installations into one
installation package to reduce installation complexity and minimize
deployment costs. In addition to Symantec products, you can include third-party
programs, command-line arguments, batch files, and so on.
See “Configuring installation packages” on page 59.
Reuse product installations in different packages
Symantec Packager lets you reuse your custom product installations and custom
commands in other installation packages. You can reuse and combine product
installations and custom commands to achieve different goals.
For example, you might want to deploy a Symantec pcAnywhere host to all of
your users, but you first need to uninstall the previous version. A subset of your
client systems may also require a service pack to address a security issue.
Another group of users may require an upgraded version of their antivirus or
firewall product. You can create multiple packages that contain the custom
commands and product installations that you need to accomplish this goal.
Figure 1-1 shows an example of how you can reuse components in multiple
packages.
Figure 1-1 Reusing product installations in different packages
See “Configuring installation packages” on page 59.
Package 1
Custom command to
uninstall previous version of
pcAnywhere
Custom command to
install antivirus product
Custom command to
install service pack
Package 2 Package 3
pcAnywhere host

11Introducing Symantec Packager
How Symantec Packager works
How Symantec Packager works
Symantec Packager uses a phased approach for creating custom installation
packages. Each phase depends on the output of the previous phase.
Figure 1-2 shows the process for creating and deploying packages.
Figure 1-2 Overview of Symantec Packager phases
The following process outlines how the Symantec Packager phases build upon
one another to let you create custom installation packages:
■Import product modules into Symantec Packager
If the product that you want to customize provides a product module,
Symantec Packager automatically imports it. This process extracts the
product installation binary files and the product template. The product
template details the feature requirements and conflicts, which makes it
possible to create custom installations of the product.
See “About the Import Products phase” on page 12.
To create a custom installation for an unsupported product, you must use a
custom command.
See “About the Configure Products phase” on page 13.
■Configure products and commands
In the Configure Products phase, you can select the features that you want
your users to have and set the default installation options for each product.
You also have the option to create custom commands to include in a
package. For example, if you want to include a third-party program or batch
file in a package, create a custom command for that program.
See “About the Configure Products phase” on page 13.
Import
Products
Configure
Products
Configure
Packages
Deploy
Packages
Configure
Commands

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.

13Introducing Symantec Packager
How Symantec Packager works
Figure 1-2 shows the process for importing a product module.
Figure 1-3 Import Products process
The product template files are the building blocks that all other phases
reference. They make it possible to customize products and eventually build
installation packages.
After you import a product in Symantec Packager, you customize that product
in the Configure Products phase so that you can include it in an installation
package.
See “Importing products in Symantec Packager” on page 31.
To deploy a Symantec or third-party product that does not provide a product
module (.pmi) file, you must create a custom command that contains the product
installation and include that custom command in a package installation.
See “Configuring custom commands” on page 47.
About the Configure Products phase
When a product is designed to take advantage of Symantec Packager, it gives
you the flexibility to select the features that you want your users to have. It also
lets you preconfigure installations with the settings that best match your
software deployment needs.
If you want to install a product that was not designed to be used with Symantec
Packager, you can still include that product in an installation package by
creating a custom command. You create custom products and custom
commands in the Configure Products phase.
After completing the Configure Products phase, the products and commands
that you customize are available to include in installation packages. You
configure installation packages in the Configure Packages phase.
See “Configuring custom products” on page 35.
See “Configuring custom commands” on page 47.
Product
module (.pmi)
file
Contains
product
installation
binary files
Contains
product
template (.pdt)
file
Import
Products
process
Symantec Packager
copies product
installation binaries
to hard disk
Product template
displays on Import
Products tab

14 Introducing Symantec Packager
How Symantec Packager works
Overview of custom products
During the Configure Products phase, you can customize a product so that it
contains only the features and options that you want to include. To do this, you
create product configuration (.pcg) files.
On the Configure Products tab, you create a new product configuration file that
is based on a product that you imported in the Import Products phase. After you
select the product features and options that you want to include and specify a
file name, Symantec Packager saves this file as a product configuration file. The
product configuration file, which displays on the Configure Products tab,
references its corresponding product template file on the Import Products tab.
When you build the product configuration file, Symantec Packager creates a
Microsoft Software Installer (.msi) file, which is used in an installation package.
Unlike the product configuration file, the product .msi file does not reference
and is not dependent upon any Symantec Packager files.
Figure 1-4 shows the process for creating custom products.
Figure 1-4 Configure Products process for custom products
See “Configuring custom products” on page 35.
Overview of custom commands
During the Configure Products phase, you can create custom commands that let
you further customize your installation packages. To do this, you create
command configuration files. A command configuration file is the same as a
product configuration (.pcg) file except that the command configuration file
does not reference a product template (.pdt) file.
On the Configure Products tab, you create a new custom command and specify
its parameters. Like a product configuration file, Symantec Packager saves this
file with a .pcg extension. The command configuration file, which displays on
the Configure Products tab, lists the command-line arguments for the custom
Product
configuration
(.pcg) file
Lists features
and options
that you
selected
Refers to
product
template (.pdt)
file
Configure
Products build
process
Symantec Packager
displays saved .pcg
file on Configure
Products tab
Symantec Packager
creates .msi file,
which is used in an
installation package

15Introducing Symantec Packager
How Symantec Packager works
command and references the locations of any files that you included in the
custom command.
When you build the command configuration file, Symantec Packager creates a
self-extracting executable (.exe) file, which is used in an installation package.
Unlike the command configuration file, the command .exe file does not
reference and is not dependent upon any Symantec Packager files.
Figure 1-5 shows the process for creating custom commands.
Figure 1-5 Configure Products process for custom commands
See “Configuring custom commands” on page 47.
About the Configure Packages phase
During the Configure Packages phase, you select the products and custom
commands that you want to include in an installation package. To do this, you
create package definition (.pkg) files.
If your product supports .msi deployment and you are configuring a single
product installation, package creation is optional. However, a package definition
gives you more options for customizing the installation such as configuring
restart and rollback options and adding custom support information. Symantec
Packager supports deployment of pcAnywhere .msi files only.
On the Configure Packages tab, you create a new package definition file by
selecting from the product configuration files and custom commands that you
customized during the Configure Products phase.
After you select the products and custom commands that you want to include in
the installation package and specify a file name, Symantec Packager saves this
file as a package definition (.pkg) file. The .pkg file, which displays on the
Configure Packages tab, references the .pcg files that it contains.
Product
configuration
(.pcg) file
Lists the
command-line
arguments and
switches
Refers to
optional files
Custom
command build
process
Symantec Packager
displays saved .pcg
file on Configure
Products tab
Symantec Packager
creates .exe file,
which is used in an
installation package

16 Introducing Symantec Packager
How Symantec Packager works
When you build the .pkg file, Symantec Packager creates an .exe, which is stored
in the deployment folder that is specified in Symantec Packager Preferences. It
also displays the .exe on the Deploy Packages tab.
Figure 1-6 shows the process for configuring and building packages.
Figure 1-6 Configure Packages process
See “Configuring installation packages” on page 59.
About the Deploy Packages phase
During the Deploy Packages phase, you select the installation packages that you
want to deploy to your users. To do this, you copy the necessary files from the
Deploy Packages tab for use with deployment tools that you already use. You can
also deploy installation packages directly from the Deploy Packages tab using a
Symantec-supplied deployment tool.
The package .exe files built during the Configure Packages phase appear
automatically on the Deploy Packages tab. The command .exe files that
Symantec Packager creates as part of the Configure Products build process are
not supported for deployment and, therefore, do not appear on the Deploy
Packages tab. (They are for testing purposes only.)
You can use the product .msi files that Symantec Packager creates as part of the
Configure Products build process for testing purposes. Product .msi files are not
supported automatically for deployment (only Symantec pcAnywhere .msi files
are automatically supported for deployment). You can configure Symantec
Packager to list supported product .msi files on the Deploy Packages tab.
See “Listing supported product .msi files on the Deploy Packages tab” on
page 28.
The package .exe files that appear on the Deploy Packages tab do not reference
and are not dependent upon any Symantec Packager files.
See “Deploying installation packages” on page 79.
Package
definition
(.pkg) file
Refers to one or
more .pcg files
Refers to one or
more
configuration
or optional files
Configure
Packages build
process
Symantec Packager
displays saved .pkg
file on Configure
Packages tab
Symantec Packager
creates .exe file,
which displays on
Deploy Packages tab

17Introducing Symantec Packager
Where to find more information
Where to find more information
If you need more information about Symantec Packager, you can access the
online Help. In addition, more information about Symantec Packager may be
available on the Symantec Web site.
For product-specific information about how to use Symantec Packager to create
or deploy a custom product installation, see your Symantec product
documentation.
Accessing online Help
The Symantec Packager online Help system has general information and step-
by-step procedures to help you create installation packages.
To access online Help
◆Do one of the following:
■In the Symantec Packager main window, on the Help menu, click Help
Topics.
■In any Symantec Packager window, press F1.
Accessing the Symantec technical support Web site
If you are connected to the Internet, you can visit the Symantec technical
support Web site for additional information about Symantec Packager.
To access the Symantec technical support Web site
◆In your Internet browser, type the following Web address:
http://www.symantec.com/techsupp

18 Introducing Symantec Packager
Where to find more information

Chapter 2
Installing Symantec
Packager
This chapter includes the following topics:
■System requirements
■Installing Symantec Packager
■Uninstalling Symantec Packager
System requirements
Before you install Symantec Packager, ensure that your computer meets the
system requirements. Review the Readme file on the installation CD for any
known issues.
System requirements for Symantec Packager
Symantec Packager runs only on Microsoft 32-bit operating systems and has the
following system requirements:
■Supported operating systems:
■Windows NT Workstation 4.0/Server 4.0 with Service Pack 6a
■Windows 2000 Professional/Server with Service Pack 2
■Windows 2003 Server
■Windows XP Professional
■Microsoft Internet Explorer 6.x or later
■Windows Installer 2.0
If Windows Installer 2.0 is not present, Symantec Packager installs it during
installation.

20 Installing Symantec Packager
System requirements
■Pentium II 300-MHz processor (or faster)
■64 MB RAM (128 MB recommended)
■60 MB disk space
■CD-ROM or DVD-ROM drive
System requirements for installation packages
Although Symantec Packager runs only on Windows NT/2000/2003 Server/XP,
packages that you create using Symantec Packager can be installed on the
following operating systems:
■Windows NT 4.0 with Service Pack 6a
■Windows 98
■Windows Millennium Edition (Me)
■Windows 2000
■Windows 2003 Server
■Windows XP Home Edition/Professional Edition
Packages that contain only custom commands might run on additional
operating systems. However, installed packages are supported on Microsoft 32-
bit systems only.
The specific system requirements for packages depend on the package contents
and options. The hardware requirements for installation packages vary
depending on the package contents.
User rights requirements
Symantec Packager requires administrator rights for installation on Windows
NT/2000/2003 Server/XP.
Windows XP restricts users who are assigned to limited user or guest accounts
from installing or uninstalling software, changing system-wide settings, or
adding, editing, or deleting user accounts. For optimal performance, log on as a
user with administrator rights when you run Symantec Packager on Windows
XP.