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
Selecting product features
Symantec Packager lets you customize product installations by including the
features that you want and removing the features that you do not need. The
product size and installed size change, depending on the features that you choose.
Some features in pcAnywhere have dependencies on other components. Although
Symantec Packager has a level of built-in dependency checking, it is possible to
build a pcAnywhere installation package that does not include all required files.
As you select product features to include or exclude from a package, you should
read the feature descriptions that are provided in the Product Editor window on
the Features tab. The feature descriptions provide information about feature
dependencies.
Table 2-3 lists some of the key product dependencies.
Table 2-3
Symantec pcAnywhere product dependencies
DependencyFeature
Required if you want to let users modify configuration
settings.
Exclude pcAnywhere Manager if you want to include
integrity management.
pcAnywhere Manager
Requires at least one communication protocol.Remote
Requires a caller configuration file (.cif) if you
configure the product to start a host automatically at
startup.
Requires at least one authentication type.
Requires at least one communication protocol.
Host
Required for all custom product installations.Remote Control
Requires at least one communication protocol.File Transfer
Requires at least one communication protocol.Remote Management
Requires at least one communication protocol.Chat
Required for all custom product installations.Authentication
Required for all custom product installations.Communication protocols
Creating custom installation packages
Customizing product settings
20