Performing A Universal Import Without Converting Or Repackaging - Symantec SOFTWARE MANAGER 8.0 - REFERENCE FOR WISE PACKAGE STUDIO V1.0 Reference

Performing a Universal Import Without Converting or Repackaging

Software Manager Reference
You can use the Import Wizard's Universal Import option to import any 32-bit setup
program into the Software Manager database from a network or local drive without
converting or repackaging. Do this to get information about the resources installed by a
non-Windows Installer or non-WiseScript installation. This provides a quick way to
determine if the installation conflicts with other packages. If no conflicts are found when
you import the installation directly, and if you do not need to make any other changes to
the installation, you might decide to distribute the original executable. In other
instances, you might use this to identify conflicts between newly repackaged
applications and legacy setup.exe installations that have already been deployed and that
you have no intention of repackaging. Corporate developers can use this to view
resources for non-Windows Installer installations without converting them.
The Universal Import is also triggered when you mark the option to import a single file,
and you specify an .EXE file that is not recognized as an importable package type.
The Import Wizard uses Virtual Capture™ technology to extract information from the
installation file, and then saves the captured information to the Software Manager
database, creating an application and package. You also can choose to have the
installation's source files copied to the share point directory.
Universal Import uses a Virtual OS created in the Virtual OS Creation utility, which you
must create before using the procedure below. See Creating a Virtual OS in the Wise
Package Studio Help. Verify that your environment meets the conditions for using
Universal Import. See Using SetupCapture With Virtual Capture in the Wise Package
Studio Help. The Virtual Capture process described in this procedure uses the same
SetupCapture Configuration settings you have set in Wise Package Studio. (See
SetupCapture Configuration in the Wise Package Studio Help.)
You cannot resolve conflicts in or export a non-Windows Installer or non-WiseScript
package, because the original installation file cannot be edited. However, you can
change packages that conflict with the installation.
You can distribute a non-Windows Installer or non-WiseScript package as part of a
group for easy deployment by a distribution system. To do so, import the package,
create a package definition file, and then add it to a group for deployment.
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 package from Software Manager into Software Management
Framework. You can then use Software Management Solution to distribute the package.
To import any installation file without converting or repackaging
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 Universal Import.
The following items become enabled:
on page 115 and Creating Package Groups
Importing Packages
on
71