Symantec Packager Implementation Manual Download Page 95 | Manualshive

Page: 95 / 98

background image

95

Index

adding unsupported products to 51
building 77
changing product installation sequence 65
creating 61
customizing installation options 66
customizing installation panels 75
deleting 62
displaying details 62
examples 9
folder location 27
logging installation information 71
preconfiguring customer information 72
selecting installation mode 67
setting restart options 68
viewing details 61
viewing product requirements 63

package deployment files

importing 85
overview 84
saving 85

Package Deployment Tool

authenticating 86
overview 81
requirements 82
selecting target computers 83
specifying the packages to deploy 82

Packager.

See

Symantec Packager

packages

See also

package definition files

folder location 27
installing locally 80
overview 59
testing 78

passive installations 52, 67
preferences

changing data folders 27
changing icon appearance 28
hiding or showing Symantec logo 28

product .msi files, testing 45
product configuration files

adding to package definitions 63
building 44
creating 37
deleting 39
displaying details 38
examples 8
folder location 27

product modules

See also

custom commands

«
...
93
94
95
96
97
...
»

Summary of Contents for Packager

Page 1: ...Symantec Packager Implementation Guide ...

Page 2: ... information contained therein is at the risk of the user Documentation may include technical or other inaccuracies or typographical errors Symantec reserves the right to make changes without prior notice No part of this publication may be copied without the express written permission of Symantec Corporation 20330 Stevens Creek Blvd Cupertino CA 95014 Trademarks Symantec and the Symantec logo are ...

Page 3: ... Chapter 2 Installing Symantec Packager System requirements 19 System requirements for Symantec Packager 19 System requirements for installation packages 20 User rights requirements 20 Installing Symantec Packager 21 Installing Symantec Packager from the installation CD 21 Starting the Symantec Packager installation program manually 22 Uninstalling Symantec Packager 22 Chapter 3 Symantec Packager ...

Page 4: ...ng custom products 45 Chapter 6 Configuring custom commands About configuring custom commands 47 Working with custom commands 49 Creating custom commands 49 Viewing custom command details 50 Deleting custom commands 50 Configuring custom commands 51 Specifying command line parameters and switches 52 Including files in a command 54 Specifying operating system support 55 Building and testing custom ...

Page 5: ...tion packages About deploying packages 79 Installing packages on the local computer 80 Using the Package Deployment Tool 81 Package Deployment Tool requirements 82 Specifying the packages that you want to deploy 82 Selecting target computers 83 Entering deployment authentication information 86 Viewing deployment status information 87 Deploying packages with other programs 90 Glossary Index ...

Page 6: ...6 Contents ...

Page 7: ...our corporate environment by building packages that contain only the features and settings that your users need Symantec products that are included in installation packages are protected by copyright law and the Symantec license agreement Distribution of these packages requires a license for each user who installs the package Note Symantec Packager runs on Windows 2000 2003 Server XP Professional ...

Page 8: ...n create a custom command that contains the product installation and include that custom command in a package installation Table 3 1 Examples of product customization options Goal Solution Reduce deployment bandwidth and application footprint Symantec Packager lists optional and required features so that you can select minimal features for low bandwidth deployments Fewer features also decrease the...

Page 9: ...command line argument to execute it For example you want to uninstall a program on the target system before you install a new version You specify the command line argument and switches that execute the uninstallation for that program Copy files to the target system Symantec Packager lets you include files of any type in a custom command You can also specify where to copy those files on the target ...

Page 10: ... 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 Another group of users may require an upgraded version of their antivirus or firewall product You can create multiple packages that contain the custom commands and product installations that you need to accomplish this goal Figu...

Page 11: ...nary files and the product template The product template details the feature requirements and conflicts which makes it possible to create custom installations of the product See About the Import Products phase on page 12 To create a custom installation for an unsupported product you must use a custom command See About the Configure Products phase on page 13 Configure products and commands In the C...

Page 12: ...arty deployment tool such as Microsoft Systems Management Server SMS The Deploy Packages tab holds the packages that you create See About the Deploy Packages phase on page 16 About the Import Products phase Symantec releases product module pmi files for products that take advantage of Symantec Packager functionality such as Symantec pcAnywhere Product module files are comprised of all of the files...

Page 13: ... product is designed to take advantage of Symantec Packager it gives you the flexibility to select the features that you want your users to have It also lets you preconfigure installations with the settings that best match your software deployment needs 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 pac...

