12.1
Table Of Contents
- Symantec pcAnywhere™ Administrator's Guide
- Technical Support
- Contents
- 1. Planning a migration and upgrade strategy
- 2. Creating custom installation packages
- 3. Deploying Symantec pcAnywhere custom installations
- 4. 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
- About the Microsoft Distributed Component Object Model (DCOM)
- About centralized logging
- 5. Integrating pcAnywhere with directory services
- 6. Managing security in Symantec pcAnywhere
- Index
You can also include additional files to support the deployment of third-party
applications.
To customize Files.ini for package deployment
1
In a text editor, open Files.ini.
2
In the [General] section, edit the line LaunchApplication= so that it references
the package executable file that you want to start after the download
completes.
For example:
LaunchApplication=Symantec pcAnywhere - Full Product.exe
3
If you are deploying multiple files, edit the FileCount= line to reflect the
number of files that you want to deploy.
The default setting is FileCount=1.
4
In the [Files] section, edit the line File1= so that it references the name of the
package that you want to deploy.
For example:
File1=Symantec pcAnywhere - Full Product.exe
Long file names are supported.
5
For each additional file, add a new Filen= filename line, where n is a unique
number and filename is the name of the file.
6
Save and close the file.
Customizing Files.ini for MSI deployment
Modify Files.ini to contain the names of the .msi files that you want to deploy.
MSI deployment requires Launch.bat, which is used to start the installation
program. You must also modify Files.ini to reference the Launch.bat file.
See
“Customizing Launch.bat” on page 50.
You can also include additional files to support the deployment of third-party
applications.
49Deploying Symantec pcAnywhere custom installations
Deploying installation packages using Web-based deployment