Symantec PCANYWHERE - V12.1 Service manual

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.1
Legal Notice
Copyright © 2007 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, LiveUpdate, Virtually Anywhere and Work Virtually Anywhere are trademarks
or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other
countries. Other names may be trademarks of their respective owners.
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, Windows Vista, 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: [e-mail]
■Europe, Middle-East, and Africa: [e-mail]
■North America and Latin America: [e-mail]
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:
These solutions provide early warning of cyber
attacks, comprehensive threat analysis, and
countermeasures to prevent attacks before they occur.
Symantec Early Warning Solutions
These services remove the burden of managing and
monitoring security devices and events, ensuring
rapid response to real threats.
Managed Security 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.
Consulting Services
Educational Services provide a full array of technical
training, security education, security certification,
and awareness communication programs.
Educational Services
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.

Technical Support
Chapter 1 Planning a migration and upgrade strategy
About migrations and upgrades ...................................................... 11
Migrating from pcAnywhere 12.0.2 in Windows 2000/2003
Server/XP to Vista ............................................................ 12
Migrating from pcAnywhere 11.x in Windows 2000/2003
Server/XP ....................................................................... 13
Migrating from pcAnywhere 10.5.x in Windows 2000/2003
Server/XP ....................................................................... 13
Using Symantec Packager to streamline migrations and upgrades ......... 13
Chapter 2 Creating custom installation packages
About Symantec Packager .............................................................. 15
What you can do with Symantec Packager ......................................... 16
How Symantec Packager works ....................................................... 16
Importing a product module ........................................................... 18
Customizing product settings ......................................................... 18
Selecting product features ....................................................... 20
Including configuration files .................................................... 21
Integrity stamping a product configuration ................................. 24
Serializing a pcAnywhere installation ........................................ 25
Managing configuration settings globally ................................... 27
Setting product installation options ........................................... 30
Creating a custom command ........................................................... 35
Creating installation packages ........................................................ 36
Adding products and commands to a package definition ................ 37
Building product installations and packages ...................................... 38
Building a product configuration file .......................................... 38
Building a package .................................................................. 39
Testing packages .......................................................................... 40
Contents

Chapter 3 Deploying Symantec pcAnywhere custom installations
About deployment ........................................................................ 41
About package installation file locations ........................................... 42
Deploying installation packages using Web-based deployment .............. 43
About Web-based deployment requirements ................................ 43
Setting up the installation Web server ........................................ 44
Customizing the deployment files ............................................. 47
Testing the installation on the Web server .................................. 51
Notifying users of the download location .................................... 51
Deploying pcAnywhere using SMS 2.0 .............................................. 52
Minimum requirements for SMS deployment .............................. 53
Deploying with SMS ............................................................... 53
Using Windows 2000/2003 Server/XP/Vista logon scripts .................... 56
Setting up the Windows server .................................................. 56
Writing the Windows logon script ............................................. 56
Testing the Windows logon script .............................................. 58
Using NetWare logon scripts .......................................................... 58
Setting up the Novell NetWare server ......................................... 58
Writing the NetWare logon script .............................................. 59
Testing the NetWare logon script ............................................... 60
Chapter 4 Performing centralized management
About centralized management ...................................................... 61
Managing pcAnywhere hosts remotely ............................................. 61
Installing the pcAnywhere Host Administrator tool ...................... 62
Adding the Host Administrator snap-in to MMC ........................... 63
Creating a configuration group ................................................. 63
Adding computers to a configuration group ................................. 64
Configuring administrator host and remote connection
items ............................................................................. 64
Configuring a host item in pcAnywhere Host Administrator ........... 67
Distributing pcAnywhere configuration files ............................... 67
Managing hosts in a configuration group .................................... 68
Integrating with Microsoft Systems Management Server ..................... 69
Importing the package definition file into SMS ............................ 69
About the Microsoft Distributed Component Object Model
(DCOM) ................................................................................ 69
Implementing DCOM in Windows 2000/2003
Server/XP/Vista ............................................................... 70
Modifying DCOM settings ........................................................ 70
About AwShim ....................................................................... 71
About centralized logging .............................................................. 72
Contents8

Monitoring performance using SNMP traps ................................. 72
About the pcAnywhere MIB file ................................................. 73
Chapter 5 Integrating pcAnywhere with directory services
About directory services ................................................................ 75
Using directory services with pcAnywhere ........................................ 75
Configuring the directory servers .................................................... 76
Configuring the LDAP server .................................................... 76
Configuring Netscape Directory Server 3.1 .................................. 76
Configuring Netscape Directory Server 4.0 .................................. 77
Configuring Novell v5.0 server .................................................. 78
Configuring Windows Active Directory ....................................... 82
Configuring pcAnywhere to use directory services .............................. 86
Setting up directory services in pcAnywhere ............................... 86
Setting up the host computer to use directory services .................. 87
Setting up the remote computer to use directory services ............... 88
Chapter 6 Managing security in Symantec pcAnywhere
Controlling access to pcAnywhere hosts ........................................... 89
Limiting connections to specific computer names or IP
addresses ........................................................................ 90
Leveraging centralized authentication in pcAnywhere ................... 91
Protecting session security ............................................................. 95
Maintaining audit trails ................................................................. 97
Implementing policy-based administration ....................................... 98
Implementing Group Policy in Windows 2000/2003
Server/XP/Vista ............................................................... 98
Importing the pcAnywhere administrative template ..................... 98
Managing user policies ............................................................ 99
Index
9Contents

