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

Software Manager Reference
View Package Resources
Use the panes in Software Manager to drill down to the resources (examples: files,
registry keys, merge modules, shortcuts, and so on) that are used by each package.
See About the Software Manager Window
Properties on page 94.
Use the reports to obtain information about file, registry, and merge module
resources in the Software Manager database.
See Software Manager Reports
Use a table query to query the package data of Windows Installer packages.
See Windows Installer Table Queries
If an .MSI contains a merge module, the resources that appear under the Merge
Modules folder also appear in the corresponding folders elsewhere in the package.
(Example, if an .MSI contains a merge module that has .DLL files in the system32 folder,
these files will appear in the system32 folder under the package's Merge Modules folder
and Files/Directories folder.) If a .WSI contains a merge module, the Merge Modules
folder and some of its subfolders appear, but none of the merge module's resources
appear.
Files that you add when you define a package do not appear in Software Manager.
Update Packages
Use the Merge Module Wizard to perform operations on .MSI or .WSI packages that
add, remove, or replace merge modules.
See Merge Modules Wizard
Use the Multi-Package Compile Wizard to compile and update a set of packages.
See Compiling Multiple Packages
Prepare Packages for Deployment
Use a Wise package definition to define what is needed to install a package. This lets
you use group distribution to prepare the package for deployment.
See About Package Definition
Use package relationships to define which packages depend on other packages.
During group distribution, package relationships determine the packages that are
installed and the order in their installation.
See About Package Relationships
Use impact and risk assessment to identify problems that might occur as a result of
installing a hotfix or patch.
See Impact and Risk Assessment
Use the SVS Enabled Package option to create a package that installs the package
as a layer if the Software Virtualization Agent is present. If the Software
Virtualization Agent is not present, the package is installed normally.
See About SVS Enabled Packages
Use Package Distribution to share or distribute a single package from Workbench or
from Software Manager.
See Package Distribution
on page 13 and
on page 98.
on page 95.
on page 102.
on page 107.
on page 114.
on page 120.
on page 125.
on page 128.
on page 129.
Introduction to Software Manager
Viewing Resource
11