Page 14: ...nce and is not dependent upon any Symantec Packager files Figure 3 4 shows the process for creating custom products Figure 3 4 Configure Products process for custom products See Configuring custom products on page 35 Overview of custom commands During the Configure Products phase you can create custom commands that let you further customize your installation packages To do this you create command ...

Page 15: ...guring a single product installation package creation is optional However a package definition gives you more options for customizing the installation such as configuring restart and rollback options and adding custom support information Symantec Packager supports deployment of pcAnywhere msi files only On the Configure Packages tab you create a new package definition file by selecting from the pr...

Page 16: ... files that Symantec Packager creates as part of the Configure Products build process are not supported for deployment and therefore do not appear on the 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 dep...

Page 17: ...sing online Help The Symantec Packager online Help system has general information and step by step procedures to help you create installation packages To access online Help Do one of the following In the Symantec Packager main window on the Help menu click Help Topics In any Symantec Packager window press F1 Accessing the Symantec technical support Web site If you are connected to the Internet you...

Page 18: ...18 Introducing Symantec Packager Where to find more information ...

Page 19: ...e 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 Windows 2000 Professional Server with Service Pack 2 Windows 2003 Server Windows XP Professional Windows Vista Microsoft Internet Explorer 6 x or later Windows Installer 3...

Page 20: ...ly custom commands might run on additional operating systems However installed packages are supported on Microsoft 32 bit systems only The specific system requirements for packages depend on the package contents and options The hardware requirements for installation packages vary depending on the package contents User rights requirements Symantec Packager requires administrator rights for installa...

Page 21: ...ot appear automatically after you insert the installation CD run the setup program manually and then continue with the installation process See Starting the Symantec Packager installation program manually on page 22 You should close any applications that are open before you start the installation process To install Symantec Packager from the installation CD 1 Insert the installation CD into the CD...

Page 22: ...llation CD To start the Symantec Packager installation program manually 1 Insert the installation CD into the CD ROM drive 2 On the Windows taskbar click Start Run 3 In the Run dialog box type the letter that designates your CD ROM drive followed by Packager setup exe For example D Packager setup exe 4 Click OK 5 Install Symantec Packager See Installing Symantec Packager on page 21 Uninstalling Sy...

Page 23: ...anel window double click Add Remove Programs 4 In the Add Remove Programs window in the Currently installed programs list click Symantec Packager 5 Click Remove 6 When you are prompted to remove Symantec Packager data files do one of the following Click Yes to remove all Symantec Packager data files from the listed locations Click No to leave the data files on your computer Note the file location ...

Page 24: ...24 Installing Symantec Packager Uninstalling Symantec Packager ...

Page 25: ...e program 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 See Importing product modules on page 32 Product modules are only available for products that support Symantec Packager To create a package for an unsuppo...

Page 26: ...creen instructions Changing Symantec Packager Preferences and view options Symantec Packager lets you configure its data folders and view options The following options are configurable in Symantec Packager Preferences Specify the folder locations in which Symantec Packager stores its data files List supported product msi files on the Deploy Packages tab See Listing supported product msi files on t...

Page 27: ...ollowing Under Folder for Configure Products tab type a new path or click Browse to navigate to a new folder Symantec Packager stores product configuration files command configuration files and testable product msi and command exe files in this folder Under Folder for Configure Packages tab type a new path or click Browse to navigate to a new folder Symantec Packager stores package definition file...

Page 28: ...tab This option is not checked by default 4 Click OK Showing or hiding the Symantec logo Symantec Packager lets you customize your display by showing or hiding the Symantec logo that appears on each tab To show or hide the Symantec logo 1 Open Symantec Packager 2 In the Symantec Packager window on the Edit menu click Preferences 3 In the Preferences dialog box check or uncheck Show Symantec logo I...

Page 29: ...ons change depending on which tab you select When there are multiple ways to complete a step or procedure the Symantec Packager Implementation Guide details the menu structure Large Icons Displays file names and 32 x 32 pixel icons in rows from left to right Small Icons Displays file names and 16 x 16 pixel icons in rows from left to right List Displays file names and 16 x 16 pixel icons in column...

Page 30: ...30 Symantec Packager basics Accessing commands in Symantec Packager ...

Page 31: ...e the required and optional features and options that are available for each product The installation binary files are used by Symantec Packager to create custom installation packages The products that appear on the Import Products tab may vary If no products appear on the Import Products tab you might need to import product modules manually See Importing product modules on page 32 Note Product mo...

Page 32: ...u need to build custom installations 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 To create a package for an unsupported product you mus...

