Symantec SOFTWARE MANAGER 8.0 - REFERENCE FOR WISE PACKAGE STUDIO V1.0 Reference page 117

If the file is:
An .MSI that is in the package
definition.
A Microsoft hotfix that is in the
package definition. (For
information on Microsoft hotfixes,
search for "Command-Line
switches for Windows software
update packages" at
msdn.microsoft.com.)
Not an .MSI or hotfix.
Or
Not in the package definition.
Software Manager Reference
9. This step depends on the file that you are creating the command line for:
Then:
Click Select File.
Select the .MSI and click OK. The Command Line Builder for Windows
Installer opens.
See Command Line Builder in the Wise Package Studio Help.
Use the Command Line Builder to build the command line and click OK.
When the command line appears in the Command Line Builder, it
includes the drive letter for the file. Because Package Definition uses
relative paths, it removes the drive letter.
We recommend that you first run the hotfix with the /? command-line
option to display a list of all the command-line options for that
particular hotfix. Otherwise, you might choose command lines that are
not appropriate for the hotfix.
Click Select File.
Select the Microsoft hotfix file and click OK.
On the Hotfix Patch Command Lines dialog box, select command-line
options and click OK.
Enter the command line on the Specify Command Line dialog box.
To add the name of a file that is in the definition, click Select File and
select it.
Because Package Definition uses relative paths, use relative paths in the
command line. If you specify a directory, the command line will look for the
file in that directory on the destination computer.
Note
Command lines that you enter on the Specify Command Line dialog box are not
validated. Be sure to test your command lines.
10. Click Next on the Specify Command page.
The Finish page appears. The Package Definition Summary describes where the
project and its files will be saved.
11. On the Finish page:
Import into Software Manager
Mark this to import the package definition file into the Software Manager
database. Clear this to have the package definition file queued for import into
the database.
Datasource
If you have multiple Software Manager databases, you can select the database
to import to.
12. Click Finish.
The package definition file is saved in its own subdirectory in the share point
Projects directory. All the files that you specified are copied to a Files subdirectory of
the package definition directory.
Preparing Packages for Deployment
117