Importing A Transform File - Symantec SOFTWARE MANAGER 8.0 - REFERENCE FOR WISE PACKAGE STUDIO V1.0 Reference

Importing a Transform File

Software Manager Reference
You can import a Windows Installer transform (.MST) into the Software Manager
database from a network or local drive. This creates a separate package for the
transform and keeps the transform's resources separate from the resources in the base
package.
To add the transform's resources to the base package instead, apply the transform when
you import the base installation. When you do this, you cannot distribute the transform
as a separate entity.
You can distribute the transform as part of a group for easy deployment by a distribution
system.
See Creating a Package Definition
page 88.
Note
If you have Symantec Management Platform 7.0 SP2 or later, you can use Wise
Connector to import the transform from the Software Manager database into Software
Management Framework. Wise Connector imports the transform when it imports the
base MSI package. You can then use Software Management Solution to distribute the
package.
See Importing a Windows Installer File
Options for Applying Imported Transforms
Apply the transform to a blank Windows Installer database (schema.msi).
The resulting transform package includes additions only and excludes deletions and
modifications. The transform package has no dependencies. You might use this
option when you have a standard, corporate transform that you apply to all
packages. (Example: General Application Registration Transforms.)
When you apply the transform to a blank Windows Installer database, you cannot
resolve conflicts in or export the transform package.
If the transform contains file additions that are in components of the base
installation, those files are not imported with the stand-alone transform package
because they only apply to the specific base installation.
Example: Suppose the base package contains Component A. The transform adds
File 1 to Component A, and adds File 2 to a new Component B. When you import the
transform and apply it to a blank database, File 2 is imported as a resource but not
File 1.
Certain transforms cannot be applied to a blank database. The transform you
specify is checked before the import begins and a message appears if it cannot be
applied to the blank database.
Apply the transform to a base package.
The resulting transform package includes all additions, deletions, and modifications
to the base package. The transform package is designated as a dependent of the
base package.
When you apply the transform to a base package, you can resolve conflicts in and
export the transform package.
on page 115 and Creating Package Groups
on page 40.
Importing Packages
on
48