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
Testing packages
It is important to test packages before you deploy them to end users to ensure
proper functionality. You should test package installation and deployment in an
isolated, controlled environment. One to two test computers should be sufficient
to conduct testing.
Although some error checking occurs during the build process, some errors cannot
be detected until installation. This is especially true if the package includes a
product that requires a third-party product or if the package includes a custom
command.
During installation, Symantec Packager checks for product conflicts and verifies
that required products are present on the target computer. The installation fails
if Symantec Packager encounters a conflict that it cannot resolve. You should test
packages to verify that product requirements are met and that the installation
sequence is correct.
You should also open each installed program to ensure that it functions correctly.
Ensure that the features that you want are present. This step is especially
important if you customize a product to reduce the installation footprint. Product
testing ensures that you have not overlooked an important feature. Once you
thoroughly test the package, you can deploy it to users.
Creating custom installation packages
Testing packages
40