Symantec PcAnywhere™ Administrator's Guide Pc Anywhere 12.0 Pca Admin

User Manual: symantec pcAnywhere - 12.0 - Administrator's Guide Free User Guide for Symantec pcAnywhere Software, Manual

Open the PDF directly: View PDF .
Page Count: 109

Download
Open PDF In Browser	View PDF

Symantec pcAnywhere™
Administrator's Guide

Symantec pcAnywhere™ Administrator's 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 12.0

Legal Notice
Copyright © 2006 Symantec Corporation.
All rights reserved.
Federal acquisitions: Commercial Software - Government Users Subject to Standard License
Terms and Conditions.
Symantec, the Symantec Logo, Symantec pcAnywhere, Symantec Packager, ColorScale,
SpeedSend, and LiveUpdate are trademarks or registered trademarks of Symantec
Corporation or its affiliates in the U.S. and other countries.
Apple and Mac OS are registered trademarks of Apple Computer, Inc. Java is a trademark
of Sun Microsystems, Inc. in the United States and other countries. Microsoft, Windows,
Windows NT, MS-DOS, and the Windows logo are registered trademarks of Microsoft
Corporation in the United States and other countries. Linux is a registered trademark of
Linus Torvalds. SUSE and its logo are registered trademarks of SUSE AG. The Red Hat
trademark and logo are trademarks of Red Hat, Inc. in the United States and other countries.
SSH and Secure Shell are trademarks of SSH Communications Security, Inc. Additional
company and product names may be trademarks or registered trademarks of the individual
companies and are respectfully acknowledged.
The product described in this document is distributed under licenses restricting its use,
copying, distribution, and decompilation/reverse engineering. No part of this document
may be reproduced in any form by any means without prior written authorization of
Symantec Corporation and its licensors, if any.
THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS,
REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT,
ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO
BE LEGALLY INVALID. SYMANTEC CORPORATION SHALL NOT BE LIABLE FOR INCIDENTAL
OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING PERFORMANCE,
OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINED IN THIS
DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE.
The Licensed Software and Documentation are deemed to be "commercial computer software"
and "commercial computer software documentation" as defined in FAR Sections 12.212 and
DFARS Section 227.7202.
Symantec Corporation 20330 Stevens Creek Blvd. Cupertino, CA 95014 USA
http://www.symantec.com

Technical Support
Symantec Technical Support maintains support centers globally. Technical
Support’s primary role is to respond to specific queries about product feature and
function, installation, and configuration. The Technical Support group also authors
content for our online Knowledge Base. The Technical Support group works
collaboratively with the other functional areas within Symantec to answer your
questions in a timely fashion. For example, the Technical Support group works
with Product Engineering and Symantec Security Response to provide alerting
services and virus definition updates.
Symantec’s maintenance offerings include the following:
■

A range of support options that give you the flexibility to select the right
amount of service for any size organization

■

A telephone and web-based support that provides rapid response and
up-to-the-minute information

■

Upgrade insurance that delivers automatic software upgrade protection

■

Global support that is available 24 hours a day, 7 days a week worldwide.
Support is provided in a variety of languages for those customers that are
enrolled in the Platinum Support program

■

Advanced features, including Technical Account Management

For information about Symantec’s Maintenance Programs, you can visit our Web
site at the following URL:
www.symantec.com/techsupp/ent/enterprise.html
Select your country or language under Global Support. The specific features that
are available may vary based on the level of maintenance that was purchased and
the specific product that you are using.

Licensing and registration
If your Symantec product requires registration or a license key, access our technical
support Web page at the following URL:
www.symantec.com/techsupp/ent/enterprise.html
Select your region or language under Global Support, and then select the Licensing
and Registration page.

Customer service
Customer service information is available at the following URL:
www.symantec.com/techsupp/ent/enterprise.html

Select your country or language under Global Support.
Customer Service is available to assist with the following types of issues:
■

Questions regarding product licensing or serialization

■

Product registration updates such as address or name changes

■

General product information (features, language availability, local dealers)

■

Latest information about product updates and upgrades

■

Information about upgrade insurance and maintenance contracts

■

Information about the Symantec Value License Program

■

Advice about Symantec's technical support options

■

Nontechnical presales questions

■

Issues that are related to CD-ROMs or manuals

Maintenance agreement resources
If you want to contact Symantec regarding an existing maintenance agreement,
please contact the maintenance agreement administration team for your region
as follows:
■

Asia-Pacific and Japan: contractsadmin@symantec.com

■

Europe, Middle-East, and Africa: semea@symantec.com

■

North America and Latin America: supportsolutions@symantec.com

Additional Enterprise services
Symantec offers a comprehensive set of services that allow you to maximize your
investment in Symantec products and to develop your knowledge, expertise, and
global insight, which enable you to manage your business risks proactively.
Enterprise services that are available include the following:
Symantec Early Warning Solutions These solutions provide early warning of cyber
attacks, comprehensive threat analysis, and
countermeasures to prevent attacks before they occur.
Managed Security Services

These services remove the burden of managing and
monitoring security devices and events, ensuring
rapid response to real threats.

Consulting Services

Symantec Consulting Services provide on-site
technical expertise from Symantec and its trusted
partners. Symantec Consulting Services offer a variety
of prepackaged and customizable options that include
assessment, design, implementation, monitoring and
management capabilities, each focused on establishing
and maintaining the integrity and availability of your
IT resources.

Educational Services

Educational Services provide a full array of technical
training, security education, security certification,
and awareness communication programs.

To access more information about Enterprise services, please visit our Web site
at the following URL:
www.symantec.com
Select your country or language from the site index.

Contents

Technical Support
Chapter 1

Planning a migration and upgrade strategy
About migrations and upgrades ......................................................
Migrating from pcAnywhere 11.x in Windows NT/2000/2003
Server/XP .......................................................................
Migrating from pcAnywhere 10.x in Windows NT/2000/ 2003
Server/XP .......................................................................
Migrating from pcAnywhere 10.x in Windows 98/Me ....................
Upgrading from pcAnywhere 9.2.x in Windows NT/2000/XP ...........
Upgrading from pcAnywhere 9.2.x in Windows 98/Me ...................
Using Symantec Packager to streamline migrations and upgrades .........

Chapter 2

11
13
13
13
14
14
14

Creating custom installation packages
About Symantec Packager ..............................................................
What you can do with Symantec Packager .........................................
How Symantec Packager works .......................................................
Importing a product module ...........................................................
Customizing product settings .........................................................
Selecting product features .......................................................
Including configuration files ....................................................
Integrity stamping a product configuration .................................
Serializing a pcAnywhere installation ........................................
Managing configuration settings globally ...................................
Setting product installation options ...........................................
Creating a custom command ...........................................................
Creating installation packages ........................................................
Adding products and commands to a package definition ................
Building product installations and packages ......................................
Building a product configuration file ..........................................
Building a package ..................................................................
Testing packages ..........................................................................

