12.1
Table Of Contents
- Symantec pcAnywhere™ Administrator's Guide
- Technical Support
- Contents
- 1. Planning a migration and upgrade strategy
- 2. Creating custom installation packages
- 3. Deploying Symantec pcAnywhere custom installations
- 4. Performing centralized management
- About centralized management
- Managing pcAnywhere hosts remotely
- Installing the pcAnywhere Host Administrator tool
- Adding the Host Administrator snap-in to MMC
- Creating a configuration group
- Adding computers to a configuration group
- Configuring administrator host and remote connection items
- Configuring a host item in pcAnywhere Host Administrator
- Distributing pcAnywhere configuration files
- Managing hosts in a configuration group
- Integrating with Microsoft Systems Management Server
- About the Microsoft Distributed Component Object Model (DCOM)
- About centralized logging
- 5. Integrating pcAnywhere with directory services
- 6. Managing security in Symantec pcAnywhere
- Index
Preserving existing configuration settings
If you are installing a package over an existing version of pcAnywhere (from
version 10.0 and later), Symantec Packager lets you preserve existing registry,
host, remote, and caller configuration settings.
This option is available for silent and passive mode installations only. You must
configure installation mode settings at the package level.
See “Creating installation packages” on page 36.
To preserve existing configuration settings
1
In the Symantec Packager window, on the Configure Products tab, do one of
the following:
■ Create a new product configuration.
■ Double-click an existing product to edit it.
2
In the Product Editor window, on the Installation Options tab, double-click
Preserve existing configuration settings.
3
In the Preserve existing configuration settings window, check Preserve
existing configuration settings.
4
Click OK.
5
In the Product Editor window, do one of the following:
■ Click OK to save your changes and close the Product Editor window.
■ Click Apply to save your changes and continue the product configuration.
6
If prompted, type a file name, and then click Save.
Creating a custom command
In addition to creating custom products, you can create custom commands to
include in your packages. Examples of custom commands include batch files,
third-party executables, command-line arguments, or simple file copies. Custom
commands let you simplify application deployment by including multiple tasks
in one package. Once defined, you can reuse custom commands in different
packages.
When you create a custom command, Symantec Packager creates a command
configuration file. A command configuration file is a generic product configuration
file that does not reference a product template file. Therefore, custom commands
do not require you to import a product module. The build process for custom
commands creates a self-extracting executable (.exe) file, which can be tested
35Creating custom installation packages
Creating a custom command