Page 33: ...n file that you can customize on the Configure Products tab It also creates a default package definition file that you can customize on the Configure Packages tab See Configuring custom products on page 35 Deleting products from Symantec Packager When you delete a product from the Import Products tab Symantec Packager removes the product template pdt file from the Import Products tab and the produ...

Page 34: ...34 Importing products in Symantec Packager Deleting products from Symantec Packager ...

Page 35: ... this process by selecting the features and options that you want to include for each product This information is saved in a product configuration file which is used in the Configure Packages phase to create packages The Configure Products phase depends on the successful completion of the Import Products phase You can only create custom products for which a product definition pdt file exists The b...

Page 36: ...g product features on page 39 Configure the installation options for the product See Setting product installation options on page 41 Include additional configuration files if necessary See Adding or removing configuration files on page 42 Build the custom product See Building custom products on page 44 Test the product before you deploy it See Testing custom products on page 45 The Configure Produ...

Page 37: ...porting product modules on page 32 Creating custom products The first step in creating a custom product is to create a product configuration file This opens the Product Editor dialog box which lets you configure and build the custom product Table 7 1 lists where to find the settings that you need Table 7 1 Overview of the Product Editor dialog box tabs Tab Description Reference Features Lets you c...

Page 38: ...ar in the Product Selection dialog box you might need to import a product module in Symantec Packager Click Cancel and return to the Import Products tab See Importing product modules on page 32 3 In the Product Editor dialog box click OK 4 In the Save As dialog box type a name for the custom product and then click Save The product configuration file appears on the Configure Products tab Viewing pr...

Page 39: ...nfiguring custom products You create a custom product by creating a product configuration file customizing product settings and then building the product configuration file The product configuration file contains information about the features and installation options that Symantec Packager requires to build a custom product Symantec Packager uses this information to construct installation package...

Page 40: ...og box on the Features tab do any of the following Check the product features that you want to include in the custom product Uncheck the features that you do not want to include Click the plus sign next to a feature to select or remove its subfeatures 3 Do one of the following Click OK to save your changes and close the Product Editor dialog box Click Apply to save your changes and continue config...

Page 41: ...lback and other installation options See Setting package installation options on page 66 Setting the product installation location Symantec Packager lets you configure the installation folder on the target system This includes the directory location such as the Windows Program Files directory or the root of the system drive as well as the folder in which the product is installed To set the product...

Page 42: ... options can vary widely by product For example Symantec pcAnywhere has additional installation options such as selecting a host object as a template or preserving existing configuration settings when installing over a previous version For more information about configuring these installation options see the documentation for the Symantec product Adding or removing configuration files Symantec Pac...

Page 43: ...nfiguration file types To add or remove configuration files 1 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 2 In the Product Editor dialog box on the Configuration Files tab do one of the following Click Add browse to the configuration file that you want to include and then click ...

Page 44: ...s If Symantec Packager encounters a conflict the build process stops You must resolve the conflict and repeat the build process 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 loca...

Page 45: ...cript msi If you are using only Symantec pcAnywhere with Symantec Packager you do not need to install ISScript msi Windows Installer 3 1 To test custom products 1 On the Windows taskbar click Start Run 2 In the Run dialog box type the following explorer exe 3 In Windows Explorer navigate to the Configure Products data folder Data folders are listed in Symantec Packager Preferences See Changing Sym...

Page 46: ...46 Configuring custom products Building and testing custom products ...

Page 47: ...tables command line arguments or simple file copies Custom commands let you simplify application deployment by including multiple tasks in one package Once defined you can reuse custom commands in different packages When you create a custom command Symantec Packager creates a command configuration file A command configuration file is a generic product configuration file that does not reference a p...

Page 48: ...product configuration and custom command files Figure 8 1 Configure Products tab showing a custom command Creating a custom command involves the following process Create a custom command file See Creating custom commands on page 49 Specify command line parameters and switches See Specifying command line parameters and switches on page 52 Include optional files See Including files in a command on p...

Page 49: ...st step in configuring a custom command is to create a custom command file This opens the Command Editor dialog box which lets you configure and build the custom command Like product configuration files custom command files are saved with pcg file extensions Table 8 1 includes information about the configuration options Table 8 1 Command Editor options Tab Description For more information Paramete...

Page 50: ...figure Products tab Viewing custom command details Symantec Packager lets you view the details of a custom command file without opening the file A summary of the custom command specifications is available using the Display Details option To view custom command details 1 In the Symantec Packager window on the Configure Products tab select the custom command file that you want to view 2 On the File ...