17
18
18
20
21
22
24
26
27
30
32
38
39
40
40
41
41
42

Contents

Chapter 3

Deploying Symantec pcAnywhere custom installations
About deployment ........................................................................
About package installation file locations ...........................................
Deploying installation packages using Web-based deployment ..............
About Web-based deployment requirements ................................
Setting up the installation Web server ........................................
Customizing the deployment files .............................................
Testing the installation on the Web server ..................................
Notifying users of the download location ....................................
Deploying pcAnywhere using SMS 2.0 ..............................................
Minimum requirements for SMS deployment ..............................
Deploying with SMS ...............................................................
Using Windows NT/2000/2003 Server/XP logon scripts .......................
Setting up the Windows server ..................................................
Writing the Windows logon script .............................................
Testing the Windows logon script ..............................................
Using NetWare logon scripts ..........................................................
Setting up the Novell NetWare server .........................................
Writing the NetWare logon script ..............................................
Testing the NetWare logon script ...............................................

Chapter 4

43
44
45
45
46
49
53
53
54
55
55
58
58
58
60
60
60
61
62

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 .....................
Importing the package definition file into SMS ............................
About the Microsoft Distributed Component Object Model
(DCOM) ................................................................................
Implementing DCOM in Windows NT/2000/2003 Server/XP ...........
Implementing DCOM in Windows 98/Me ....................................
Modifying DCOM settings ........................................................
About AwShim .......................................................................
About centralized logging ..............................................................

63
63
64
65
65
66
66
69
69
70
71
71
71
72
72
72
73
74

Contents

Monitoring performance using SNMP traps ................................. 74
About the pcAnywhere MIB file ................................................. 75

Chapter 5

Integrating pcAnywhere with directory services
About directory services ................................................................
Using directory services with pcAnywhere ........................................
Configuring the directory servers ....................................................
Configuring the LDAP server ....................................................
Configuring Netscape Directory Server 3.1 ..................................
Configuring Netscape Directory Server 4.0 ..................................
Configuring Novell v5.0 server ..................................................
Configuring Windows Active Directory .......................................
Configuring pcAnywhere to use directory services ..............................
Setting up directory services in pcAnywhere ...............................
Setting up the host computer to use directory services ..................
Setting up the remote computer to use directory services ...............

Chapter 6

77
77
78
78
78
79
80
84
88
88
89
90

Managing security in Symantec pcAnywhere
Controlling access to pcAnywhere hosts ........................................... 91
Limiting connections to specific computer names or IP
addresses ........................................................................ 92
Leveraging centralized authentication in pcAnywhere ................... 93
Protecting session security ............................................................. 97
Maintaining audit trails ................................................................. 99
Implementing policy-based administration ....................................... 99
Implementing Group Policy in Windows 2000/2003
Server/XP ....................................................................... 99
Implementing system policy in Windows 98/Me/NT4 .................. 100
Importing the pcAnywhere administrative template .................... 100
Managing user policies .......................................................... 101

Index

Contents

Chapter

Planning a migration and
upgrade strategy
This chapter includes the following topics:
■

About migrations and upgrades

■

Using Symantec Packager to streamline migrations and upgrades

About migrations and upgrades
Symantec pcAnywhere supports migration from versions 10.x to version 12.0 on
Windows 98/Me/NT/2000/2003 Server/XP. During a migration, pcAnywhere lets
you install over the previous version of the product and preserve user-defined
settings.
Symantec pcAnywhere supports upgrades from version 9.2.x to version 12.0 on
Windows 98/Me/NT/2000/2003 Server/XP. An upgrade lets you install over the
previous version of the product; however, user-defined settings are not
automatically preserved.
A system restart for migrations and upgrades is required only if system files need
to be updated. Symantec pcAnywhere requires a system restart if you are migrating
or upgrading to the new version in Windows 98/Me.
Symantec Packager helps you simplify the process of uninstalling previous versions
or distributing preconfigured settings to multiple users.
See “Using Symantec Packager to streamline migrations and upgrades” on page 14.
Table 1-1 includes information that you can use as a reference in planning your
migration and upgrade strategy.

Planning a migration and upgrade strategy
About migrations and upgrades

Table 1-1

Migration and upgrade strategy matrix

Symantec
pcAnywhere
version

Operating
system

Restart required Data preserved
automatically

11.x

Windows
NT/2000/2003
Server/XP

Host items
Caller items
Remote items
Option sets
Registry settings
AutoTransfer files (must be
converted)
Serial ID sets

10.x

Windows
NT/2000/XP

Host items
Caller items
Remote items
Option sets
Registry settings
AutoTransfer files (must be
converted)

10.x

Windows 98/Me

Yes

Host items
Caller items
Remote items
Option sets
Registry settings
AutoTransfer files (must be
converted)

9.2.x

Windows
NT/2000/XP

Windows 98/Me

Yes

None

Uninstalls
previous version

None

Planning a migration and upgrade strategy
About migrations and upgrades

Migrating from pcAnywhere 11.x in Windows NT/2000/2003 Server/XP
Symantec pcAnywhere supports full migration of the full product version and
host-only version of pcAnywhere 11.x to version 12.0 in Windows
NT/2000/2000/2003 Server/XP.
During the installation, you are prompted to preserve existing configuration
settings. This data includes settings for host, remote, and caller items, as well as
option sets.
Migration of remote-only packages and integrity-checked packages is not
supported.

Migrating from pcAnywhere 10.x in Windows NT/2000/ 2003 Server/XP
Symantec pcAnywhere supports full migration of the full product version and
host-only version of pcAnywhere 10.x to 12.0 in Windows NT/2000/2003
Server/XP.
During the installation, you are prompted to preserve existing configuration
settings. This data includes settings for host, remote, and caller items, as well as
option sets.
AutoTransfer files (.atf) that were created in earlier versions of pcAnywhere are
preserved. However, to use the .atf files in this version of pcAnywhere, you must
convert the .atf files to command queue files.
Migration of remote-only packages and integrity-checked packages is not
supported.

Migrating from pcAnywhere 10.x in Windows 98/Me
Symantec pcAnywhere supports full migration of the full product version and
host-only version of pcAnywhere 10.x to pcAnywhere 12.0 in Windows 98/Me.
During the installation, you are prompted to preserve existing configuration
settings. This data includes settings for host, remote, and caller items, as well as
option sets.
This migration requires a system restart to remove older pcAnywhere system
files. You can use Symantec Packager to streamline the migration process.
See “Using Symantec Packager to streamline migrations and upgrades” on page 14.
Migration of remote-only packages and integrity-checked packages is not
supported.

