Summary
InstallShield's AdminLetter (now Macrovision's AdminLetter) had published a series of articles by Jeremy Moskowitz between October 2004 - July 2005. These articles provide a good understanding of Windows Installer Technology along with windows installer packages deployment via Active Directory, managing deployed packages and creating transforms and patches.

MSI 101: Why MSI?
[Author Excerpt]
There are a myriad of benefits the file format can provide. The most immediate benefit to rolling out new packages with the MSI format is the benefit of self-healing, which makes MSI files robust and dynamic. That is, if a critical file for an installed application is deleted or damaged, the application can simply repair itself. The application grabs the needed file from the original source. This benefit is immediately recognized should a user inadvertently or maliciously delete an application’s underlying files. To be sure, that application can just keep on running. To provide this functionality, the application used to create the MSI file needs to be able to “key” critical files.

Read more...

MSI 201: About MSIEXEC
[Author Excerpt]
Most installations will go very easily by simply double-clicking on the MSI file you have. However, you might require more control than just by double-clicking on the file. To that end, Windows has the powerful msiexec command.

Read more...

MSI 301: Preparing for deploying MSI packages with Active Directory
[Author Excerpt]
Specifically, using Active Directory and Group Policy, an administrator can deploy software to either users and/or computers as desired in multiple fashions. While there is a rudimentary deployment capability for .EXE files, Active Directory’s biggest deployment strength is bolstered with the magic of MSI files. In other words, without MSI files (from the manufacturer or those you create or repackage using an automated software packaging and testing tool like AdminStudio), true Active Directory software deployment isn’t really possible.

Read more...

MSI 401: Preparing to Deploy MSI Packages with Active Directory
[Author Excerpt]
Deploying applications using Active Directory and Group Policy is almost too good to be true. The downside of using Active Directory and Group Policy to deploy is minimal. However, one specific downside is the lack of centralized reporting capabilities. If, however, that feature isn’t very important to you, Group Policy based software installation is a powerful tool which is very easy to use.

Read more...

MSI 501: Managing Deployed MSI Applications
[Author Excerpt]
When it comes to managing your MSI applications, you’ve got a host of things you can choose to do:

• Automatic removal of previously installed applications
• Automatic removal when the application no longer applies
• Automatic upgrade of previously deployed applications

Read more...

MSI 601: Transforms and Patches
[Author Excerpt]
It is equally important to ensure that you’re only deploying as much of the package as you need. You also need to ensure that your applications are always up to date with the latest updates and patches. To that end, we’ll examine the ideas of “transforms” and “patches”.

Read more...

About the Author
Jeremy Moskowitz runs Moskowitz, Inc. (www.moskowitz-inc.com). Jeremy is an MCSE and a Microsoft MVP in Group Policy. Jeremy has authored the wildly successful Group Policy, Profiles and IntelliMirror (SYBEX). Jeremy runs www.GPanswers.com where system administrators can enjoy a vibrant community forum for Group Policy, free Group Policy related downloads, and information about 3rd party Group Policy related products. Jeremy has a two-day Group Policy Intensive Training and Workshop class which he teaches around the USA and the world. You can reach Jeremy via www.moskowitz-inc.com for comments or column ideas. [Source: The article series]