12.1

Table Of Contents
You must also modify the Files.ini file to run Launch.bat.
See “Customizing Files.ini for MSI deployment” on page 49.
Note: Installation of .msi files requires Windows Installer 3.1 or later. You should
ensure that the target computer meets the system requirements before you deploy
the product installation.
To customize Launch.bat
1
In a text editor, open Launch.bat.
2
Ensure that the following command line is included in the file:
@SET PATH=%path%;%windir%\system
3
Edit the line @msiexec -i Package.msi so that it reflects the name of the .msi
file that you want to deploy.
For example, @msiexec -i Symantec Packager - Host Only.msi
4
Save and close the file.
Testing the installation on the Web server
To test the installation, go to the Web site (for example, <your web
site>/webinstall), and then click Install.
If the installation fails, note any error messages that are displayed. Use the
following guidelines to troubleshoot the problem:
If there is a problem with the parameters in Start.htm, an error message shows
the path of the files that the Web-based installation is trying to access. Verify
that the path is correct.
If there is a problem in Files.ini (for example, a file not found error), compare
the File1= value with the actual name of the package file.
Confirm that no other entries were changed during modification.
Notifying users of the download location
You can email instructions to your users to download the package that you want
to deploy.
To install a pcAnywhere installation package, users must have Internet Explorer
6.0 or later on their computers. The Internet Explorer security level for the local
intranet must be set to Medium so that Symantec ActiveX controls can be
51Deploying Symantec pcAnywhere custom installations
Deploying installation packages using Web-based deployment