Planning a migration and upgrade strategy
Using Symantec Packager to streamline migrations and upgrades

Upgrading from pcAnywhere 9.2.x in Windows NT/2000/XP
Symantec pcAnywhere supports upgrades of the full product and host-only
versions of pcAnywhere 9.2.x to version 12.0 in Windows NT/2000/XP.
The upgrade process does not automatically preserve user-defined data. If you
need to upgrade pcAnywhere on multiple computers, you can use Symantec
Packager to create a custom installation package that contains preconfigured
data files.
See “Using Symantec Packager to streamline migrations and upgrades” on page 14.

Upgrading from pcAnywhere 9.2.x in Windows 98/Me
If you are installing pcAnywhere version 12.0 on a Windows 98/Me computer that
has version 9.2.x installed, pcAnywhere prompts you to uninstall the program.
This is required to ensure proper functionality.
To automate this process, you can use Symantec Packager to create a custom
installation package to handle the uninstallation and installation process. You
can also include preconfigured data files in the package and deploy it to other
users.
See “Using Symantec Packager to streamline migrations and upgrades” on page 14.

Using Symantec Packager to streamline migrations
and upgrades
Symantec Packager is an administrator tool that lets you create, modify, and build
custom installation packages that you distribute to target systems. Symantec
Packager is available as an installation option on the pcAnywhere installation
CD.
Symantec Packager helps you streamline the process of migrating or upgrading
from earlier versions of pcAnywhere in the following ways:
The product installation requires you to
Create a custom installation package that
manually uninstall a previous version of the includes a custom command to silently
product.
uninstall the previous version before
installing the product.
The product installation requires you to
restart the computer to complete the
installation process.

Create a custom installation package for the
product installation and configure the
package to install in passive or silent mode.

Planning a migration and upgrade strategy
Using Symantec Packager to streamline migrations and upgrades

The product installation does not support
preservation of preconfigured product
settings.

Create a custom installation package that
includes preconfigured data files that
contain the settings that you need.

See “Using Symantec Packager to streamline migrations and upgrades” on page 14.

Planning a migration and upgrade strategy
Using Symantec Packager to streamline migrations and upgrades

Chapter

Creating custom
installation packages
This chapter includes the following topics:
■

About Symantec Packager

■

What you can do with Symantec Packager

■

How Symantec Packager works

■

Importing a product module

■

Customizing product settings

■

Creating a custom command

■

Creating installation packages

■

Building product installations and packages

■

Testing packages

About Symantec Packager
Symantec Packager lets you create, modify, and build custom installation packages
that you can 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 included in installation packages are protected by copyright
law and the Symantec license agreement. Distribution of packages requires a
license for each user who installs the package.

Creating custom installation packages
What you can do with Symantec Packager

Note: Symantec Packager runs on Windows NT/2000/2003 Server/XP Professional
platforms only. However, installation packages that are created with Symantec
Packager can be installed on all Microsoft 32-bit platforms except for Windows
95/NT 3.51.

What you can do with Symantec Packager
Symantec Packager lets you do the following:
■

Tailor products to adhere to your security policy, giving users full access to
all features, or limiting access where appropriate

■

Reduce deployment bandwidth and application footprint by creating a custom
installation package that contains only the features that your users need

■

Reduce installation complexity by including preconfigured data files

■

Minimize deployment costs and complexity by installing multiple products at
once

■

Simplify application deployment and migration by including custom commands
with product installations

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 2-1 shows the process for creating custom installation packages with
Symantec Packager.
Figure 2-1
Import Products

Overview of Symantec Packager phases
Configure Products

Configure Packages Deploy Packages

Configure Commands

Table 2-1 outlines the process for creating packages.

Creating custom installation packages
How Symantec Packager works

Table 2-1

Package creation process

Task

Description

Reference

Import product modules into Product modules contain the See “Importing a product
Symantec Packager.
installation binary and
module” on page 20.
product template files that
are needed to create a custom
installation of the product.
Configure products.

You can select the features
See “Customizing product
that you want your users to settings” on page 21.
have, add preconfigured data
and configuration files, and
set default installation
options for each product.

Configure commands that
you want to include in a
package.

Custom commands let you
See “Creating a custom
add additional functionality command” on page 38.
that is not supported in the
product templates, such as
including a third-party
program or batch file.

Configure packages.

You can bundle one or more See “Creating installation
product configurations and packages” on page 39.
custom commands in a
package. You can further
customize the package by
setting package installation
options, product installation
order, and other settings.

Build custom products or
packages.

When you build a package,
Symantec Packager creates
an installation file that
incorporates the product,
command, and package
options that you specified.
Alternatively, Symantec
Packager lets you build a
product configuration file,
which creates a Microsoft
Installer (.msi) file for a
single product installation.

See “Building product
installations and packages”
on page 40.

Creating custom installation packages
Importing a product module

Table 2-1

Package creation process (continued)

Task

Description

Reference

Test the package.

You should test packages
See “Testing packages”
before deploying them to end on page 42.
users to ensure proper
functionality.

Deploy the package.

The Deploy Packages tab
See “About deployment”
holds the packages that you on page 43.
create, which you can deploy
to your users. Symantec
provides a Package
Deployment tool in Symantec
Packager and a Web-based
deployment tool on the
pcAnywhere CD. You can also
use your current deployment
tools.

Importing a product module
Product modules are the building blocks for creating packages. Symantec Packager
extracts the product installation binary files and the product template from the
product module. The product template details the feature requirements and
conflicts, making it possible to create custom installations of the product. During
installation, Symantec Packager automatically checks the Packager/Products
folder for product module files and imports them automatically.
Symantec pcAnywhere provides a product module file (Symantec pcAnywhere
.PMI) on the installation CD. If you install Symantec Packager from the
pcAnywhere installation CD, Symantec Packager automatically imports this
product module file.
If no products appear on the Import Products tab when you open Symantec
Packager, you must import the product module manually.
To import a product module

Open Symantec Packager.

In the Symantec Packager window, on the Import Products tab, on the File
menu, click Import New Product.

Creating custom installation packages
Customizing product settings

In the Open dialog box, navigate to the folder that contains the product module
that you want to import.

Select the product module, and then click Open.
Symantec Packager imports the product module and returns you to the Import
Products tab. Depending on the size and complexity of the product module,
the registration process might be lengthy.

Customizing product settings
Symantec Packager creates a default product configuration file (.pcg) for each
product module that you import into Symantec Packager. Each product
configuration file contains the features, installation options, and preconfigured
settings that you want to include for that product. Symantec Packager uses this
information to construct installation packages. You can edit the default product
configuration file or create a new one.
Table 2-2 includes information about the configuration options that are available
in the default pcAnywhere product configuration file.
Table 2-2

