Novell ADMINSTUDIO 9.5 User Manual page 318

Chapter 6: Managing Application Catalog Databases
Reference
Table 6-26 • Application Manager Product View
Field
Original File
Imported On
Transforms
Patches
Groups
Description
Note • If the package and/or transforms are no longer in their original import directory, you can locate the file(s)
from the provided hyperlink. You are also informed if the last modified date for the package in the Application
Catalog does not match the last modified date of the package in its external location. You are given the opportunity
to reimport the package to keep it synchronized in the Application Catalog.
318
Description
When a user selects a Windows Installer package (
patch files ( ) to import, AdminStudio first performs an administrative
.msp
installation to merge the
the merged file into the Application Catalog. In this instance, the Original
.msi
File field lists the name and path of the original Windows Installer package that
the patches were applied to, while the File field lists the name and path of the
merged file that was imported.
.msi
If the package is part of the Software Repository, the following statement appears:
Managed within the Software Repository
Note • When a Windows Installer package that was imported without a patch is selected,
the entry of the Original File and File fields is identical.
The date and time the package was imported.
This can be either a hard-coded path or a UNC path.
The patch files that were used to get to the final imported MSI package.
Any groups to which the package belongs.
You can edit this with additional information about the product.
and files into one
.msi .msp
ADS-0950-UG00
) along with one or more
.msi
file, and then imports
.msi
AdminStudio 9.5 User Guide