Process For Deploying A Group - Symantec SOFTWARE MANAGER 8.0 - REFERENCE FOR WISE PACKAGE STUDIO V1.0 Reference

Process for Deploying a Group

Software Manager Reference
1. Complete the repackaging process.
Make sure that the package is ready for deployment. This includes resolving
conflicts and testing.
2. Make packages available.
Change the package's status to Available to indicate that it is ready for deployment.
See Changing the Package Status
3. Distribute packages to a network directory or to a distribution system.
Use Package Distribution to share or distribute the package. Distribute installable
files (example: .MSI or .EXE) from the Software Manager database.
See Package Distribution
Software Manager lets you deploy multiple related packages at once, enforcing package
dependencies and installation order, and defining command lines that run the package
installations. It also lets you install packages that you could not otherwise repackage
and deploy.
Examples:
Group a package with its related transforms and patches, specify the order in which
the transforms and patches are applied, and define the command lines that are
needed to run the transforms.
Group several packages that are always installed together and ensure that they are
installed in the correct order.
Run regsvr32.exe multiple times to register .DLLs outside the installation process.
Suppose you must install Package A, run regsvr32.exe to register a .DLL in Package
A, install Package B, run regsvr32.exe to register a .DLL in Package B, and so on.
Instead of deploying each of those packages separately, set up a group to deploy
them together.
Deploy an application and the contents of its installation CD without repackaging.
This can be in a group by itself or part of a group that contains other packages.
Create a group containing a single package that consists of a Setup.exe file of
unknown format and the command line to run it.
To prepare a group of packages for deployment, do the following:
1. Define and import packages.
In this step, you:
Define what is needed to install the package. At a minimum, this is a command
line. However, it can also be the installation file itself, additional command lines,
or any file that needs to be deployed. A package definition containing at least
one command line is required for any package that you include in a group
distribution, except for the following formats: .MSI, .WSI, .MSP, .MST, .WSE,
and .IPF. Those formats have default command lines, and Group Distribution
determines the installation file. However, by defining packages for any of those
Preparing Packages for Deployment
on page 108.
on page 129.
112