Symantec pcAnywhere product configuration options

Tab

Settings

Features

You can customize the following features in
pcAnywhere such as:

Configuration Files

■

User interface (pcAnywhere Manager)

■

Remote components

■

Host components

■

Communications protocols

■

Documentation (online manuals and Help)

■

Symantec installation utilities

The pcAnywhere product template includes default
remote and host configuration items that you can
configure after you install the package or custom
product.
You can add configuration files that you create in
pcAnywhere to the package or custom product
configuration for further customization.

Creating custom installation packages
Customizing product settings

Table 2-2

Symantec pcAnywhere product configuration options (continued)

Tab

Settings

Installation Options

You can customize the following product installation
options for pcAnywhere:
■

Product description

■

Target location

■

Start online registration at startup

■

Host object to use as a template

■

Host object to start with Windows

■

Remote object to use as a template

■

Run LiveUpdate after installation

■

Preserve existing configuration settings

After you select the product features, installation options, and optional
configuration files to include in your custom product, you can build it for testing
purposes. Building the product configuration file creates a Microsoft Installer
(.msi) file. Symantec Packager supports installation of pcAnywhere .msi files only.
See “Building a product configuration file” on page 41.

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.

Creating custom installation packages
Customizing product settings

Table 2-3

Symantec pcAnywhere product dependencies

Feature

Dependency

pcAnywhere Manager

Required if you want to let users modify configuration
settings.
Exclude pcAnywhere Manager if you want to include
integrity management.

Remote

Requires at least one communication protocol.

Host

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.

Remote Control

Required for all custom product installations.

File Transfer

Requires at least one communication protocol.

Remote Management

Requires at least one communication protocol.

Chat

Requires at least one communication protocol.

Authentication

Required for all custom product installations.

Communication protocols

Required for all custom product installations.

To select product features

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.

In the Product Editor window, on the Features tab, do any of the following:
■

Select the product features that you want to include in the custom product.

■

Clear the features that you do not want to include.

■

Click the plus sign next to a feature to select or remove its subfeatures.

Creating custom installation packages
Customizing product settings

Select one of the following:
OK

Saves your changes and closes the Product Editor
window

Apply

Saves your changes and lets you continue the
product configuration

If prompted, type a file name, and then click Save.

Including configuration files
Symantec Packager lets you include preconfigured data or configuration files so
that your users do not have to make configuration changes during or after
installation. For product-specific configurations, you must configure these files
in the product first, and then add them to the Configuration Files tab in Symantec
Packager. Configuration files cannot be edited in Symantec Packager.
For more information, see the Symantec Packager online Help.
The pcAnywhere product template provides the following default configuration
files, depending on the features that you selected on the Features tab:
Symantec Live Update file (LIVEUPDT.HST) Provides the information needed to support
connections to the Symantec LiveUpdate
server to receive automatic product updates
associated with your version of pcAnywhere.
Remote connection item files (.chf)

Provides default settings to support
connections to a host computer over a
modem, network, or direct connection. Also
provides default settings to start a
connection in file transfer or remote
management mode.

Host connection item files (.bhf)

Provides default settings to allow remote
users to connect to the computer over a
modem, network, or direct connection.

Depending on the features that you selected on the Features tab, you can configure
the following files in pcAnywhere and add them to the custom product installation:
Option sets

Lets you configure global options for pcAnywhere to
accommodate unique configuration requirements.

Host Security IDs

Lets you serialize the pcAnywhere installation.

Creating custom installation packages
Customizing product settings

Remote connection item files (.chf) Lets you preconfigure the connection and security
settings needed to connect to another computer
remotely.
For more information, see the Symantec pcAnywhere
User's Guide.
Command queue files

Lets you automate file transfer, command-line, and
end-of-session tasks.
For more information, see the Symantec pcAnywhere
User's Guide.

Host connection item files (.bhf)

Lets you preconfigure the connection and security
settings needed to allow a connection from another
computer.
For more information, see the Symantec pcAnywhere
User's Guide.

Caller files (.cif)

Lets you preconfigure a logon account for users who
connect to the host computer and select an
authentication method to verify their identities. This
information is required to launch a host.
For more information, see the Symantec pcAnywhere
User's Guide.

Symantec pcAnywhere configuration files are located in the following folders:
Windows 2000/2003 Server/XP

\Documents and Settings\All Users\Application
Data\Symantec\pcAnywhere

Windows NT 4.0

\Winnt\Profiles\All Users\Application
Data\Symantec\pcAnywhere

Windows 98/Me

\Windows\All Users\Application
Data\Symantec\pcAnywhere

These folders are hidden by default in the operating system. To browse for the
pcAnywhere configuration files, you must edit the folder options on your operating
system to show hidden files.
You can also add registry key files to control certain pcAnywhere settings. The
registry keys that are contained in the file are added to the system registry on the
target computer when the package or custom product is installed.

Creating custom installation packages
Customizing product settings

Warning: Use caution when configuring a registry key file. An incorrect setting
could make the operating system or product inoperable.
To include a configuration file

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.

In the Product Editor window, on the Configuration Files tab, do one of the
following:
■

Select the type of preconfigured file that you want to add, and then click
Add.

■

Browse to the configuration file that you want to include, and then click
Open. Symantec pcAnywhere configuration files are added to the list. For
other types of configuration files, this replaces the default file with your
preconfigured file.

■

Select the file that you want to remove, and then click Remove.
This removes your preconfigured file and replaces it with the default file
provided by Symantec, if one is available.

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.

If prompted, type a file name, and then click Save.

Integrity stamping a product configuration
You can prevent unauthorized changes to the installed product by using integrity
management. If pcAnywhere detects that a pcAnywhere executable, registry, or
configuration file has been changed in an installed, integrity-stamped package,
pcAnywhere will not run.
If you use integrity management, you must exclude the pcAnywhere Manager
and LiveUpdate features. Once an integrity-stamped package is installed, users
are restricted from changing or updating pcAnywhere in any way, including
installation of software upgrades using LiveUpdate. When updates are needed,
you must create and deploy a new package.
Breaches to integrity, including changes to the registry or adding or deleting files,
can result in denial of service. Use integrity management in conjunction with

Creating custom installation packages
Customizing product settings

policy management and overall strong security practices, such as hardening the
operating system.
See “Implementing policy-based administration” on page 99.
To integrity stamp a product configuration

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.

In the Product Editor window, on the Features tab, click the plus sign next to
Symantec installation utilities to expand the listing.

Select Integrity management.

Select the other features that you want to include or exclude from the product.

