or any other text editor. The file itself has two primary sections:
, which is the
Application section and
, which is the File Extensions section.
22.214.171.124 Deploying .zap Files
Software Installation normally works only with Windows Installer package files. However, you can get
around this requirement by creating a .zap file that provides instructions for deploying the application. You
should only use .zap files to publish applications when it is not feasible to use repackaging software to
repackage an application and when a Windows Installer package file from a software vendor is unavailable.
A .zap file is a text file that can be parsed and executed by Software Installation. These files allow you to
publish non-Windows Installer applications with the following limitations:
The applications cannot be assigned to either users or computers. They can only be published.
The applications do not automatically repair themselves when key files have been deleted or become
corrupted. Instead, the application will invoke and rerun its setup program any time it is unable to start.
The applications are rarely able to install without user intervention. These applications run the
software’s original setup program, and few of these programs support an unattended installation.
The applications cannot install with elevated privileges. If you intend to deploy .zap files, users must
have permission to install software on their local computers. Native package files install using the
privileges assigned to the Windows Installer. This allows package files to be installed on computers
regardless of the user’s privileges. In other words, security is based on the GPO that deployed the
application rather than on the individual user’s security rights. A .zap file can be created with Notepad