1. Manuals
  2. Brands
  3. Symantec Manuals
  4. Software
  5. 14541094 - pcAnywhere Host & Remote
  6. Implementation manual

Symantec 14541094 - pcAnywhere Host & Remote Implementation Manual

Implementation guide
Hide thumbs Also See for 14541094 - pcAnywhere Host & Remote:
Table of Contents

Advertisement

Quick Links

Download this manual See also: Administrator's Manual, User Manual
Symantec™ Packager
Implementation Guide

Advertisement

Table of Contents
loading

Related Manuals for Symantec 14541094 - pcAnywhere Host & Remote

Summary of Contents for Symantec 14541094 - pcAnywhere Host & Remote

  • Page 1 Symantec™ Packager Implementation Guide...
  • Page 2 NO WARRANTY. The technical documentation is being delivered to you AS-IS, and Symantec Corporation makes no warranty as to its accuracy or use. Any use of the technical documentation or the information contained therein is at the risk of the user.

  • Page 3: Table Of Contents

    Changing Symantec Packager data folders ..........27 Listing supported product .msi files on the Deploy Packages tab ..28 Showing or hiding the Symantec logo ............28 Changing the appearance of icons in Symantec Packager ....28 Accessing commands in Symantec Packager ..........29...
  • Page 4 Chapter 4 Importing products in Symantec Packager About importing products .................. 31 Importing product modules ................32 Deleting products from Symantec Packager ........... 33 Chapter 5 Configuring custom products About configuring custom products ..............35 Working with custom products ................. 37 Creating custom products ................
  • Page 5 Contents Configuring package definitions ............... 63 Adding products and commands to a package definition ..... 63 Changing the installation sequence ............65 Setting package installation options ............66 Building and testing packages ................77 Building packages ..................77 Testing packages ..................78 Chapter 8 Deploying installation packages About deploying packages ..................
  • Page 6 6 Contents...

  • Page 7: Introducing Symantec Packager

    About Symantec Packager Symantec Packager lets you create, modify, and build custom installation packages that you 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.

  • Page 8: What You Can Do With Symantec Packager

    What you can do with Symantec Packager What you can do with Symantec Packager Symantec Packager gives you the flexibility to select only the features that you require, which lets you reduce the deployment size and the installation footprint. It also lets you tailor products to adhere to your security policy, which lets you give users full access to all features or limit access where appropriate.

  • Page 9: Include Custom Commands With Product Installations

    What you can do with Symantec Packager Include custom commands with product installations If a product that you want to deploy is not supported by Symantec Packager, you can create a custom command that contains the product installation and include that custom command in a package installation.

  • Page 10: Install Multiple Products At Once

    You can reuse and combine product installations and custom commands to achieve different goals. For example, you might want to deploy a Symantec pcAnywhere host to all of your users, but you first need to uninstall the previous version. A subset of your client systems may also require a service pack to address a security issue.

  • Page 11: How Symantec Packager Works

    Packages Packages Configure Commands The following process outlines how the Symantec Packager phases build upon one another to let you create custom installation packages: Import product modules into Symantec Packager ■ If the product that you want to customize provides a product module, Symantec Packager automatically imports it.

  • Page 12: About The Import Products Phase

    You can further customize the package by setting package installation options, product installation order, and other settings. When you build a package in the Configure Packages phase, Symantec Packager creates an installation file that incorporates the product, command, and package options that you specified.

  • Page 13: About The Configure Products Phase

    If you want to install a product that was not designed to be used with Symantec Packager, you can still include that product in an installation package by creating a custom command.
  • Page 14 Import Products phase. After you select the product features and options that you want to include and specify a file name, Symantec Packager saves this file as a product configuration file. The product configuration file, which displays on the Configure Products tab, references its corresponding product template file on the Import Products tab.

  • Page 15: About The Configure Packages Phase

    After you select the products and custom commands that you want to include in the installation package and specify a file name, Symantec Packager saves this file as a package definition (.pkg) file. The .pkg file, which displays on the...

  • Page 16: About The Deploy Packages Phase

    Deploy Packages tab. (They are for testing purposes only.) You can use the product .msi files that Symantec Packager creates as part of the Configure Products build process for testing purposes. Product .msi files are not supported automatically for deployment (only Symantec pcAnywhere .msi files...

  • Page 17: Where To Find More Information

    In any Symantec Packager window, press F1. ■ Accessing the Symantec technical support Web site If you are connected to the Internet, you can visit the Symantec technical support Web site for additional information about Symantec Packager. To access the Symantec technical support Web site In your Internet browser, type the following Web address: ◆...
  • Page 18 18 Introducing Symantec Packager Where to find more information...

  • Page 19: Installing Symantec Packager

    Before you install Symantec Packager, ensure that your computer meets the system requirements. Review the Readme file on the installation CD for any known issues. System requirements for Symantec Packager Symantec Packager runs only on Microsoft 32-bit operating systems and has the following system requirements: Supported operating systems: ■...

  • Page 20: System Requirements For Installation Packages

    CD-ROM or DVD-ROM drive ■ System requirements for installation packages Although Symantec Packager runs only on Windows NT/2000/2003 Server/XP, packages that you create using Symantec Packager can be installed on the following operating systems: Windows NT 4.0 with Service Pack 6a ■...

  • Page 21: Installing Symantec Packager

    CD. Installing Symantec Packager from the installation CD When you insert the CD that contains the Symantec Packager installation program into your CD-ROM drive, an installation window displays the products that you can install.

  • Page 22: Starting The Symantec Packager Installation Program Manually

    Control Panel. Once the removal process begins, you cannot cancel it. Symantec Packager automatically deletes the product template files on the Import Products tab. Symantec Packager prompts you to remove the files in the Symantec Packager data folders. This includes all product configuration files,...
  • Page 23 Installing Symantec Packager Uninstalling Symantec Packager want to keep these files, click No when prompted to delete Symantec Packager data files. To uninstall Symantec Packager Close Symantec Packager if it is open. On the Windows taskbar, click Start > Settings > Control Panel.
  • Page 24 24 Installing Symantec Packager Uninstalling Symantec Packager...

  • Page 25: Symantec Packager Basics

    During installation, Symantec Packager automatically imports any product module (.pmi) files that it finds. If no products appear on the Import Products tab when you open Symantec Packager, you may need to import the product modules manually. “Importing product modules”...

  • Page 26: Updating Symantec Packager

    Packager by connecting to the Symantec LiveUpdate server and selecting the updates that you want to install. To update Symantec Packager On the Windows taskbar, click Start > Program Files > Symantec Packager. On the Help menu, click LiveUpdate. Follow the on-screen instructions.

  • Page 27: Changing Symantec Packager Data Folders

    Changing Symantec Packager Preferences and view options Changing Symantec Packager data folders Symantec Packager saves its data in the folders that are specified in Symantec Packager Preferences. You can use the default folders or specify new folder locations in the Preferences dialog box.

  • Page 28: Listing Supported Product .Msi Files On The Deploy Packages Tab

    Changing Symantec Packager Preferences and view options Listing supported product .msi files on the Deploy Packages tab You can configure Symantec Packager to list supported product .msi files on the Deploy Packages tab. Note: Only Symantec pcAnywhere .msi files are supported for deployment. For more information, see the Symantec pcAnywhere product documentation.

  • Page 29: Accessing Commands In Symantec Packager

    Accessing commands in Symantec Packager To change the appearance of icons in Symantec Packager Open Symantec Packager. In the Symantec Packager window, on the View menu, select one of the following: Large Icons Displays file names and 32 x 32 pixel icons in rows from left to right.
  • Page 30 30 Symantec Packager basics Accessing commands in Symantec Packager...

  • Page 31: Importing Products In Symantec Packager

    Import Products tab, you might need to import product modules manually. “Importing product modules” on page 32. Note: Product modules are only available for products that support Symantec Packager. To create a package for an unsupported product, you must create a custom command. “Configuring custom commands”...

  • Page 32: Importing Product Modules

    During installation, Symantec Packager automatically imports any product modules that it finds. If no products appear on the Import Products tab when you open Symantec Packager, you might need to import product modules manually. Note: Product modules are only available for products that support Symantec Packager.

  • Page 33: Deleting Products From Symantec Packager

    Deleting products from Symantec Packager To import product modules In the Symantec Packager window, on the Import Products tab, on the File menu, click Import New Product. In the Open dialog box, navigate to the folder that contains the product module that you want to import.
  • Page 34 34 Importing products in Symantec Packager Deleting products from Symantec Packager...

  • Page 35: Configuring Custom Products

    Chapter Configuring custom products This chapter includes the following topics: About configuring custom products ■ Working with custom products ■ Configuring custom products ■ Building and testing custom products ■ About configuring custom products During the Configure Products phase, you create product configuration (.pcg) files.
  • Page 36 36 Configuring custom products About configuring custom products Figure 5-1 shows the Configure Products tab. Figure 5-1 Configure Products tab Product configuration (.pcg) files Creating a custom product involves the following process: Create a new custom product. ■ “Creating custom products” on page 37.

  • Page 37: Working With Custom Products

    Working with custom products Working with custom products In the Symantec Packager main window, the Configure Products tab lists the product configuration files that you have created and provides information about when they were last built and modified. In this window, you can create, edit, and delete product configuration files and view details.

  • Page 38: Viewing Product Details

    38 Configuring custom products Working with custom products Each phase of Symantec Packager relies on the output from previous phases. If you edit a custom product, all built packages that include the product do not change until you rebuild them.

  • Page 39: Deleting Custom Products

    Built packages that are stored on the Deploy Packages tab are not affected. To delete custom products In the Symantec Packager window, on the Configure Products tab, select the custom product that you want to delete. On the Edit menu, click Delete.
  • Page 40 40 Configuring custom products Configuring custom products To select product features In the Symantec Packager window, on the Configure Products tab, do one of the following: Create a new product configuration. ■ Double-click an existing product to edit it. ■...

  • Page 41: Setting Product Installation Options

    To set the product installation location In the Symantec Packager window, on the Configure Products tab, do one of the following: Create a new product configuration.

  • Page 42: Adding Or Removing Configuration Files

    The Configuration Files tab lists required files. You cannot remove these files, but you can replace them with configuration files that you edit. Symantec Packager does not supply a means to edit configuration files. For more information about editing configuration files, see the documentation for the product that you are customizing.
  • Page 43 The configuration files that can be included are limited to what the product supports. Some products may support multiple configuration file types. To add or remove configuration files In the Symantec Packager window, on the Configure Products tab, do one of the following: Create a new product configuration.

  • Page 44: Building And Testing Custom Products

    After you complete the validation process, Symantec Packager creates a Microsoft Software Installer (.msi) file, which you can use for testing purposes. Symantec Packager places the .msi file in the folder that is specified for the Deploy Packages tab. This folder is usually located in the following directory: \Documents and Settings\<User_Name>\My Documents\Packager\Deployment...

  • Page 45: Testing Custom Products

    Testing custom products The product module files and product configuration files that are provided by Symantec are designed to help you create a buildable, installable product. You should test whether your feature selections and installation options are appropriate for your users. It is important that you test your custom products on all supported platforms before you include them in a package or deploy them to end users.
  • Page 46 46 Configuring custom products Building and testing custom products...

  • Page 47: Configuring Custom Commands

    Building and testing custom commands ■ About configuring custom commands Symantec Packager lets you create custom commands to include in your packages. Examples of custom commands include installations of unsupported products, batch files, third-party executables, command-line arguments, or simple file copies. Custom commands let you simplify application deployment by including multiple tasks in one package.
  • Page 48 48 Configuring custom commands About configuring custom commands Custom commands let you do the following: Execute a command on the target computer. ■ Copy files to the target computer. ■ Combine these two so that you copy files to the target computer and execute ■...

  • Page 49: Working With Custom Commands

    57. Working with custom commands In the Symantec Packager main window, the Configure Products tab lists the custom commands that you have created and provides information about when they were last modified and built. You can create, edit, and delete custom commands and view details in this window.

  • Page 50: Viewing Custom Command Details

    You can customize the command configuration file. To create a custom command In the Symantec Packager window, on the Configure Products tab, on the File menu, click New Custom Command. In the Command Editor dialog box, on the Parameters tab, do one or both of...

  • Page 51: Configuring Custom Commands

    (such as updated virus definitions), removing conflicting software programs, or running a clean-up utility. Symantec Packager lets you enter a specific command or add a script file that contains a series of commands.

  • Page 52: Specifying Command-Line Parameters And Switches

    Symantec Packager needs to install and run the command and any variables that you want to use. To specify command-line parameters and switches In the Symantec Packager window, on the Configure Products tab, do one of the following: Create a new custom command.
  • Page 53 Configuring custom commands Configuring custom commands In the Command Editor dialog box, on the Parameters tab, click Command line, and then click Add. In the Command Line Specification dialog box, under Command line and switches, type the command-line argument and switches that are required to execute the command.

  • Page 54: Including Files In A Command

    Packager copies the file to the specified folder on the target computer. Symantec Packager lets you copy files in the Program Files folder, the root of the system drive, or a custom path. If you select the Program Files folder or the root of the system drive, Symantec Packager automatically completes the full path.

  • Page 55: Specifying Operating System Support

    If prompted, type a file name, and then click Save. Specifying operating system support You can install the custom installation packages that you create with Symantec Packager on any Microsoft 32-bit platform except for Windows 95/NT 3.5x. Unless you specify otherwise, Symantec Packager installs the custom commands that you include in a package on all supported operating systems.
  • Page 56 56 Configuring custom commands Configuring custom commands To specify operating system support In the Symantec Packager window, on the Configure Products tab, do one of the following: Create a new custom command. ■ Double-click an existing command to edit it.

  • Page 57: Building And Testing Custom Commands

    Deploy Packages tab. The command .exe file is supplied for testing purposes and is not supported for deployment. To build custom commands In the Symantec Packager window, on the Configure Products tab, select the custom command that you want to build. On the File menu, click Build.
  • Page 58 In the Run dialog box, type explorer.exe In Windows Explorer, navigate to the working directory of the Deploy Packages tab. Data folders are listed in Symantec Packager Preferences. “Changing Symantec Packager data folders” on page 27. Double-click the command .exe file that you want to test.

  • Page 59: Configuring Installation Packages

    The Configure Packages phase depends on the successful completion of the Configure Products phase. You can add only products or custom commands for which a product configuration (.pcg) file exists. Symantec Packager uses the information from the product configuration and package definition files to build the package.
  • Page 60 60 Configuring installation packages About configuring packages Figure 7-1 shows the Configure Packages tab with sample package definition files. Figure 7-1 Configure Packages tab Package definition (.pkg) files Configuring a package involves the following process: Create a package definition. ■ “Creating package definitions”...

  • Page 61: Working With Package Definitions

    Working with package definitions Working with package definitions In the Symantec Packager main window, the Configure Packages tab lists the package definition files that you have created and provides information about when they were last modified and built. In this window, you can add, edit, rename, and delete package definition files.

  • Page 62: Viewing Package Definition Details

    The package definition file appears on the Configure Packages tab. Viewing package definition details Symantec Packager lets you view the details of a package definition file without opening the file. A summary of the package definition specifications is available using the Display Details option.

  • Page 63: Configuring Package Definitions

    Adding products and commands to a package definition Symantec Packager lets you create a custom installation package that includes one or more products or custom commands. As you add an item to a package definition file, its properties, as defined in the product or command configuration file, are displayed in the Package Editor dialog box.
  • Page 64 To add products and commands to a package definition In the Symantec Packager window, on the Configure Packages tab, do one of the following: Create a new package definition. ■ Double-click an existing package definition to edit it.

  • Page 65: Changing The Installation Sequence

    To change the installation sequence In the Symantec Packager window, on the Configure Packages tab, do one of the following: Create a new package definition.

  • Page 66: Setting Package Installation Options

    Symantec Packager installs Windows Installer only if the target computer does not have Windows Installer or has an earlier version. To include Windows Installer In the Symantec Packager window, on the Configure Packages tab, do one of the following: Create a new package definition.
  • Page 67 “Customizing optional installation panels” on page 75. To select an installation mode In the Symantec Packager window, on the Configure Packages tab, do one of the following: Create a new package definition. ■...
  • Page 68 Product restart requirements are specified in the product modules. If a package contains multiple products that require a restart, Symantec Packager lets you choose a restart option for the entire package. This suppresses individual product settings. You can configure a package to not restart the computer, to restart after installing each product that requires it, or to delay the restart until the entire package is installed.
  • Page 69 Configuring installation packages Configuring package definitions In the Package Editor dialog box, on the Installation Options tab, double- click Perform reboot(s). In the Reboot Options dialog box, under Reboot frequency, select one of the following: Do not reboot Installs the package without restarting the computer or prompting the user to restart.
  • Page 70 If prompted, type a file name, and then click Save. Setting installation rollback options Symantec Packager lets you restore, or roll back, a target computer to its original, preinstallation configuration if any part of the package installation fails. During the rollback, Symantec Packager removes the files that were installed, including drivers and configuration files, and it restores registry settings.
  • Page 71 Logging installation information Symantec Packager lets you record information about the installation in a log file. Upon deployment of a package, the log file is written to the system temp environment (%windir%\temp). For a local installation, the log file is written to the temp environment of the logged-in user.
  • Page 72 72 Configuring installation packages Configuring package definitions To log installation information In the Symantec Packager window, on the Configure Packages tab, do one of the following: Create a new package definition. ■ Double-click an existing package definition to edit it.
  • Page 73 This information is displayed on the optional installation panels during the package installation; therefore, the package definition must use Interactive installation mode. To include custom support information In the Symantec Packager window, on the Configure Packages tab, do one of the following: Create a new package definition. ■...
  • Page 74 For example, to add a custom Web address for technical support, in the Web address for support information box, type the URL as you would like it to appear on the screen. For example: http://www.symantec.com Click OK. In the Package Editor dialog box, do one of the following: Click OK to save your changes and close the Package Editor dialog box.
  • Page 75 Configuring package definitions Customizing optional installation panels Symantec Packager lets you customize the optional installation panels that the user sees during an interactive installation. This only applies to generic installation panels, such as the Welcome and Installation Complete panels, not the installation panels that are associated with specific Symantec products.
  • Page 76 152 pixels Leave remainder of bitmap blank To customize optional installation panels In the Symantec Packager window, on the Configure Packages tab, do one of the following: Create a new package definition. ■ Double-click an existing package definition to edit it.

  • Page 77: Building And Testing Packages

    As the package builds, Symantec Packager provides status information, so you can determine whether the package was built successfully.

  • Page 78: Testing Packages

    “Deploying installation packages” on page 79. To build packages In the Symantec Packager window, on the Configure Packages tab, select the package definition file that you want to build. On the File menu, click Build. The Package Build Status window appears, which provides information about the progress of the build and logs any problems that have occurred.

  • Page 79: Deploying Installation Packages

    About deploying packages When you are ready to deploy packages to your users, the self-extracting executable (.exe) files that you created using Symantec Packager are stored on the Deploy Packages tab. The Deploy Packages tab lets you do the following: Install a package on the local computer.

  • Page 80: Installing Packages On The Local Computer

    Package installations are supported on Microsoft 32-bit systems only (for example, Windows NT/2000/2003 Server/XP). Symantec Packager lists product .msi files on the Deploy Packages tab if they are supported and if you configured the Symantec Packager Preferences to show supported .msi files.

  • Page 81: Using The Package Deployment Tool

    Using the Package Deployment Tool To install packages on the local computer In the Symantec Packager window, on the Deploy Packages tab, select the package that you want to deploy to the local computer. On the File menu, click Install.

  • Page 82: Package Deployment Tool Requirements

    To specify the packages that you want to deploy In the Symantec Packager window, on the Deploy Packages tab, on the File menu, click Deploy. In the Package Deployment window, under File deployment sequence, click Add.

  • Page 83: Selecting Target Computers

    Deploying installation packages Using the Package Deployment Tool Repeat steps if you would like to add other packages. Under Target computers, select the target computers that will receive the package. “Selecting target computers” on page 83. Selecting target computers The Package Deployment Tool lets you select the target computers in the following ways: Select the target computers in the user interface, either by typing the ■...
  • Page 84 “Entering deployment authentication information” on page 86. Using package deployment files Symantec Packager lets you deploy packages using a preconfigured package deployment (.dpl) file. You can create this file yourself or set it up through the Package Deployment Tool. The package deployment file tracks the domain, computer name or IP address,...
  • Page 85 Deploying installation packages Using the Package Deployment Tool Figure 8-3 shows the contents of a sample package deployment file. Figure 8-3 Package deployment file data Domain=TESTSERVER Machine=TESTUSER1210 Package=PCANYWHERE.EXE LocalPath=C:\Documents and Settings\User_Name\My Documents\Packager\Deployment CommandLine=”PCANYWHERE.EXE” Status=Not Started Saving a package deployment file You can save the information in the Package Deployment window as a package deployment file.

  • Page 86: Entering Deployment Authentication Information

    86 Deploying installation packages Using the Package Deployment Tool Entering deployment authentication information The Package Deployment Tool requires that you authenticate to the target computer or the domain in which the target computers are located. You must have administrator rights on the target computers to deploy packages using the Package Deployment Tool.

  • Page 87: Viewing Deployment Status Information

    Deploying installation packages Using the Package Deployment Tool In the Password box, type the administrator password for the target computer. You can leave this box blank if your current credentials satisfy the authentication requirements. Click OK. Deployment status information displays. “Viewing deployment status information”...
  • Page 88 88 Deploying installation packages Using the Package Deployment Tool Table 8-1 details the status messages that the Package Deployment Tool displays. Table 8-1 Deployment status messages Icon Status Details Pending The package deployment has not started. In Progress The package deployment is in progress. Additional details include the following: Authenticating ■...
  • Page 89 Deploying installation packages Using the Package Deployment Tool Stopping deployment tasks The Package Deployment Tool lets you configure a deployment so that it ends any preexisting deployment task that it encounters or stops all pending tasks. When you deploy packages to target computers, some deployment tasks might not process as expected.

  • Page 90: Deploying Packages With Other Programs

    .msi files. Only Symantec pcAnywhere .msi files are supported for deployment. You can use the Web-based Deployment Tool that is supplied by Symantec or an industry-standard, third-party deployment tool to deploy the pcAnywhere .msi file. The Symantec Packager Deployment Tool does not support deployment of .msi files.

  • Page 91: Glossary

    (.pdt) file. product module (.pmi) A file that contains all of the files required to customize a Symantec product installation. file When you import a product module, Symantec Packager extracts the product template and creates a default product configuration file and package definition file based on that product.
  • Page 92 92 Glossary product template (.pdt) A file that dictates the selectable features, components, and installation options for a file Symantec product that is supported by Symantec Packager. See also product configuration (.pcg) file. silent installation An installation in which the user sees no indication that the installation is occurring. The user is not prompted to enter any information and the user does not see status messages.

  • Page 93: Index

    Index Symbols custom commands (continued) configuring parameters 52 .exe files creating 49 folder location for built commands 27 deleting 50 folder location for packages 27 displaying file details 50 .msi files examples 9, 13 folder location for testing products 27 folder location 27 listing on Deploy Packages tab 28 including optional files 54...
  • Page 94 72 changing product installation sequence 65 creating 61 customizing installation options 66 customizing installation panels 75 hiding or showing Symantec logo 28 deleting 62 displaying details 62 examples 10 icons, changing size and appearance of 28 folder location 27...
  • Page 95 Symantec Packager 19 user rights 20 view options viewing 63 changing icon size 28 restart 68 showing or hiding Symantec logo 28 roll back 70 viewing custom command details 50 deployment status information 87 saving package deployment files 85...
  • Page 96 96 Index...

This manual is also suitable for:

Packager - v 1.3Packager

Table of Contents