On the Installation Options tab, select the product installation options that
you want to use.
See “Setting product installation options” on page 32.

Select one of the following:
OK

Saves your changes and closes the Product Editor
window

Apply

Saves your changes and lets you continue the
product configuration

If prompted, type a file name, and then click Save.

Do one of the following:
■

Build the product.
Building a product configuration file creates an .msi file that contains the
single product.

■

Create a package that includes the product, and then build the package.
Building a package creates a self-extracting .exe file.

See “Building product installations and packages” on page 40.

Serializing a pcAnywhere installation
Symantec pcAnywhere lets you create a custom installation that contains an
embedded security code, or serial ID. This serial ID number must be present on
both the host and remote computers to make a connection.

Creating custom installation packages
Customizing product settings

Serialization involves the following process:
■

In pcAnywhere, generate a serial ID file (.SID).

■

In Symantec Packager, in the Product Configuration Editor, select the feature
components that you want to include, and then add the serial ID configuration
file.

■

Build the package.

■

Deploy and install the package.

Generating a serial ID file
Symantec pcAnywhere lets you generate a security code, or serial ID, which can
be embedded into a custom installation. Serial IDs must be a numeric value between
0 and 4,294,967,296.
To let a remote user connect to one or more host computers that use different
serial IDs, you must include the serial ID for each host computer in the serial ID
file.
To generate a serial ID file

In the pcAnywhere Manager window, on the left navigation bar, click Serial
ID Sets.

On the File menu, click New Item > Advanced.

In the Serial ID Set Properties dialog box, under Limit host connections by
using the following serial IDs, type the serial ID number that you want to use.
Serial IDs must be a numeric value between 0 and 4,294,967,296.

Click Add.

Click OK.
The Serial ID file is added to the right pane under Serial ID Sets.

Creating a serialized installation file
To create a serialized version of pcAnywhere, you must add the serial ID file that
you generate in pcAnywhere to a product definition file in Symantec Packager.
The serial ID is embedded in the product when you build the product or build a
package that contains the product definition.
The custom product installation or package must be installed on the host and
remote computers. To allow a connection between a host and remote computer,
the host and remote computers must have matching serial IDs.

Creating custom installation packages
Customizing product settings

To create a serialized installation file

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.

In the Product Editor window, on the Features tab, do any of the following:
■

Check the product features that you want to include in the custom product.

■

Uncheck the features that you do not want to include.

■

Click the plus sign next to a feature to select or remove its subfeatures.

To configure a custom product installation or package that includes host and
remote features, select Host and Remote. To create separate installations,
select only Host or Remote.

On the Configuration Files tab, click Host Security IDs File (*.SID) , and then
click Add.

Browse to the folder that contains the serial ID file (*.sid) that you generated
in pcAnywhere, select the file, and then click Open.
The serial ID file is added to the list of data and configuration files.

On the Installation Options tab, select the product installation options that
you want to use.
See “Setting product installation options” on page 32.

Select one of the following:
OK

Saves your changes and closes the Product Editor
window

Apply

Saves your changes and lets you continue the
product configuration

If prompted, type a file name, and then click Save.

Do one of the following:
■

Build the product.
Building a product configuration file creates an .msi file that contains the
single product.

■

Create a package that includes the product, and then build the package.
Building a package creates a self-extracting .exe file.

Creating custom installation packages
Customizing product settings

See “Building product installations and packages” on page 40.

Managing configuration settings globally
Symantec pcAnywhere option sets let you manage global settings for host and
remote connections, file transfer, logging, and other functions to improve
performance, enhance security, or manage connections. Symantec pcAnywhere
lets you create multiple option sets to accommodate unique configuration
requirements.
Preconfigured option sets can be used for custom installation packages created
with Symantec Packager. They can also be used as the default preferences for the
local computer.

Configuring an option set in pcAnywhere
Symantec pcAnywhere groups the option set properties by tabs.
Table 2-4 lists the properties that are available.
Table 2-4

Symantec pcAnywhere option set properties

Tab

Description

Host Operation

Controls basic host operations, such as host name and
record settings

Remote Operation

Controls performance and display settings for remote
sessions

Host Communications

Contains customization options for modem and
network connections on the host computer

Remote Communications

Contains customization options for modem and
network connections on the remote computer

Session Manager

Controls basic session options, such as the background
color for the unusable part of the remote desktop, and
lets you view or edit the command prompt exclusion
list

File Transfer

Controls file transfer settings

Event Logging

Enables logging of events that occur during
pcAnywhere sessions

Directory Services

Controls settings for using a directory service to find
hosts

Creating custom installation packages
Customizing product settings

Table 2-4

Symantec pcAnywhere option set properties (continued)

Tab

Description

Remote Printing

Contains settings for configuring remote printing

Encryption

Specifies certificate information required for
public-key encryption

To configure an option set in pcAnywhere

In the pcAnywhere Manager window, on the left navigation bar, click Option
Sets.

Do one of the following:

■

To create a new option set, on the File menu, click New Item > Advanced.

■

To modify an existing option set, in the right pane, right-click the option
set, and then click Properties.

In the Option Set Properties window, click the left and right arrows to scroll
through the list of tabs.
See Table 2-4 on page 30.

Configure the settings that you want to use.

When you are finished, click OK.
For more information about a feature, see the Symantec pcAnywhere User's
Guide .

Adding an option set to a custom installation file
You can add the option sets that you create in pcAnywhere to a custom installation
file. After the package or custom product is installed on the target computer, the
option set can be applied on the local computer.
To add an option set to a custom installation file

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.

In the Product Editor window, on the Configuration Files tab, click Option
Set File (*.OPT), and then click Add.

Creating custom installation packages
Customizing product settings

Browse to the folder that contains the option set files (*.opt) that you created
in pcAnywhere, select the one that you want to use, and then click Open.
The option set file is added to the list of data and configuration files.

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.

If prompted, type a file name, and then click Save.

Applying an option set on the local computer
Symantec pcAnywhere lets you maintain multiple option set files to accommodate
unique configuration requirements. For example, if you work in different locations,
you can avoid changing the default settings each time you change locations. Create
an option set for each location, and then apply it when you arrive. When you apply
an option set on the local computer, you override the default preferences in
pcAnywhere.
To apply an option set on the local computer

In the pcAnywhere Manager window, on the left navigation bar, click Option
Sets.

In the right pane, right-click the option set file that you want to use, and then
click Apply to Local System.

Setting product installation options
Symantec Packager lets you specify product installation options, which vary by
product and by the features that you have included in the product configuration.
There are other installation options that you can control at the package level.
These include installation mode, restart, logging, and rollback options.
For more information, see the Symantec Packager online Help.
Symantec pcAnywhere lets you customize the following installation options:
Description

