Symantec 14541094 Implementation Guide - Page 9

Include custom commands with product installations, Table 1-2, Solution

Page 9 highlights

Introducing Symantec Packager 9 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. Examples of custom commands include running executable files, Microsoft Software Installer (.msi) files, batch files, and so on. If you can run a command from the command line, you can create a custom command for it. In addition to running programs from the command line, you can also create a custom command that copies files to the end user's system. Table 1-2 lists examples of how you can use custom commands. Table 1-2 Examples of custom commands Goal Solution Execute a command on the target If the file or command that you want to execute is system. already on the target system, you can specify the 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 system. For example, you want to roll out an updated file for an application that you use. You include the file in a custom command and specify the destination on the target system. Copy a file and execute it on the target system. If the file that you want to execute is not already on the target system, you include the file in the custom command, the destination location on the target system, and the command-line argument to execute that file on the target system. For example, you want to include a text file in a package so that it displays at the end of the installation. You include the text file in a custom command and specify a command-line argument that opens that text file in Notepad. See "Configuring custom commands" on page 47.

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96

9
Introducing Symantec Packager
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.
Examples of custom commands include running executable files, Microsoft
Software Installer (.msi) files, batch files, and so on. If you can run a command
from the command line, you can create a custom command for it.
In addition to running programs from the command line, you can also create a
custom command that copies files to the end user’s system.
Table 1-2
lists examples of how you can use custom commands.
See
“Configuring custom commands”
on page 47.
Table 1-2
Examples of custom commands
Goal
Solution
Execute a command on the target
system.
If the file or command that you want to execute is
already on the target system, you can specify the
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 system.
For example, you want to roll out an updated file for
an application that you use. You include the file in a
custom command and specify the destination on the
target system.
Copy a file and execute it on the
target system.
If the file that you want to execute is not already on
the target system, you include the file in the custom
command, the destination location on the target
system, and the command-line argument to execute
that file on the target system.
For example, you want to include a text file in a
package so that it displays at the end of the
installation. You include the text file in a custom
command and specify a command-line argument that
opens that text file in Notepad.