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

Software Manager Reference
When you successfully import a package from the share point directory, its .QUE file is
deleted and the package information is added to the Software Manager database. Paths
to the new source file locations are also updated in the package installation file, except
for Wise package definition files.
See About .QUE Files on page 40 and How Source Files Are Indexed in the Wise Package
Studio Help.
(Enterprise Management Server only.) You also can use the Auto Import Service
scheduled task to import packages from the share point automatically.
See About the Auto Import Service
Note
When you use either Windows Installer Editor or WiseScript Editor to add files to a
package that has already been distributed to the share point directory and imported, a
prompt appears asking if you want to add the new files to the share point directory. If
you do so, the .QUE file for that package is reset and you must re-import the package in
Software Manager. If you have already detected conflicts for that package, you must
also redo the conflict detection process.
To import a package from the share point directory
1. (Enterprise Management Server only.) If multiple databases are open, select a
database in the Applications/Packages pane.
2. Select Packages menu > Import.
The Import Type page appears.
3. Mark Import from share point directory.
Distribute source files to the share point directory is marked automatically
and unavailable.
It is unavailable because the source files were copied when the package was
distributed to the share point or because Wise package definition files do not have
source files.
The following items become enabled:
Overwrite existing application and package
Mark this to overwrite any package that is already in the database with the
same application and package names.
If you clear this check box and the application and package names are already
in the database:
If the existing package has resources, the new package is not imported.
If the existing package does not have resources, the new package's
resources are added to the existing package. An existing package might not
have resources if it consists only of meta data or a package definition.
Do not modify the original package
Normally, when you import a Windows Installer installation (.MSI or .WSI), the
original installation file is updated with Wise-specific version information that
speeds future subscriptions and imports of the installation. Mark this to prevent
the original file from being changed.
on page 74.
Importing Packages
38