Importing Multiple Files - Symantec SOFTWARE MANAGER 8.0 - REFERENCE FOR WISE PACKAGE STUDIO V1.0 Reference

Importing Multiple Files

Software Manager Reference
Note
If you will use Group Distribution, it is best to add packages to groups on the Group
Properties dialog box. The order in which you add packages to a group on the Group
Properties dialog box can affect the state of the package check boxes during
distribution.
7. Click Finish on the Import Type page.
The Wise Task Manager dialog box appears and remains open until the operation is
completed. However, you can close or minimize the dialog box and continue your
work in Wise Package Studio. From this dialog box, you can view a log file for the
import.
The package you selected is imported to the active Software Manager database.
During the import process, errors are displayed as they are encountered.
See also:
Package Import on page 34
Importing From the Share Point Directory
Wise Task Manager in the Wise Package Studio Help
You can import a batch of packages from any network or local directory you can access.
Use this method when you use the Network distribution method in Package
Distribution, or when the installations are saved on a network or local directory. When
you import multiple packages, all packages you specify must be of the same type. You
can import multiple packages of the following types:
Windows Installer installation (.MSI, .WSI)
Virtual software package (.VSA, .WVP).
WiseScript / SMS Installer installation (.WSE, .IPF)
Merge Module (.MSM, .WSM)
(Not available in Standard Edition.) InstallShield Developer setup.exe (.EXE)
(Not available in Standard Edition.) Device driver (.INF)
(Not available in Standard Edition.) Group Policy Object (.POL)
When you import a Windows Installer package, Software Manager preferences
determine which of the .MSI tables are imported into the Software Manager database: a
minimum number of required tables; or the required tables plus additional tables you
specify; or all tables. Importing additional tables can significantly increase the time it
takes to import a Windows Installer package. Empty tables are not imported.
See Setting Software Manager Preferences
Note
In general, do not import a package from a CD. If you do, you will not be able to export
the package after resolving its conflicts, because you will not have access to its source
files and you cannot write to a CD. However, when you import a package as part of the
Package Definition process, you can use a CD as the source because Package Definition
copies the source files to the share point directory.
on page 37
on page 24.
Importing Packages
68