Situation:
You want to know how to deploy a pcAnywhere 10 installation package.

Solution:
This release of pcAnywhere 10.0 offers Administrators the ability to create custom packages of pcAnywhere designed to meet their particular needs. Once an Administrator has determined the functionality and features that they want their users to have, the Packager builds a Windows Installer File (.msi) or a Setup file (.exe). The CD also contains some pre-configured packages representing the most common uses of pcAnywhere, which can also be deployed using the tools described in this document.

After creating a pcAnywhere package, the next step for the Administrator is to deploy the package. In the past, deploying pcAnywhere to end-users could present some challenges to the Administrator. With the introduction of the pcAnywhere Packager, an Administrator can now take advantage of the many tools that currently exist for deploying .msi and .exe files. This document explains how to use four tools to deploy the pcAnywhere Package once it has been built. (To read about how to create a pcAnywhere Package, please see the documentation on the Packager).

It is important to point out that the Packager creates an .msi or .exe file, so any tool that is capable of deploying these types of files should function with the pcAnywhere packages. For the purposes of this release we have tested and documented the following deployment tools:

• SMS 2.0 (Microsoft's Systems Management Server)
• Symantec's Web Based Deployment Tool
• NT Logon Scripts
• NetWare Login Scripts

Deploying pcAnywhere 10.0 Packages with Norton Ghost

To deploy and install a pcAnywhere 10 package using Ghost 6.5, please see the document How to distribute and run application packages with Ghost 6.5.
To deploy and install a pcAnywhere 10 package using Ghost 7.0, please see the document How to distribute and run application packages with Ghost 7.0.

Deploying pcAnywhere 10.0 Packages with SMS 2.0

Definition of "Packages"

pcAnywhere Package: A pre-configured installation package created by the pcAnywhere package manager to allow quick deployment solutions to system administrators. pcAnywhere packages only contain the pcAnywhere files necessary for the pre-configured installation. They can be created as an .msi file or as an .exe file.

SMS Package: A collection of installation sources and packages that are used to inventory, and install software on SMS client machines. SMS packages can be any type of software program that support installation via SMS.

Package Definition File (PDF): The abbreviation "pdf" in this document refers to the "package definition file" used by SMS to create SMS packages.

System Requirements

• Windows NT 4.0 Server with Service Pack 6A or later
• SQL Server 6.5 or later
• SMS 2.0 with the WMI patch, Service Pack 1 or Service Pack 2
• All deployment clients must be a member of the same domain as the SMS distribution server, or have a trust relationship set up between domains, with appropriate permissions to allow the SMS server administrative rights on all clients.
• pcAnywhere 10.0 installed with customized packages created for deployment.

SMS Installation for NT 4.0 Service Pack 6A or later

You must first install SMS 2.0 on Windows NT 4.0 Service Pack 6A or later. It is recommended that you obtain the SMS Service Pack 2 or later from Microsoft. There are specific steps that need to be followed in order to apply this service pack. Please visit http://www.microsoft.com/sms for the latest information regarding these and other updates for SMS.

pcAnywhere Package Creation

See the pcAnywhere 10.0 documentation for information regarding pcAnywhere package creation. You may also use one of the pre-configured packages included on the CD.
Alternately, see the document How to create an installation package for pcAnywhere 10

Deployment with SMS

Package Definition File

A default Package Definition file is provided with pcAnywhere. This file can be modified to accommodate any package created with the pcAnywhere packager. To use the supplied Package Definition file without modification, rename the pcAnywhere package you want to use to "Package.exe" for EXE-based packages, and rename the pcAnywhere package to "Package.msi" for MSI based Packages. The following values must not be removed or changed in the Package Definition File if it is modified:

• AfterRunning=ProgramRestart
• CanRunWhen=UserLoggedOn
• AdminRightsRequired=TRUE

Creating a SMS Deployment Package

An SMS Package must be created, and a distribution must be configured for each type of pcAnywhere installation that you want to perform on the client machines. The following details some configuration steps that should be taken when setting up a package with the default configuration:

• Create a pcAnywhere package for deployment. Build the package as a MSI and EXE File.
• In the SMS Administrator console, right click on Packages, select New, and then select Package from definition from the new sub-menu item. The Package creation wizard should be displayed.
• When prompted to provide the name of a package file, browse to the pcAnywhere source files. (The default location is C:\Program Files\Symantec\pcAnywhere\CMS folder) and select the SETUP.SMS file.
• Select "Always obtain files from a source directory." Do not select "This package does not contain any files."
• Browse to the folder that contains the pcAnywhere package created by the pcAnywhere packager. The package creation wizard will use this folder to point to the pcAnywhere package.
• After you finish the wizard, a package for pcAnywhere 10.0 should appear in the SMS Administrator Console.

Assigning Distribution Points

After a SMS package is created, distribution point must be specified for the package. The following configuration steps show how to setup a distribution point using the default package:

1. Right-click on Distribution Points, point to New, and then click Distribution point.
2. Check the Distribution points that you want to distribute the package to.
3. Select Finish to complete the distribution point wizard.

Advertising the Package

To send the pcAnywhere installation to the clients, an advertisement of one or more of the packaged installs needs to be created. The following is a list of steps to follow to help create a successful advertisement:

1. Right-click Advertisements, point to New, and then click Advertisement from the new sub-menu.
2. Select the desired package that you want to advertise and give the advertisement a descriptive name.
3. Select the program that you want to install from the drop-down menu. Select Windows ME/Windows 2000 if it will be distributed to Windows ME and Windows 2000 clients that support MSI based installations. Select Windows 9x/Windows NT if you would like to distribute the pcAnywhere package to any Windows 9x or Windows NT clients.
4. Click Browse and pick a collection that you would like to advertise the installation to.
5. Set the schedule, requirements, and appropriate security rights of the package.
6. The advertisement is be created, and pcAnywhere should deploy to all of the selected clients.

NOTE: Advertisements created using the EXE-based installer will require user intervention on the client machine to select a temporary directory to extract the installation files to. When prompted to extract the files, select a temporary folder on the local client machine. Extract the setup files, and click Yes to the prompt asking to run Setup.exe. The pcAnywhere package install will execute and install the software. Delete all of the temporary setup files when installation is complete.

Deploying pcAnywhere 10.0 Packages with Symantec's Web Based Deployment Tool


Introduction

pcAnywhere 10.0 allows software deployment to multiple client workstations using a Web-based interface. An Administrator can now deploy pcAnywhere via the corporate Intranet or via the Internet. All of the source files necessary to implement Web-based deployment are included on the pcAnywhere installation CD. These files can be located in the Admin Tools\Web Based Deployment Tool folder on the CD. There are modifications that need to be made to default configuration of these files to create a custom Web-based deployment site. This document covers all of the necessary changes that need to be made to the Web-based installation configuration files to successfully deploy pcAnywhere 10.0 to multiple client workstations.

Creating the Installation Web Site

The source files need to be copied to a virtual directory on your Web server. For the purposes of this document, we created a virtual directory called Webinstall. You can give the virtual directory any name you choose. You will also need to create a sub-folder in the virtual directory. For the purposes of this document we created a sub-folder called Webinst. Here are the steps that you will need to take to set up the Web server.

1. Copy the following files into the root of the virtual directory (The folder that you created. We used Webinstall.)
   brnotsup.htm
   default.htm
   intro.htm
   oscheck.htm
   plnotsup.htm
   start.htm
   logo.jpg
   webinst.cab
   
2. Copy the following files to the Webinst sub-folder of Webinstall.
   files.ini
   launch.bat
   The pcAnywhere Package that you created (for example, pcAnywhere.msi or pcAnywhere.exe)
   
3. Ensure the default document for the virtual directory is set to default.htm.

Editing the Files.ini file

The next step in configuring the Web-based deployment tool is to modify the Files.ini file to reflect the name of the pcAnywhere package that you created. Files.ini is located in the \Webinst folder of the Webinstall source files. The entry shown in the table below is the only one that needs to be modified in this configuration file. Open the Files.ini file and search for File1= . When you locate File1=, modify the value as described below.

Param Name =	Value =
File1=	Set this value to the name of the package that was created using the pcAnywhere Packager (example=pcAnywhere.msi) Long file names can be used for this entry.

Editing the Launch.bat file

The next step in configuring the Web-based deployment tool is to modify the Launch.bat file. The Launch.bat file is a simple batch file that is used to start the installation of a pcAnywhere package. The file only contains the command line used to execute the package installation. Modify this command line to reflect the name of the package that is being installed. The table below gives examples of the command line that should be used for both MSI and EXE packages. Edit the Launch.bat file with the following Command Line. Substitute <PackageName> for the name of the package you created.

Package Type	Command Line (Where <PackageName> is the name of the package)
If you created an .exe based package	@<PackageName>.exe
If you created an .msi based package	@msiexec -i <PackageName.msi>

Editing the Start.htm file

The next step is to modify some parameters in the Start.htm file. The values of these parameters provide the Web based installation tool with information about the Web server that it is installed on, and the location of the files that need to be installed. The configuration parameters are located toward the bottom of the start.htm file, inside the <object> tags. Edit the Start.htm file and search for Objects. The table below outlines the parameters for Start.htm, and the values that should be used for each parameter.

Param Name =	Value=
ServerName	This value should be changed to reflect the name of the server that contains the installation source files. Hostname, IP address, or NetBIOS name can be used here. The source files must be contained on a HTTP Web server.
VirtualHomeDirectory	This value should reflect the virtual directory of the HTTP server that contains the installation source files (for example, Webinstall).
ConfigFile	The value of this parameter points to the file name of files.ini. The default value for this parameter should be OK. If you did not change the name of Files.Ini, you can leave this value as is.
*ProductFolderName	This parameter points to the subdirectory that actually contains the source files to be downloaded locally. Set this value to the subdirectory that contains the pcAnywhere package, Files.ini, and the Launch.bat file (for example, Webinst).
MinDiskSpaceInMB	This value sets the limit for minimum hard drive space. The default value should be OK.
ProductAbbreviation	This value contains the abbreviation for the product. The default value should be OK.

Testing the Installation

You can now test the deployment Web site by browsing to the Web site and clicking Install from the Web page. The source files will be downloaded locally, and then Launch.bat will be executed which will launch the package installation.


Troubleshooting

To determine the cause of an installation problem, make note of any error messages you receive.

1. If there is a problem with the parameters in Start.htm, an error message showing the path of the files the Web based install is trying to access will be displayed. Verify the path shown in the error message is the same as the correct path.
2. If there is a problem in Files.ini ("file not found" error), compare the File1= value with the actual name of the pcAnywhere package file.
3. Confirm that no other entries were changed during modification.

Deploying pcAnywhere Packages using Windows NT/Windows 2000 login scripts

pcAnywhere Packages can be deployed to multiple Windows workstations on a Windows NT Domain using logon scripts. Logon scripts can simplify the deployment of pcAnywhere and allow custom installation options to be used for each user or group of users. A sample Windows NT logon script used to install pcAnywhere is shown in this document, and may be used as a reference.

Creating Windows NT logon scripts

There are multiple configuration steps that should be followed to set up a Windows NT logon script. The following sections will detail the setup and configuration process:

• Setting up the server
• Writing the logon script
• Completing and testing the script

Setting up the server

The server must be configured to allow for the storage of pcAnywhere Packages and the implementation of logon scripts. You must have Administrator rights on the domain to perform these tasks. The following steps show how to set up the server using our sample test script:

1. On the server, create a PCAHOME folder.
2. Share the folder and use the default PCAHOME share name.
3. Set the permissions of this share so that all users have "read" access.
4. Copy the pcAnywhere Package that you've created to this share.

Writing the logon script

A sample logon script is provided below. The script is a simple batch file that copies the pcAnywhere Package to the workstation, launches the pcAnywhere Package installation, and cleans up all of the installation files when it is complete. This script assumes default installation directories. You may need to modify the script to fit the particular environment.

@echo off
setlocal

REM ***** Package Variable -- Change to name of pca Package *****
Set Package=Package.msi

REM ***** EXE or MSI Variable -- Change to package type (MSI or EXE) *****
Set PkgType=MSI

Rem ***** File Server Name Variable -- Change to server containing the pca Package *****
Set FSName=\\2KServer

REM ***** Maps a drive to the network share *****
net use z: %FSName%\PCAHOME

REM ***** Checks for pca in default folder
If exist c:\progra~1\Symant~1\pcanyw~1\anywhere.bin GOTO End

REM ***** Creates a folder in the temp dir, and copies the package *****
C:
CD %TEMP%
MD pcapkg
CD pcapkg
z:
COPY %Package% c:

REM ***** Launch Package Installation *****
C:
IF %PkgType% == MSI msiexec -i %Package%
IF %PkgType% == EXE %Package%

REM ***** Cleanup *****
del %Package%
CD ..
rd pcapkg
Net Use z: /DELETE

:End
endlocal

Completing and testing the logon script

When you are finished writing the script, copy it to the scripts share on the domain controller. Test the script on one or two workstations before setting the script up for all users. Windows NT and Windows 2000 users must have local administrative rights on their workstation before installing the pcAnywhere package.

Deploying pcAnywhere 10.0 packages with NetWare Login Scripts

pcAnywhere packages may be deployed to multiple Windows clients on a Novell NetWare network using login scripts. You can write NetWare login scripts to simplify the deployment of pcAnywhere packages as well as customize the way the packages are deployed to each user. This section covers the setup of pcAnywhere package deployment using NetWare login scripts. This script assumes default installation directories. You may need to modify the script to fit the particular environment.

Setting up the server

1. Map drive "Z:" to the "SYS:" volume. Another drive letter may be used, but make sure you substitute for that drive letter in the following steps.
2. In the "Z:\login" folder create a folder called "PCA".
3. Create a group called PCA_Users. This group should exist in the default context for servers that host both NDS and Bindery logins. If the server only hosts NDS logins, this group should exist in a context that exists in the NDS partition stored on the server.
4. Grant the PCA_Users group read rights to the PCA folder.
5. Copy the pcAnywhere package that you created into the PCA folder.

Writing the login script

A sample login script and deployment batch file is provided below. The script creates the appropriate drive mappings to the local workstation, and launches the deployment batch file. The batch file installs the pcAnywhere package and removes the installation files when complete.

NetWare Script

REM ***** Default mappings *****

MAP *1:=SYS:

REM ***** Maps a drive to the network share *****
MAP Z:=SYS:LOGIN\PCA

REM ***** launches the deployment batch file *****
#Cmd /c z:\deploy.bat

Exit

Deployment Batch File

@echo off
setlocal
REM ***** Package Variable -- Change to name of pca Package *****
Set Package=Package.msi

REM ***** EXE or MSI Variable -- Change to package type (MSI or EXE) *****
Set PkgType=MSI

REM ***** Checks for pca in default folder
If exist c:\progra~1\Symant~1\pcanyw~1\anywhere.bin GOTO End

REM ***** Creates a folder in the temp dir, and copies the package *****
C:
CD %TEMP%
MD pcapkg
CD pcapkg
z:
COPY %Package% c:

REM ***** Launch Package Installation *****
C:
IF %PkgType% == MSI msiexec -i %Package%
IF %PkgType% == EXE %Package%

REM ***** Cleanup *****
del %Package%
CD ..
rd pcapkg

:End
endlocal

Completing and testing the login script

When you are finished writing the script, test the script on one or two workstations before setting the script up for all users. Windows NT and Windows 2000 users must have local administrative rights on their workstation before installing the pcAnywhere package.