MSI and it's brethren MSU, MSP, and MST[转]

dougsk:

Looking through logmein central, was curious about the differenciation between an MSI file and it's partners, MSU (update), MSP (patch), MST (Transfrom), it seems MSI really only means file extensions that end with MSI, is that correct?

 

TomRBerg:

An MSI file contains the actual program files and a set of rules for how to install and uninstall the program in question. MSI-files are installed through the MSIEXEC program built into Windows. Through command line parameters to MSIEXEC you can "answer" the questions the rules have directly on the command line, or point MSIEXEC to use an MST file.

An MST file usually contains answers to the questions in the MSI file (licence agreement, installation paths, which features to install etc) and is linked to an MSI file. Office 2003 Resource Kit lets you create MST files to configure and "drive" an Office 2003 or earlier installation.

ORCA (part of the Windows SDK) and "Installation Tuners" (like what is available at adobe.com for Acrobat or the Office 2003 Resource Kit) allows you to create your own MST files for these programs. While the MSI format itself is an open and "standard" format, a tuner tool is always preferable because you may not know or find documentation on what the MSI rules mean for the particular package. ORCA lets you dig directly into the MSI and see the raw data and edit the MSI or create MSTs. ORCA usually involves a lot of trial and error if you cannot get documentation from the software developer. There are also 3rd party MSI editors available.

You can install MSI and MST files using the msiexec program or using the GPI (Group Policy Installer) part of a group policy object.

An MSP file does the same thing as an MST file, but can contain binary data (is my understanding at least! I am probably unprecise). The Office 2007 or later setup tool creates MSP files instead of MST files. You cannot use MSP files in a Group Policy installation to control the process, but through tweaking of XML files and careful placement of the MSP file its possible to deploy Office 2007 or later using GPOs. The Office 2007 or later resource kit documentation has more details.

An MSU file is a Windows Update package. It basically integrates with the Windows Update service and installs a Windows update from a file using the Windows Update engine. When installed, it can be uninstalled as a usual Windows update package.

 

http://community.logmein.com/t5/Central/MSI-and-it-s-brethren-MSU-MSP-and-MST/td-p/62934