Page 51: ...d products to a package adding product updates or patches 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 Like custom products the configuration information for custom commands is saved in product configuration files However unlike custo...

Page 52: ...ctive package installation You must specify the information that Symantec Packager needs to install and run the command and any variables that you want to use To specify command line parameters and switches 1 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 Enter a command line argument to ...

Page 53: ...n uses the following types of switches to make the command installation mimic the package installation 5 Under Run options select how the command installation should appear to the user as follows Silent mode Specify the switch that suppresses all user interaction Interactive mode Specify the switch that suppresses user interaction while still displaying status messages Suppress reboot Specify the ...

Page 54: ...ystem 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 You only have to type the subfolder name to place the files in a subfolder of the Program Files or root directory If you select a custom path you must type the full path To include files in a command 1 In the Symantec Packager window on the Con...

Page 55: ...under Sample path 7 Click OK 8 In the Command Editor dialog box do one of the following Click OK to save your changes and close the Command Editor dialog box Click Apply to save your changes and continue configuring the command 9 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 Packag...

Page 56: ...tems on which the custom command can run The default selection is Any operating system You can limit the installation by category for example all Windows NT platforms by specific operating system for example Windows 2000 and Windows XP or by any combination for example all Windows NT platforms plus Windows 98 and Windows 98 SE 3 Do one of the following Click OK to save your changes and close the C...

Page 57: ...reates a self extracting executable exe file and places it in the folder that is specified for the Deploy Packages tab The command exe file is supplied for testing purposes and is not supported for deployment To build custom commands 1 In the Symantec Packager window on the Configure Products tab select the custom command that you want to build 2 On the File menu click Build A Build Status window ...

Page 58: ...d you include that custom command in a package the installation stops until the user responds to the prompt To test custom commands 1 On the Windows taskbar click Start Run 2 In the Run dialog box type explorer exe 3 In Windows Explorer navigate to the working directory of the Deploy Packages tab Data folders are listed in Symantec Packager Preferences See Changing Symantec Packager data folders o...

Page 59: ...nition pkg file If your product supports msi deployment and you are configuring a single product installation package creation is optional However a package definition gives you more options for customizing the installation such as configuring restart and rollback options and adding custom support information Symantec Packager supports deployment of pcAnywhere msi files only The Configure Packages...

Page 60: ... or more products and custom commands See Adding products and commands to a package definition on page 63 Specify the installation sequence for packages that contain multiple products or custom commands See Changing the installation sequence on page 65 Specify package installation and logging options See Setting package installation options on page 66 Build the package See Building and testing pac...

Page 61: ... Building custom products on page 44 See Building custom commands on page 57 Creating package definitions The first step in creating a package is to create a package definition file This opens the Package Editor dialog box which lets you configure and build the package As you add or remove products or custom commands the bottom left portion of the dialog box displays the approximate size of the in...

Page 62: ... 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 To view package definition details 1 In the Symantec Packager window on the Configure Packages tab select the package definition file that you want to view 2 On the File menu click Display Details 3 Click OK to cl...

Page 63: ...ionally a package definition file can include technical support information 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 Edito...

Page 64: ... definition to edit it 2 In the Package Editor dialog box on the Product Selection tab click Add 3 In the Open window select the product or custom command configuration pcg file that you want to add 4 Click Open The Estimated package size in the bottom left portion of the dialog box changes to reflect the product or command that you include 5 Repeat steps 2 through 4 to add more products or custom...

Page 65: ...u can change the order in which a product is installed by moving it up or down in the installation sequence list To change the installation sequence 1 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 2 In the Package Editor dialog box on the Product Selection tab under Instal...

Page 66: ...e package Windows Installer is installed first During installation Symantec Packager checks the target computer to determine if Windows Installer is already installed Symantec Packager installs Windows Installer only if the target computer does not have Windows Installer or has an earlier version To include Windows Installer 1 In the Symantec Packager window on the Configure Packages tab do one of...

Page 67: ... installations provide a user interface that steps users through the installation You can further customize an installation by adding a brand name or by replacing product specific installation graphics with custom graphics See Customizing optional installation panels on page 75 To select an installation mode 1 In the Symantec Packager window on the Configure Packages tab do one of the following Cr...

Page 68: ...ains 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 You can also configure the package to restart the computer a...

Page 69: ... installation of each product that requires a restart This option preserves product restart settings If you select this option also specify whether the computer restarts automatically or prompts the user before restarting You can optionally click Ensure reboot at end of package installation to add a restart at the end of the package installation if one does not already exist Delay reboot until end...