Contents10

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.5.x to version 12.1
on Windows 2000/2003 Server/XP/Vista. During a migration, pcAnywhere lets
you install over the previous version of the product and preserve user-defined
settings.
A system restart for migrations and upgrades is required on Vista, but is only
required on Windows 2000/2003 Server/XP if system files need to be updated.
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 13.
Table 1-1 includes information that you can use as a reference in planning your
migration and upgrade strategy.
1
Chapter

Table 1-1 Migration and upgrade strategy matrix
Data preserved
automatically
Restart requiredOperating
system
Symantec
pcAnywhere
version
Host items
Caller items
Remote items
Option sets
Registry settings
AutoTransfer files (must be
converted)
Serial ID sets
Yes (for Vista)Windows
2000/2003
Server/XP/Vista
12.0
Host items
Caller items
Remote items
Option sets
Registry settings
AutoTransfer files (must be
converted)
Serial ID sets
NoWindows
2000/2003
Server/XP
11.x
Host items
Caller items
Remote items
Option sets
Registry settings
AutoTransfer files (must be
converted)
NoWindows 2000/XP10.5.x
Migrating from pcAnywhere 12.0.2 in Windows 2000/2003 Server/XP
to Vista
Symantec pcAnywhere supports full migration of the full product version and
host-only version of pcAnywhere 12.0.2 to version 12.1 in Windows 2000/20003
Server/XP. If you are also upgrading to Vista, you can either upgrade to Vista and
then to pcAnywhere 12.1, or vice versa.
Planning a migration and upgrade strategy
About migrations and upgrades
12

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 11.x in Windows 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.1 in Windows 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.5.x in Windows 2000/2003 Server/XP
Symantec pcAnywhere supports full migration of the full product version and
host-only version of pcAnywhere 10.5.x to 12.1 in Windows 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.
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:
13Planning a migration and upgrade strategy
Using Symantec Packager to streamline migrations and upgrades

Create a custom installation package that
includes a custom command to silently
uninstall the previous version before
installing the product.
The product installation requires you to
manually uninstall a previous version of the
product.
Create a custom installation package for the
product installation and configure the
package to install in passive or silent mode.
The product installation requires you to
restart the computer to complete the
installation process.
Create a custom installation package that
includes preconfigured data files that
contain the settings that you need.
The product installation does not support
preservation of preconfigured product
settings.
See “Using Symantec Packager to streamline migrations and upgrades” on page 13.
Planning a migration and upgrade strategy
Using Symantec Packager to streamline migrations and upgrades
14

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.
2
Chapter

Note: Symantec Packager runs on Windows 2000/2003 Server/XP
Professional/Vista platforms only.
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 Overview of Symantec Packager phases
Import Products Configure Products Configure Packages
Configure Commands
Deploy Packages
Table 2-1 outlines the process for creating packages.
Creating custom installation packages
What you can do with Symantec Packager
16

Table 2-1 Package creation process
DescriptionTask
Product modules contain the installation binary and product
template files that are needed to create a custom installation
of the product.
See “Importing a product module” on page 18.
Import product modules into
Symantec Packager.
You can select the features that you want your users to have,
add preconfigured data and configuration files, and set
default installation options for each product.
See “Customizing product settings” on page 18.
Configure products.
Custom commands let you add additional functionality that
is not supported in the product templates, such as including
a third-party program or batch file.
See “Creating a custom command” on page 35.
Configure commands that
you want to include in a
package.
You can bundle one or more product configurations and
custom commands in a package. You can further customize
the package by setting package installation options, product
installation order, and other settings.
See “Creating installation packages” on page 36.
Configure 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 38.
Build custom products or
packages.
You should test packages before deploying them to end users
to ensure proper functionality.
See “Testing packages” on page 40.
Test the package.
The Deploy Packages tab holds the packages that you 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.
See “About deployment” on page 41.
Deploy the package.
17Creating custom installation packages
How Symantec Packager works

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
<version>.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
1Open Symantec Packager.
2In the Symantec Packager window, on the Import Products tab, on the File
menu, click Import New Product.
3In the Open dialog box, navigate to the folder that contains the product module
that you want to import.
4Select 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.
If you are running Symantec Packager on Windows Vista, .pmi files from
previous versions prior to 12.1 cannot be imported; however, you can import
them if you are running Symantec Packager on XP.
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.
Creating custom installation packages
Importing a product module
18

Table 2-2 Symantec pcAnywhere product configuration options
SettingsTab
You can customize the following features in
pcAnywhere such as:
■User interface (pcAnywhere Manager)
■Remote components
■Host components
■Communications protocols
■Documentation (online manuals and Help)
■Symantec installation utilities
Features
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.
Configuration Files
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
Installation Options
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 the installation of pcAnywhere .msi and
.exe files.
See “Building a product configuration file” on page 38.
19Creating custom installation packages
Customizing product settings

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