A Windows Installer Transform (.mst) contains a set of alterations to a Windows installer package (.msi). In order to correctly view the changes a transform makes, the .msi package that served as the 'original' should be used as the base package. Read on to learn what the MST viewer is and how to get some mileage out of it.

The MST File Viewer is automatically installed on your computer when you install the Office Resource Kit (orktools.exe).

The MST File Viewer (MSTView.exe) enables you to view customizations a transform (MST file) makes to a user's computer. Transforms are created by using the Custom Installation Wizard.

To use the MST File Viewer, you must supply it with the path and file name of the MST file you created with the Custom Installation Wizard. The MST File Viewer is not a separate application — instead, it reads the MST file and creates a plain-text file containing readable content. The information is then displayed through the Notepad text...

Here's a nifty tool I found that makes working with MSIs a real joy.... Exaggeration? maybe, but this tool's sweet (and free).

A common use MSIDiff is to automate changes you wish to apply over and over again to MSIs produced by other tools.

To do this you start by first manually making (and testing) the proposed changes using a table editing tool similar to the free "ORCA" tool and then using MSIDIFF to generate the code to perform these changes.

The generated output (typically with minor changes) is then executed via the (also free) MAKEMSI tool (you may have made it more generic so parameters are passed into it).

Download MSIDIFF here.

Uninstallation for the Installshield applications sometimes use rundll32.exe. Here are some of the different silent uninstallation cmd lines that I've come across:

1. RunDll32
   

   C:\PROGRA~1\COMMON~1\INSTAL~1\PROFES~1\RunTime\0701\Intel32\Ctor.dll,LaunchSetup "C:\Program Files\InstallShield Installation Information\{BBDE6ABE -EF72-4752-9C09-EE9D6DE3102A}\Setup.exe" -l0x9 AnyText -remove -s -f1c:\Uninstall.iss
   
   

2. RunDll32
   

   C:\PROGRA~1\COMMON~1\INSTAL~1\PROFES~1\RunTime\0701\Intel32\Ctor.dll,LaunchSetup "C:\Program Files\InstallShield Installation Information\{BBDE6ABE-EF72-4752-9C09-EE9D6DE3102A}\Setup.exe" -l0x9 AnyText /s /f1c:\Uninstall.iss
   
   

3. RunDll32
   

   C:\PROGRA~1\COMMON~1\INSTAL~1\engine\6\INTEL3~1\Ctor.dll,LaunchSetup "C:\Program Files\InstallShield Installation Information\{5CE1EF14-2595-4320-A638-A627EE1D1BB9}\Setup.exe" -l0x9 -uninst -s
   
   

This piece...

If your application requires installation of components such as files or registry keys on a per-user basis, but your application has no advertised entry points or other triggers to initiate the installation process, then Active Setup is the solution.

What is Active Setup?

Active setup is a process that runs automatically when a user logs in.

How Does Active Setup Work?

Registry keys at HKLM\Software\Microsoft\Active Setup\InstalledComponents\%APPNAME% and HKCU\Software\Microsoft\Active Setup\InstalledComponents\%APPNAME% are compared, and if the HKCU registry entries don't exist, or the version number of HKCU is less than HKLM, then the specified application is executed for the current user.

How do you create an Active Setup?

To implement Active Setup, you need to package all your user installation requirements into an EXE preferably, using SMS Installer, or Wise Installation System, and place the EXE on the client...