Page 70: ... and it restores registry settings Installation rollback does not apply to custom commands that might be included in the package To set installation rollback options 1 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 2 In the Package Editor dialog box on the Installation Opti...

Page 71: ...e following Click OK to save your changes and close the Package Editor dialog box Click Apply to save your changes and continue configuring the package definition 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 ...

Page 72: ...the Package Editor dialog box do one of the following Click OK to save your changes and close the Package Editor dialog box Click Apply to save your changes and continue configuring the package definition 6 If prompted type a file name and then click Save Preconfiguring user information During an interactive package installation users are prompted for a user or group name and a company name Symant...

Page 73: ...nges and continue configuring the package definition 7 If prompted type a file name and then click Save Including custom support information Symantec Packager lets you specify a Web address phone number and other custom support information This feature for example lets value added resellers VARs and original equipment manufacturers OEMs create custom installation packages that include their own We...

Page 74: ...pport information as you would like it to appear on the screen 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 5 Click OK 6 In the Package Editor dialog box do one of the following Click OK to save your changes and close the Package Editor dialog ...

Page 75: ...r provides installation graphics or you can use your own custom graphics If you use a custom bitmap that does not adhere to the size and color specifications the installation program will stretch or shrink the bitmap to the appropriate size This does not affect how the package installation functions but it does impact the look of the panels Use the following specifications if you create your own c...

Page 76: ... optional installation panels in interactive mode A preview of the Symantec Packager graphics appears in the top bitmap and background bitmap preview areas If this option is unchecked optional installation panels do not display during installation 4 In the Package title field type a package title The package title appears on the optional installation panels during package installation 5 Click Incl...

Page 77: ...al step in creating the installation package The build process uses the information from the package definition file and product configuration files to create an installation file that you can deploy to end users As the package builds Symantec Packager provides status information so you can determine whether the package was built successfully Building packages During the build process Symantec Pac...

Page 78: ...loy them to end users to ensure proper functionality Although some error checking occurs during the build process some errors cannot be detected until installation This is especially true if the package includes a product that requires a third party product or if the package includes a custom command During installation Symantec Packager checks for product conflicts and verifies that required prod...

Page 79: ...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 See Installing packages on the local computer on page 80 Deploy one or more packages to one or more computers using the Package Deployment Tool The Package Deployment Tool supports deployment to Microsoft Windows 2000 2003 Server XP Vista T...

Page 80: ...s tab Installing packages on the local computer When you deploy a package locally you open the self extracting executable exe file on the Deploy Packages tab This installs the package on the local computer Package installations are supported Windows 2000 2003 Server XP Vista Symantec Packager lists product msi files on the Deploy Packages tab if they are supported and if you configured the Symante...

Page 81: ...etwork You can deploy packages to multiple computers by browsing for computers from the user interface using a preconfigured list of target computers or using a preconfigured package deployment dpl file Figure 10 2 shows the Package Deployment window Figure 10 2 Package Deployment window List systems that will receive the package List packages that will be deployed Use a preconfigured package depl...

Page 82: ... operating systems for example Windows 2000 2003 Server XP Vista You must have an administrator user name and password on the target computers and the administrator user name and password must be the same for all target computers The easiest way to accomplish this is for all target computers to be in the same domain and for you to use a domain administrator user name and password An administrator ...

Page 83: ...user interface If you know the computer names or IP addresses of the computers to which you want to deploy packages enter the information in the Package Deployment window You can also search across domains Note All computers in your Network Neighborhood appear in the browse list regardless of their operating systems This deployment tool supports only Microsoft 32 bit operating systems for example ...

Page 84: ...n the Package Deployment window add the package or packages that you want to deploy See Specifying the packages that you want to deploy on page 82 2 Under Target computers click Import List 3 Browse to the preconfigured target computer list and then click Open 4 In the Package Deployment window click Deploy 5 In the Deployment Credentials dialog box type the authentication credentials required to ...

Page 85: ...loy to the same set of computers on a regular basis you can edit the package deployment file to reflect the appropriate package file name and path instead of browsing for the computers through the user interface To import a preconfigured package deployment file 1 In the Package Deployment window click Open 2 Browse to the package deployment file and then click Open The details of the package deplo...

Page 86: ... that you want to deploy 2 Under Target computers select the target computers that will receive the package 3 In the Package Deployment window click Deploy 4 In the Deployment Credentials dialog box in the Share name box type the drive letter for the administrator share on the target computer The default share is C 5 In the Path on target box type a temporary location to which the deployment tool ...

