Home
> e-infrastructure, service-is-it-managing > How to comprehensively identify your software packages using the MS-Installer infrastructure
How to comprehensively identify your software packages using the MS-Installer infrastructure
- Problem:
- Some packages may have built-in checks which prevent installation. The built-in error messages may be difficult to interpret (even if you speak foreign languages).
- Some built-in checks may be erroneous.
- Product name and version may be difficult to identify.
- Etc.
- Solution: Take advantage of the features of the MS Installer infrastructure.
- If necessary (setup file does not come as an MSI file), try to unpack your setup file (7zip alone will work in many cases. There are more advanced free extractors available on the web).
- with the the unpacked MSI’s
- run with the “/log” parameter and to generate and examine the log file for more speaking (an English!) installation errors.
- Open with MS-Orca to examine the software package properties:
.
- Right-click and “copy cell” :
- Esp. note the following:
- “Make”
- Productname (base, qualified) variants
- “Model”
- GUID for Upgradecode (e.g. {00140000-0028-0000-1000-0000000FF1CE})
- Productname
- “Year”:
- GUID for Productcode ({90140000-0028-0804-1000-0000000FF1CE})
- ProductVersion
- “Make”
- you can edit your MSI with MS-Orca (better be sure what you are doing).
- you can compare this installer package with what you already have installed in the registry
- use a registry search tool
- you have to search the registry for the compressed GUIDs, to compress, use this: https://thomasplagwitz.com/tag/guid/.
Categories: e-infrastructure, service-is-it-managing
GUID, MS-ORCA, msi
Comments (0)
Trackbacks (0)
Leave a comment
Trackback