Lets you specify a unique description for the product

Target location

Lets you select the directory in which you want to
install the product on the target computer
See “Changing the target installation directory”
on page 33.

Creating custom installation packages
Customizing product settings

Start online registration at startup Prompts users to register the product when they start
the program for the first time
See “Prompting users to register upon startup”
on page 34.
Host object to use as template

Lets you select the host configuration file that you
want to use as a template for new host connection
items that the user creates after installation
See “Selecting the default template for host
connections” on page 35.

Host object to start with Windows

Lets you select a host connection item to start
automatically when the user on the target computer
starts Windows
See “Selecting the default template for host
connections” on page 35.

Remote object to use as template

Lets you select the remote configuration file that you
want to use as a template for new remote connection
items that the user creates after installation
See “Selecting the default template for remote
connections” on page 35.

Run LiveUpdate after installation

Lets you configure the custom installation to
automatically connect to the Symantec LiveUpdate
server to download product updates
See “Updating products” on page 36.

Preserve existing configuration
settings

Lets you configure the product to preserve existing
configuration settings if you are installing over a
previous version of pcAnywhere

Changing the target installation directory
Symantec pcAnywhere custom installations that you create with Symantec
Packager are installed by default in the Program Files directory under
Symantec\pcAnywhere. You can specify a different directory.
To change the target installation directory

In the Symantec Packager window, on the Configure Products tab, do one of
the following:
■

Create a new product configuration.

Creating custom installation packages
Customizing product settings

■

Double-click an existing product to edit it.

In the Product Editor window, on the Installation Options tab, double-click
Target location.

In the Target Location dialog box, select one of the following:
■

Program Files directory

■

Root of system drive

■

Custom path

Under Folder specification, type the full path to the location in which you
want to install the product.

Click OK.

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.

If prompted, type a file name, and then click Save.

Prompting users to register upon startup
Symantec Packager lets you configure the product to prompt users to complete
the online registration process the first time they start the product. To use this
installation option, you must include the pcAnywhere Manager feature in the
product configuration.
To prompt users to register upon startup

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.

In the Product Editor window, on the Installation Options tab, double-click
Start online registration at startup.

In the Start online registration at startup dialog box, selectStart online
registration at startup .

Click OK.

In the Product Editor window, do one of the following:
■

Click OK to save your changes and close the Product Editor window.

Creating custom installation packages
Customizing product settings

■

Click Apply to save your changes and continue the product configuration.

If prompted, type a file name, and then click Save.

Selecting the default template for host connections
Symantec Packager lets you select the host configuration file that you want to
use as a template for new host connection items that the user creates after
installation. Host connection items contain the configuration settings needed to
let remote users connect to the host computer.
You can select the pcAnywhere program default settings, select a preconfigured
host connection item provided by pcAnywhere, or select a user-provided host
connection item.
To select the default template for host connections

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.

In the Product Editor window, on the Installation Options tab, double-click
Host object to use as template.

In the Host object to use as template dialog box, under Value, select the host
connection item file (.bhf) that you want to use as a template.

Click OK.

To configure the product to automatically start a host when the user starts
Windows, in the Product Editor window, on the Installation Options tab,
double-click Host object to start with Windows.

In the Host object to start with Windows dialog box, under Value, select the
.bhf file that you want to use.

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.

If prompted, type a file name, and then click Save.

Selecting the default template for remote connections
Symantec Packager lets you select the remote configuration file that you want to
use as a template for new remote connection items that the user creates after

Creating custom installation packages
Customizing product settings

installation. Remote connection items contain the configuration settings needed
to connect to another computer remotely.
You can select the pcAnywhere program default settings, select a preconfigured
remote connection item provided by pcAnywhere, or select a user-provided remote
connection item.
To select the default template for remote connections

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.

In the Product Editor window, on the Installation Options tab, double-click
Remote object to use as template.

In the Remote object to use as template dialog box, under Value, select the
remote connection item file (.chf) that you want to use as a template.

Click OK.

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.

If prompted, type a file name, and then click Save.

Updating products
If you include the LiveUpdate feature in the product configuration, Symantec
Packager lets you configure the product to automatically connect to the Symantec
LiveUpdate server after installation to download product updates.
If you have installed the Symantec LiveUpdate Administration Utility to manage
LiveUpdate operations for your network, you can configure the product to connect
to the LiveUpdate server on your network. You must customize the LiveUpdate
configuration file (LIVEUPDT.HST) to include the location of the LiveUpdate
Server.
For more information, see the LiveUpdate documentation.
To update products

In the Symantec Packager window, on the Configure Products tab, do one of
the following:
■

Create a new product configuration.

Creating custom installation packages
Customizing product settings

■

Double-click an existing product to edit it.

In the Product Editor window, on the Installation Options tab, double-click
Run LiveUpdate after installation.

In the Run LiveUpdate after installation dialog box, select Run LiveUpdate
after installation .

Click OK.

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.

If prompted, type a file name, and then click Save.

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 39.
To preserve existing configuration settings

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.

In the Product Editor window, on the Installation Options tab, double-click
Preserve existing configuration settings.

In the Preserve existing configuration settings window, check Preserve
existing configuration settings .

Click OK.

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.

If prompted, type a file name, and then click Save.

Creating custom installation packages
Creating a custom command

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
prior to inclusion in a package. Symantec pcAnywhere packages do not require
custom commands.
For more information about custom commands, see the Symantec Packager online
Help.
To create a custom command

In the Symantec Packager window, on the Configure Products tab, on the File
menu, click New Custom Command.

In the Command Editor window, on the Parameters tab, double-click
Description.

In the Command Description dialog box, type a descriptive name for the
command so that you can easily identify it later.
For example:
Uninstall pcAnywhere 9.0 without user intervention

Click OK.

In the Command Editor window, on the Parameters tab, double-click Command
line .

Creating custom installation packages
Creating installation packages

In the Command Line Specification dialog box, under Command line and
switches, type the command-line arguments and switches that are required
to run the command.
For example, to run the uninstallation program for pcAnywhere 9.0 without
requiring user interaction, type the fully qualified path to the remove.exe
file that is located in the pcAnywhere 9.0 program directory followed by the
/s switch. For example:
“C:\Program Files\Symantec\pcAnywhere\remove.exe” /s
You must type a double quotation mark before and after the fully qualified
path to ensure that the operating system handles spaces in the file name and
long file names properly.

Under Optional switches, type the command-line switches that you want to
use to control the installation behavior.

Under Run options, select how the installation should appear to the user.

Click OK.