Page 87: ...ployment Status dialog box the Package Deployment Tool displays the computer name the name of the package being deployed and the status of the deployment task In the Deployment Status dialog box you can do the following View the status of deployment tasks and interpret the results Stop a deployment task Save deployment status information in a log file Interpreting deployment status information The...

Page 88: ...rienced an error When possible the tool displays details about the error Additional details include the following Failure launching deployment mechanism Authentication failure File copy failed Unable to install remote service Unable to start remote service Failure executing User interrupted Unknown The status of the package deployment is unknown Complete The package deployment completed successful...

Page 89: ...eads continue to process until the deployment tasks are complete To stop preexisting deployment tasks 1 In the Package Deployment window check If encountered stop existing deployment tasks 2 Configure the remaining deployment details and then click Deploy To stop pending deployment tasks 1 In the Deployment Status dialog box click Stop The Stop button changes to a Close button when the tasks are c...

Page 90: ...les 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 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 ...

Page 91: ... See also command configuration pcg file product configuration pcg file package deployment dpl file A file that can be imported into the Package Deployment Tool to assist in package deployment The file details the domain computer name or IP address the package to be deployed and its location on the local computer the command line argument to execute the package installation and the status of the d...

Page 92: ...ser 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 See also interactive installation passive installation switch A command that when applied to a command line argument or executable changes the behavior of the command line argument or executable Windows Installer A program that processes Microsoft So...

Page 93: ...product configuration files 37 custom commands adding to package definition files 63 building 57 configuring parameters 52 creating 49 deleting 50 displaying file details 50 examples 8 13 folder location 27 including optional files 54 selecting operating system 55 specifying target path for files 54 testing 57 custom products See product configuration files customer information preconfiguring 72 D...

Page 94: ...s 75 installation mode 67 log files 71 restoring preinstallation settings 70 installer program 66 installing packages locally 80 Symantec Packager 19 interactive installations 52 67 L license agreement 7 LiveUpdate 26 log files 71 O online Help accessing 17 opening online Help 17 opening Symantec Packager 25 order installation 65 overview Configure Packages phase 15 Configure Products phase 13 Dep...

Page 95: ...mporting 85 overview 84 saving 85 Package Deployment Tool authenticating 86 overview 81 requirements 82 selecting target computers 83 specifying the packages to deploy 82 Packager See Symantec Packager packages See also package definition files folder location 27 installing locally 80 overview 59 testing 78 passive installations 52 67 preferences changing data folders 27 changing icon appearance 2...

Page 96: ...lent installations 52 67 stopping pending deployment tasks 89 preexisting deployment tasks 89 support information customizing 73 switches custom commands 52 Symantec logo showing or hiding 28 Symantec Packager changing data folders 27 changing icon appearance 28 installing 19 learning more about 17 opening 25 overview of phases 11 system requirements 19 uninstalling 22 updating 26 system requireme...

Page 97: ...ame preconfiguring 72 V view options changing icon size 28 showing or hiding Symantec logo 28 viewing custom command details 50 deployment status information 87 package definition file details 62 product configuration file details 38 W Web site adding to packages 73 Symantec technical support 17 Windows Installer including 66 ...

Page 98: ...98 Index ...

Reviews:

No comments

Related manuals for Packager

TRANSCEND EM/NT 6.3

Brand: 3Com Pages: 39

GROUPWISE 7 - WEB ACCESS

Brand: Novell Pages: 110

Brand: ZixCorp Pages: 44

Electric Bass Vol. 1—Rock

Brand: M-Audio Pages: 4

DRUMBEAT 2000 ECOMMERCE EDITION

Brand: MACROMEDIA Pages: 238

Ripstation v4.4.11.0

Brand: MF DIGITAL Pages: 43

Brand: SanDisk Pages: 18

Brand: Tascam Pages: 6

Brand: Elgato Pages: 5

Brand: Better Light Pages: 99

Brand: DigiDesign Pages: 39

Brand: Zing Magic Pages: 10

ALTIRIS DEPLOYMENT SOLUTION

Brand: Symantec Pages: 3

IRISPOWERSCAN 9

Brand: I.R.I.S. Pages: 12

Brand: Franklin Pages: 32

DuraStor 6220SS

Brand: Adaptec Pages: 133

Brand: Adaptec Pages: 174

Brand: TomTom Pages: 58

Brands by name

0 1 2 3 4 5 6 7 8 9 A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

Popular brands

Load more brands