12.1

Table Of Contents
downloaded to the client. When the installation is complete, the security level
can be restored to its original setting.
Make sure that users understand the system requirements and have the
administrative rights that are required for the products that they are installing.
For example, to install pcAnywhere, users who are installing on Windows
2000/2003 Server/XP/Vista must have administrator rights on their own
computers and must be logged on with administrator rights.
If your package restarts the client computer at the end of the installation, notify
your users that they should save their work and close their applications before
they begin the installation. For example, a silent installation on Windows 98
computers restarts the computer at the end of the setup.
Include a URL in your email message that points to the client installation as
follows:
For Internet Information Server:
http://Server_name/Virtual_home_directory/Webinst/
where Server_name is the name of the Web-based server,
Virtual_home_directory is the name of the alias that you created, and Webinst
is the folder that you created on the Web server.
For example:
http://Server_name/ClientInstall/Webinst/
For Apache Web Server:
http://Server_name/Webinst/
where Server_name is the name of the computer on which Apache Web Server
is installed. The IP address of the server computer can be used in place of the
Server_name.
Deploying pcAnywhere using SMS 2.0
The following components are required to deploy pcAnywhere with Microsoft
Systems Management Server (SMS) 2.0:
An installation package or custom product installation
created by Symantec Packager
You can create an installation package or custom
product installation as a self-extracting .exe file or as
an .msi file.
pcAnywhere installation file
Deploying Symantec pcAnywhere custom installations
Deploying pcAnywhere using SMS 2.0
52