Creating installation packages
Symantec Packager lets you bundle one or more product configuration files and
custom commands in a package definition file. The package definition file contains
the configuration information and installation instructions that Symantec
Packager requires to build the package.
Package creation is optional for pcAnywhere custom installations. Symantec
Packager lets you build the Symantec pcAnywhere product configuration file,
which creates an .msi file that can be installed locally. You can deploy the Symantec
pcAnywhere .msi file using a third-party deployment tool. The Symantec Packager
Deployment Tool does not support MSI deployment.
Creating a package definition lets you do the following:
■

Bundle one or more products and custom commands in one installation package

■

Configure the installation to run in interactive, passive, or silent mode

■

Add custom graphics to the installation panels for interactive installations

■

Configure restart options, including whether to prompt users to save work

■

Select rollback options for handling an installation that fails

■

Generate a log file to determine whether the package installed successfully

■

Include technical support contact information

Creating custom installation packages
Building product installations and packages

For more information about configuring package settings, see the Symantec
Packager online Help.

Adding products and commands to a package definition
Symantec Packager lets you create a custom installation package that includes
one or more products or custom commands. As you add an item to a package
definition file, its properties, as defined in the product configuration file, are
displayed in the Package Editor window, as well as any product requirements or
conflicts.
To add products and commands to a package definition

In the Symantec Packager window, on the Configure Packages tab, do one of
the following:
■

Create a new package definition.

■

Double-click a package definition to edit an existing one.

In the Package Editor window, on the Product Selection tab, click Add.

In the Open dialog box, select the product or custom command (.pcg) file that
you want to add.

Click Open.
The Estimated package size changes to reflect the product or command that
you include.

Repeat steps 2 through step 4 to add more products or custom commands.

In the Package Editor window, do one of the following:

■

Click OK to save your changes and close the Package Editor window.

■

Click Apply to save your changes and continue the package definition.

If prompted, type a file name, and then click Save.

Building product installations and packages
After you define the contents and installation options for the package definition
file, you must build the package definition to create the installation file. When
you build a package, Symantec Packager creates a self-extracting .exe file that
incorporates the product, command, and package options that you specified.
Alternatively, Symantec Packager lets you build a product configuration file,
which creates a Microsoft Installer (.msi) file for a single product installation.

Creating custom installation packages
Building product installations and packages

Building a product configuration file
Building a product configuration file lets you create an .msi file that you can use
for testing or installation. Symantec Packager supports MSI installation for
pcAnywhere product modules only. You do not need to build a product
configuration file to include it in a package.
Symantec Packager stores the .msi files in the Symantec Packager data directory.
You can view these files on the Deploy Packages tab if you edit the Symantec
Packager preferences to list supported .msi files.
You can use an industry-standard, third-party deployment tool to deploy the
pcAnywhere .msi file. The Symantec Packager Deployment Tool does not support
deployment of .msi files.
To build a product configuration file

In the Symantec Packager window, on the Configure Products tab, select the
product configuration file that you want to build.

On the File menu, click Build.
The Product Build Status window appears, which provides information about
the progress of the build and logs any problems that have occurred. If the
product build is successful, the last line in the Product Build Status window
reads as follows:
Product was built successfully.

In the Product Build Status dialog box, click Close.

Building a package
During the build process, Symantec Packager retrieves information from the
package definition file and product configuration files to determine what products
to include in the installation file, as well as the product features, installation
instructions, and custom settings. Symantec Packager then checks the contents
of the package for product conflicts. If Symantec Packager encounters a product
conflict, the build process stops. You must resolve the conflict, and then repeat
the build process.
After checking for product conflicts, Symantec Packager verifies that product
requirements are met. This includes verification that all required products are
included in the package definition file. If Symantec Packager encounters an error,
the user receives an error message; however, the build process continues.
After completing the validation phases, Symantec Packager creates a
self-extracting executable file and places it on the Deploy Packages tab for testing
and distribution to licensed users.

Creating custom installation packages
Testing packages

To build a package

In the Symantec Packager window, on the Configure Packages tab, select the
package definition file that you want to build.

On the File menu, click Build.
The Package Build Status window appears, which provides information about
the progress of the build and logs any problems that have occurred. If the
package build is successful, the last line in the Build Status window reads as
follows:
Package was built successfully.

In the Build Status dialog box, click Close.

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.

Chapter

Deploying Symantec
pcAnywhere custom
installations
This chapter includes the following topics:
■

About deployment

■

About package installation file locations

■

Deploying installation packages using Web-based deployment

■

Deploying pcAnywhere using SMS 2.0

■

Using Windows NT/2000/2003 Server/XP logon scripts

■

Using NetWare logon scripts

About deployment
You can deploy the custom pcAnywhere installations that you create with
Symantec Packager and the preconfigured installations that are included on the
Symantec pcAnywhere CD using any of the following methods:
■

Local computer installation
Opening an .exe file or supported .msi file on the Deploy Packages tab in
Symantec Packager starts the installation process. Ensure that the target
computer meets the system requirements for pcAnywhere installation.
For more information about using the Deploy Packages tab, see the Symantec
Packager Implementation Guide on the pcAnywhere CD.

Deploying Symantec pcAnywhere custom installations
About package installation file locations

For more information about installing pcAnywhere, see the Symantec
pcAnywhere User's Guide.
■

Symantec Packager deployment tool
This tool lets you deploy packages to one or more computers on your network.
The Symantec Packager deployment tool supports deployment to Microsoft
32-bit computers only (for example, Windows NT/2000/2003 Server/XP).
For more information, see the Symantec Packager Implementation Guide on
the pcAnywhere CD.

■

Symantec Web Deploy tool
This tool lets you deploy package or product installations to one or more
computers using a Web server.
See “Deploying installation packages using Web-based deployment” on page 45.

■

Third-party tools
Package and product installations created with Symantec Packager can be
distributed using a third-party deployment product, such as Microsoft Systems
Management Server (SMS).
See “Deploying pcAnywhere using SMS 2.0” on page 54.

■

Logon scripts
Package and product installations created with Symantec Packager can be
distributed to Windows NT/2000/2003 Server/XP and Novell NetWare target
computers using a logon script.
See “Using Windows NT/2000/2003 Server/XP logon scripts” on page 58.
See “Using NetWare logon scripts” on page 60.

About package installation file locations
Preconfigured package and product installation files are stored in the Packages
directory on the Symantec pcAnywhere CD. Packages and product installation
files that you create with Symantec Packager are listed on the Deploy Packages
tab in Symantec Packager.
To view .msi files, you must edit the Symantec Packager preferences to list
supported product .msi files. Symantec Packager supports MSI deployment only
for pcAnywhere .msi files.
For more information, see the online Help in Symantec Packager or the Symantec
Packager Implementation Guide on the pcAnywhere installation CD.

