The Microsoft Windows Installer (MSI) is an installer service, on the agent side, that manages the installation of applications on Windows platforms. These applications must be encapsulated in a package, called MSI package. The MSI package consists of an MSI file (*.msi) and any external source files that are pointed to by this file. The package contains all of the information needed by the Microsoft Windows Installer to run the user interface and to install or uninstall the application.
The MSI file (*.msi) contains an installation database, a summary information stream, and data streams for various parts of the installation. The logic and data necessary for an installation are maintained in a relational database, also in the MSI file. In addition, the MSI file can also contain one or more transforms, internal source files, and external source files or cabinet files required by the installation.
A transform is a collection of changes applied to an installation. The Installer can add or replace data in the installation database by applying a transform to a base installation package. For instance, a transform can change the text in an application interface from one language to another. Transforms are specified by one or more transform files (.mst). The Installer can only apply transforms during an installation.
A cabinet file is a single file, usually with a .cab extension, that stores compressed files in a file library.
The Microsoft Windows Installer organizes installations based on the concept of components and features. Components are pieces of the application or product that is to be installed. These are usually hidden from the user. Features are presented to the users, and are typically determined by the application's functionality from the user's perspective.
MSI packages can be registered in the Software Package Library using the Register MSI Package wizard. Using this wizard, you can choose to register the MSI package, use an administrative installation, or perform and use an administrative installation. The wizard guides you through the registration process, where you can, for example, add procedures, and properties. You can also specify separate paths for the MSI package and the MSI file.
You may later receive an MSI patch package from one of your software vendors. For information on how to add these patch packages to administrative or local installations, see Registering and Installing a MSI Patch Package.
You can distribute registered MSI packages offline to target computers, using a data carrier like CD. The combined use of a registered procedure and a data carrier can be of value, if you want to create an administrative installation not only on the domain manager but also on its downstream scalability servers to reduce bandwidth requirements. For instructions on how to create an offline administrative install procedure for use with a CD, see Using an Offline Administrative Install Procedure with a CD.
Note: Because some products may update system files or make changes to the Windows registry, an installation may fail when an installation job is sent to a User Profile that has inadequate access rights.
|
Copyright © 2013 CA.
All rights reserved.
|
|