A command line determines how software is installed or uninstalled on the client computer. A command line that is associated with a software resource can run a package or run without a specific package. For example, a command line that is not associated with a package might run a batch file or repair an application.
The types of actions that a command line can perform depend on the type of installation that the package represents. They also depend on the platform that the package is installed on. For example, a command line for an MSI package can advertise the delivered software but a command line for an RPM package cannot. The most common command-line actions are installation and uninstallation.
A software resource can contain multiple command lines to perform different actions.
For example, a software resource that has an MSI package might have multiple command lines that perform the following actions:
Install the package silently.
Uninstall the package.
Apply a transform to the package.
Repair the package.
Install the package silently except for a progress bar.
By predefining the command lines for a software resource, you automate the software management actions and reduce the risk of user errors. For example, a user who needs to quickly deliver a software resource can select the software resource and the action to perform. For example, an installation or a repair. The user does not need to create a command line or even know the command-line syntax for the software package.
In a software delivery environment, you typically limit or hide the installation user interface.
For best results when you use command lines for software management, build the command lines according to the following guidelines:
A command line should never run in a way that requires user interaction.
For example, it should not prompt for installation configuration or display any messages that require the user to click any option or other control.
A command line should contain sufficient input data so that it can run without input from the end user.
Consider whether the command line requires the software package and set the package option on the command line accordingly.
For example, Windows Installer applications can be uninstalled or repaired without requiring the package. Instead, you can use the product code GUID value in the command line. By not needlessly delivering the software package you save network bandwidth during the software delivery.
You can create a command line that runs a package or that runs without a specific package.
When you import a supported installation file type into the Software Catalog, default command lines are created automatically. When you import a non-supported installation file, or when you add a software resource in any other way, you must create the command lines.
To create a command line for a software resource
In the Symantec Management Console, on the Manage menu, click Software Catalog.
In the Software Catalog window, do one of the following:
For an undefined software resouce, in the Newly discovered/undefined software pane, select it and then click the Edit symbol.
For a defined software resource, locate the software product that the software resource is associated with in the Managed software products or Unmanaged software pane. Then click the software product and in the Software Product dialog box open the required software resource from the list in the Identify inventroy tab.
On the software resource page, click the Package tab.
On the Package tab, add or edit the command line as follows:
To add a command line to the software resource, click Add command.
To edit an existing command line, select it in the Command Lines list and click Edit.
In the Add or Edit Command Line dialog box, define the command line and click OK.
For example, you use the Application Management agent command-line options to create the command line that runs the agent according to your specifications.