Deploying Symantec pcAnywhere custom installations
Deploying installation packages using Web-based deployment

Deploying installation packages using Web-based
deployment
Packages that are created with Symantec Packager can be deployed over your
corporate intranet using a Web-based deployment tool that is provided by
Symantec. All of the source files that are necessary to implement Web-based
deployment are included on the Symantec pcAnywhere CD in the Tools/Web
Deploy folder.
Deploying packages using Web-based deployment requires the following steps:
■

Review the Web-based deployment requirements.

■

Set up the installation Web server, which includes copying the package files
to the deployment directory on the Web server.

■

Customize the deployment files.

■

Test the installation.

■

Notify users of the download location.

The Web-based deployment tool supports the deployment of Symantec Packager
packages and Microsoft Installer (.msi) files. Symantec Packager lets you create
a package installation file as a self-extracting executable (.exe) file or create a
custom product installation for a single product as an .msi file.

About Web-based deployment requirements
Table 3-1 lists the minimum requirements that the server or computer must meet
before you implement Web-based deployment on a Web server or target computer.
Table 3-1

Web server and target computer requirements

Deployment

Requirements

Web server

■

HTTP Web server.

Microsoft Internet Information Server (IIS) version
4.0/5.0.
■ Apache HTTP Server version 1.3 or later.
UNIX and Linux platforms are also supported.
■

Deploying Symantec pcAnywhere custom installations
Deploying installation packages using Web-based deployment

Table 3-1

Web server and target computer requirements (continued)

Deployment

Requirements

Target computer

■

Internet Explorer 4.0 or later.
Symantec pcAnywhere requires Internet Explorer
6.x or later for installation.
Windows Installer 2.0 or later (required only for
MSI installations).
Browser security must allow ActiveX controls to
be downloaded to the target computer.
When the installation is complete, the security
level can be restored to its original setting.
Must meet system requirements for the package
to be installed.
Must be logged on to the computer with the rights
that are required for the package to be installed.
You must have administrator rights to install
pcAnywhere.

Setting up the installation Web server
To set up the Web server, complete the following tasks in the order in which they
are listed:
■

Copy the installation files to the Web server.

■

Configure the Web server.

Copying the installation files to the Web server
You must copy the installation files required to support Web-based deployment
to a directory on the Web server. You should create a separate directory on the
Web server for these files. You must also copy the installation files (.exe or .msi)
that you want to make available.
File names are case-sensitive. The following is an example of the folder structure
on the Web server:

Deploying Symantec pcAnywhere custom installations
Deploying installation packages using Web-based deployment

Deploy/Webinst

Deploy\Webinst\Webinst

■

brnotsup.htm

■

default.htm

■

intro.htm

■

logo.jpg

■

oscheck.htm

■

plnotsup.htm

■

readme.htm

■

start.htm

■

webinst.cab

■

files.ini

■

Launch.bat (required only for MSI installations)

■

Installation packages
For example:
Symantec pcAnywhere - Full Product.exe
Symantec pcAnywhere - Host Only (Network).msi

After you complete this process, you must edit the start.htm and files.ini files to
specify the location and names of the installation files.
See “ Customizing the deployment files” on page 49.
To copy the installation files to the Web server

On the Web server, create a directory in which you want to place the
deployment files.
For example:
Deploy

From the Packages folder on the Symantec pcAnywhere CD, copy the
installation files that you want to make available for deployment to the
Webinst subfolder on the Web server.
For example:
Deploy\Webinst\Webinst

Ensure that the default document for the virtual directory is Default.htm.
See “Setting up the installation Web server” on page 46.

Creating a virtual directory on the Web server
You must configure the Web server to create a virtual directory.

Deploying Symantec pcAnywhere custom installations
Deploying installation packages using Web-based deployment

The Web-based deployment tool supports Microsoft Internet Information Server
(IIS) or Apache HTTP Web Server. The procedures for creating a virtual directory
on these servers vary.
To create a virtual directory on a Microsoft Internet Information Server

Do one of the following to launch the Internet Services Manager:
■

In IIS version 4.0: On the Windows taskbar, click Start > Programs >
Windows NT 4.0 Option Pack > Microsoft Internet Information Server
> Internet Service Manager .

■

In IIS version 5.0: On the Windows taskbar, click Start > Programs >
Administrative Tools > Internet Services Manager .

Double-click the Web server icon to open it.

Right-click Default Web Site, and then click New > Virtual Directory.

Click Next to begin the Virtual Directory Creation Wizard.

In the Alias text box, type a name for the virtual directory (for example,
ClientInstall), and then click Next.

Type the location of the installation folder (for example, C:\Client\Webinst),
and then click Next.

For access permissions, select Read only, and then click Next.

Do one of the following to complete the virtual directory creation:
■

In IIS 4.0 click Finish.

■

In IIS 5.0 click Next, and then click Finish.

To create a virtual directory on an Apache Web Server

In a text editor, do one of the following:
■

If you are using Apache Web Server 2.0 or later, open httd.conf.
This file is installed by default in C:\Program Files\ Apache
Group\Apache2\conf.

■

If you are using Apache Web Server 1.3, open srm.conf.

Deploying Symantec pcAnywhere custom installations
Deploying installation packages using Web-based deployment

This file is installed by default in C:\Program Files\ Apache
Group\Apache\conf.

Type the following lines at the end of the file:
DirectoryIndex default.htm

#ServerName machinename
DocumentRoot "C:\Client\Webinst"

For the VirtualHost

Replace 111.111.111.111 with the IP address of
the computer on which Apache HTTP Server is
installed.

For ServerName

Replace machinename with the name of the
server.

For the DocumentRoot

Specify the folder in which you copied the Web
install files (for example, "C:\Client\Webinst").
Double quotation marks are required to specify
the DocumentRoot. If the quotation marks are
omitted, Apache services might not start.

Customizing the deployment files
You must edit the following files to deploy and install packages using the
Web-based deployment tool:
Start.htm

Contains the parameters for the Web server and the
location of the files that need to be installed
This file resides in the root of the Webinstall directory.

Files.ini

Contains the file name parameters for the packages
and files that you want to deploy and install
This file resides in the Webinst subdirectory.

Launch.bat

Contains the command line used to execute the
package installation
This file resides in the Webinst subdirectory.
Launch.bat is required only for MSI installations.

Deploying Symantec pcAnywhere custom installations
Deploying installation packages using Web-based deployment

Customizing Start.htm
The parameters in the Start.htm file contain information about the Web server
and the location of the files that need to be installed. The configuration parameters
are located near the bottom of the Start.htm file, inside the

Symantec PcAnywhere™ Administrator's Guide Pc Anywhere 12.0 Pca Admin

Navigation menu

Versions of this User Manual:

Views

Navigation