applicationPackaging created the topic: What is Installation Sequences in MSI Script?
Installation Sequences:
Installation sequences are represented by tabs below the Installation Sequence section in MSI Script. Windows Installer has 2 main types of sequences:
User Interface and Execute.
The User Interface sequence, which is executed at the beginning of installation, gathers system information, displays dialogs to the end user, and records end user choices. It is suppressed during silent installations.
The Execute sequence installs the application and makes changes to the system. During installation, Windows Installer first goes through each action in the Execute sequence and builds an internal installation script to follow. You cannot see or access this internal script.
This first pass is referred to as immediate mode and is represented by the Execute Immediate tab. After it creates the internal installation script, it runs the script it created, performing the actions that change the system.
The second pass is referred to as deferred mode, and encompasses all the actions between InstallInitialize and InstallFinalize. It is represented by the Execute Deferred tab. This makes it easier to specify in which mode to run an action. For information on where to place a custom action,
LaunchConditions
FindRelatedProducts
AppSearch
CCPSearch
RMCCPSearch
ValidateProductID
CostInitialize
FileCost
IsolateComponents
CostFinalize
MigrateFeatureStates
ExecuteAction
applicationPackaging replied the topic: Re: What is Installation Sequences in MSI Script?
Installation sequences are represented by tabs below the Installation Sequence section in MSI Script. Windows Installer has 2 main types of sequences:
1. User Interface and
2. Execute.
The User Interface sequence, which is executed at the beginning of installation, gathers system information, displays dialogs to the end user, and records end user choices. It is suppressed during silent installations.
The Execute sequence installs the application and makes changes to the system. During installation, Windows Installer first goes through each action in the Execute sequence and builds an internal installation script to follow. You cannot see or access this internal script.
This first pass is referred to as immediate mode and is represented by the Execute Immediate tab. After it creates the internal installation script, it runs the script it created, performing the actions that change the system.
The second pass is referred to as deferred mode, and encompasses all the actions between InstallInitialize and InstallFinalize. It is represented by the Execute Deferred tab.
This makes it easier to specify in which mode to run an action. For information on where to place a custom action, see Guidelines for Custom Action Location.
When Windows Installer generates the installation script, it generates a rollback script that will undo the actions of the installation script. The rollback script is executed if the installation is canceled or is unsuccessful, and is also run in deferred mode. Although you cannot view or edit the rollback script, you can specify that custom actions you add be added to it; use the In-Script Options field on the Properties tab of the custom action details dialog.
On Windows NT, 2000, XP, and Server 2003, Windows Installer runs as a service, which is registered in the Services control panel. When an .MSI is launched, it is run by the service. The Windows Installer service can run with elevated privileges based on policies, and the Windows Installer database runs with the current user’s privileges. When you add custom actions, you can specify whether they should be run with elevated privileges (system context) or with user privileges (user context). Set privileges to user context or system context in the In-Script Options field on the Properties tab of the custom action details dialog. On Windows 95 and Windows 98, Windows Installer runs as an executable. Because there are no levels of privileges on Windows 95 and Windows 98 (everyone has full privileges), setting privileges has no effect.
- Use of runtime variables to save into another variable using register in Ansible - September 6, 2018
- Ansible & Ansible Tower Variable Precedence Hierarchy - September 6, 2018
- How to use template in Ansible? - September 6, 2018