Determining the Preparation Method
Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2
Before you start the software distribution process, determine which preparation method to use for each new application, patch, or upgrade that you plan to deploy. The following methods are available:
Use native Windows Installer packages. If the application you are installing includes a built-in .msi package you can either deploy the software as-is, or customize it further. For information about using transforms for customizing Windows Installer packages, see "Packaging Software for Deployment" later in this chapter.
Reauthor the setup program to include a native .msi. This method is not recommended except for expert Windows Installer package authors. However, when used, this method is most appropriate if the application is relatively simple, or you have thorough knowledge of its structure and of the application setup on the Windows platform that uses Windows Installer. For more information about reauthoring applications for Windows Installer, see "Packaging Software for Deployment" later in this chapter.
Create a Software Installation Settings (.zap) file. A .zap file is a text file similar to an .ini file, which contains instructions that allow Windows to publish an application (Setup.exe) for users to install by using Add or Remove Programs in Control Panel. To publish applications that do not install by using Windows Installer, you must create a .zap file, copy the .zap file to the software distribution point servers, and then use the Group Policy–based software deployment to publish the application for the users. You cannot use .zap files for assigned applications.
For information about using other installing programs, see article 231747 in the Microsoft Knowledge Base.
Repackaging applications into an .msi format has limitations and application manufacturers typically do not support it. Therefore, consider repackaging as a last resort, except for applications that are developed specifically for your organization. For information about repackaging applications for Windows Installer, see the Windows Security Collection in the Windows Server 2003 Technical Reference on the Web (https://go.microsoft.com/fwlink/?linkid=4571).
Table 8.3 describes the advantages and disadvantages of the various packaging methods.
Note
- Packages that are created on Windows 2000 by using Veritas WinInstall LE (the repackaging software that is included with Windows 2000) work on target computers running Windows XP. However, Veritas WinInstall LE does not run on Windows XP and is not intended for repackaging new .msi files.
Table 8.3 Comparing Packaging Methods
| Advantages and Disadvantages | Natively Author or Reauthor Windows Installer-Based Packages | Repackaging | .zap Files |
|---|---|---|---|
Advantages |
Can benefit from all Windows Installer features, including just-in-time feature installation, feature repair, and installation with elevated permissions. Can be run without user intervention. Can be assigned or published. Does not require user to be a local administrator to install. Can automatically repair itself if key files are damaged or missing. If application includes native .msi package, easy to deploy. Can roll back an unsuccessful installation, modification, repair, or removal. |
Same benefits as natively authoring. |
Easy to create and fast to deploy. Display application in AddorRemove Programs. |
Disadvantages |
Time-consuming to build and test. |
Can easily fail if repackaging not performed on a clean computer. Time-consuming to build and test. Control over installation less detailed than natively authoring. |
Run existing setup, requiring user intervention. Do not benefit from Windows Installer features. Might require user to have local administrator permissions to install. Cannot automatically install software or features on demand. Cannot automatically repair if key files are damaged or missing. Cannot roll back an unsuccessful operation. |
Important
Before you reauthor or repackage applications in your organization:
Check with the application manufacturer or internal development group to see if either has or is planning to develop a native Windows Installer implementation of the program.
Weigh the benefits of reauthoring and repackaging against the costs involved. Keep in mind that both are advanced operations. There are tools for each operation that can help software package developers create the final Windows Installer package, but the procedures are still quite resource-intensive and can be costly.