Explore topic-wise InterviewSolutions in Current Affairs.

1. Customize Applications to suit the user needs.
2. Simplify the Installation and Un-installation Procedures.
3. Saves Time in both Installation and Un-installation.
4. Once PACKAGED, applications can be quickly installed on a range of desktops in multiple locations, saving administrative costs, simplifying the manage of LICENSING fees and minimizing support and repair expenditures.
5. Saves SPACE of the product by doing apt modifications to applications.
6. Has a great flexibility of obtaining the lost files through a phenomenon called Self Heal, this reduces the down time of application. If a critical file (a .DLL or .EXE file, for example) that is part of the distribution is corrupt or is deleted, the user can be prompted to repair the installation by presenting the original .MSI distribution. Additionally, if the installation media is available (for example, on a network share), the repair simply happens automatically.
7. Can be advertised. So that on demand installation could take place.
8. Upgrading of the application can be done with ease.
9. Clean installation and Un-Installation is achieved by a process called Roll- Back.
10. Simplifies management of new user set-up along with the revision and distribution of software repairs and new applications to existing users. Application recovery can also be improved.
11. Helps eliminate uncontrolled software downloads and installation, enables applications to be safely removed and reduces non-business traffic on a corporate network.
12. Using .MSI format, can automate software distribution process and ensure that the installation doesn’t break other applications that have ALREADY been installed.
13. Application is installed via an OS service.
14. State management is maintained. In the past, it’s been difficult to know whether an application is installed on a machine. You would have to query for a .DLL with a specific version number or determine whether an .EXE file with a specific name was present. Windows Installer provides an application programming interface (API) that lets programmers and administrators SEE whether a specific application is installed on a machine.
15. Scriptable API. This whips together a VBScript to help us with the MSI file manipulations. The API to manipulate MSI files is so powerful that it can create, validate and update packages, trigger installs and uninstalls, examine the MSI repository data on computers, and perform some custom actions.
16. Served installs. Because MSI files can be housed in a share point and delivered via a server, we can keep our installation files all in one place or move them around — closer to the users if necessary.

A PACKAGE describes the installation of a full product (Windows Installer does not handle dependencies between products) and is universally identified by a GUID. A product is made up of components, grouped into features.

Components:

A component is the minimal part of a product—each component is treated by Windows Installer as a unit: the install developer cannot, for example, use a

condition to specify to install just part of a component. Components can contain files,groups of files, directories, COM components, registry keys, shortcuts, and other data. The end user does not directly INTERACT with components.

Components are identified globally by GUIDs, thus the same component can be shared among several features of the same package or multiple packages, ideally through the use of merge modules (although, for this to work correctly, different components should not share any sub-components).

Key paths:

A key path is a specific file, registry key, or ODBC data source that the package author specifies as critical for a given component. Because a file is the most common type of key path, the term key file is commonly used. A component can contain at most one key path; if a component has no EXPLICIT key path, the component's destination directory is taken to be the key path.

When an MSI-based application is launched, Windows Installer checks the existence of these critical files or registry keys (that is, the key paths). If there is a mismatch between the current system state and the value specified in the MSI package (e.g., a key file is missing), then the related feature is re-installed. This process is also known as self-healing or self-repair. No two components should use the same key path.

Features :

A feature is a hierarchical group of components—a feature can contain any number of components and other features (a feature contained in another feature is called a "subfeature"). Most installation programs display a "custom setup" dialog box at run time, from which the end user can SELECT which features to install or remove.

The package author defines the product features. A word-processing program, for example, might provide features for the main program executable, the program's help files, and optional spelling CHECKER and stationery modules.

A package describes the installation of a full product (Windows Installer does not handle dependencies between products) and is universally identified by a GUID. A product is made up of components, grouped into features.

Components:

A component is the minimal part of a product—each component is treated by Windows Installer as a unit: the install developer cannot, for example, use a

condition to specify to install just part of a component. Components can contain files,groups of files, directories, COM components, registry keys, shortcuts, and other data. The end user does not directly interact with components.

Components are identified globally by GUIDs, thus the same component can be shared among several features of the same package or multiple packages, ideally through the use of merge modules (although, for this to work correctly, different components should not share any sub-components).

Key paths:

A key path is a specific file, registry key, or ODBC data source that the package author specifies as critical for a given component. Because a file is the most common type of key path, the term key file is commonly used. A component can contain at most one key path; if a component has no explicit key path, the component's destination directory is taken to be the key path.

When an MSI-based application is launched, Windows Installer checks the existence of these critical files or registry keys (that is, the key paths). If there is a mismatch between the current system state and the value specified in the MSI package (e.g., a key file is missing), then the related feature is re-installed. This process is also known as self-healing or self-repair. No two components should use the same key path.

Features :

A feature is a hierarchical group of components—a feature can contain any number of components and other features (a feature contained in another feature is called a "subfeature"). Most installation programs display a "custom setup" dialog box at run time, from which the end user can select which features to install or remove.

The package author defines the product features. A word-processing program, for example, might provide features for the main program executable, the program's help files, and optional spelling checker and stationery modules.

Active Setup:

It is USED when your application requires installation of components such as FILES or registry keys on a per-user basis, but application has no advertised entry points or other triggers to initiate the installation process.

Run:

The Run key is processed after every logon, either by the Explorer shell, if it is present, or by First Boot Agent (FBA), if a custom shell, Command shell, or Task MANAGER Shell is used. If FBA processes this key, it does so after every logon, not during first boot as it normally would. Typically, this flag is used to load Systray APPLICATIONS, launch services in executables, hide autostart applications, or hide background processes

Run Once:

The RunOnce key is processed only once, by FBA, after Plug and Play device enumeration and DLL REGISTRATION processing have completed. The values of this

registry key are deleted from the registry after it is processed, so that it will not run again. Typically, this flag is used when a reboot is required, such as for a DLL or OCX registration, or for cleaning up a setup or an uninstall.

Active Setup:

It is used when your application requires installation of components such as files or registry keys on a per-user basis, but application has no advertised entry points or other triggers to initiate the installation process.

Run:

The Run key is processed after every logon, either by the Explorer shell, if it is present, or by First Boot Agent (FBA), if a custom shell, Command shell, or Task Manager Shell is used. If FBA processes this key, it does so after every logon, not during first boot as it normally would. Typically, this flag is used to load Systray applications, launch services in executables, hide autostart applications, or hide background processes

Run Once:

The RunOnce key is processed only once, by FBA, after Plug and Play device enumeration and DLL registration processing have completed. The values of this

registry key are deleted from the registry after it is processed, so that it will not run again. Typically, this flag is used when a reboot is required, such as for a DLL or OCX registration, or for cleaning up a setup or an uninstall.

Self Heal and Repair are two different concepts in Windows Installer which people many times consider to be the same thing however there is difference in these two. 

Self Heal is triggered by advertised shortcuts, or other advertising information in the package which eventually Repairs the application.

When the application is LAUNCHED by advertised SHORTCUT, it checks for all the key paths of the Current FEATURE, if any of the key paths is missing it will launch Repair.

Note that if there are multiple features then it will not check the missing key paths of the other features, but only the feature of which the advertised shortcut is launched.

Repair of an MSI can be triggered by:

• Repair button in Add/Remove PROGRAMS

• Giving the command line msiexec /f{other option} {MSI name}

• Self Heal by advertised shortcut or other advertising information

• Active setup

Once the repair of the package is triggered, EVEN with Self Heal, then the whole of the MSI is reinstalled. Then it does not see that only the feature which triggered the self heal should be repaired, but the whole MSI, by which I mean, all its features are reinstalled.

Self Heal and Repair are two different concepts in Windows Installer which people many times consider to be the same thing however there is difference in these two. 

Self Heal is triggered by advertised shortcuts, or other advertising information in the package which eventually Repairs the application.

When the application is launched by advertised shortcut, it checks for all the key paths of the Current Feature, if any of the key paths is missing it will launch Repair.

Note that if there are multiple features then it will not check the missing key paths of the other features, but only the feature of which the advertised shortcut is launched.

Repair of an MSI can be triggered by:

• Repair button in Add/Remove programs

• Giving the command line msiexec /f{other option} {MSI name}

• Self Heal by advertised shortcut or other advertising information

• Active setup

Once the repair of the package is triggered, even with Self Heal, then the whole of the MSI is reinstalled. Then it does not see that only the feature which triggered the self heal should be repaired, but the whole MSI, by which I mean, all its features are reinstalled.

The INSTALLLEVEL property is the initial level at which features are selected “ON” for INSTALLATION by default. A FEATURE is INSTALLED only if the VALUE in the Level field of the Feature table is LESS than or equal to the current INSTALLLEVEL value. The installation level for any installation is specified by the INSTALLLEVEL property, and can be an integral from 1 to 32,767.

The INSTALLLEVEL property is the initial level at which features are selected “ON” for installation by default. A feature is installed only if the value in the Level field of the Feature table is less than or equal to the current INSTALLLEVEL value. The installation level for any installation is specified by the INSTALLLEVEL property, and can be an integral from 1 to 32,767.

PROPERTY: PRIVATE Properties in MSI (Properties that cannot be CHANGED during RUNTIME).

PROPERTY: Public Properties (Properties that can be changed during runtime).

Property: Private Properties in MSI (Properties that cannot be changed during runtime).

PROPERTY: Public Properties (Properties that can be changed during runtime).

ADDLOCAL: It will install the components (file resources) associated with the FEATURE locally on the CLIENT the package is installed on.

ADDSOURCE: The files will be “installed” on the source MEANING where the MSI is ORIGINALLY located. There will actually not be any installation of files into the folder but they must exists as “external UNCOMPRESSED”.

ADDLOCAL: It will install the components (file resources) associated with the feature locally on the client the package is installed on.

ADDSOURCE: The files will be “installed” on the source meaning where the MSI is originally located. There will actually not be any installation of files into the folder but they must exists as “external uncompressed”.

It is the folder in which MICROSOFT Windows stores PROTECTED SYSTEM files.

It is the folder in which Microsoft Windows stores protected system files.

One or more operations processed together as a single indivisible WHOLE CALLED a transaction. All the constituent operations must succeed for the transaction to succeed, otherwise all the operations are rolled back to the original state.

Windows Installer 4.5 includes SUPPORT for installing multiple packages using transaction processing. The packages are CHAINED together and processed as a single transaction. If one or more of the packages in the transaction cannot be installed successfully or if the end USER cancels the installation, the Windows Installer initiates rollback for all of the packages to restore the system to its earlier state.

One or more operations processed together as a single indivisible whole called a transaction. All the constituent operations must succeed for the transaction to succeed, otherwise all the operations are rolled back to the original state.

Windows Installer 4.5 includes support for installing multiple packages using transaction processing. The packages are chained together and processed as a single transaction. If one or more of the packages in the transaction cannot be installed successfully or if the end user cancels the installation, the Windows Installer initiates rollback for all of the packages to restore the system to its earlier state.

Any MSI which INSTALLS files based on selection, be it from COMMAND line, System Search or SELECTED OPTIONS while installing.

Any MSI which installs files based on selection, be it from command line, System Search or selected options while installing.

The Windows Installer can perform an administrative installation of an application or product to a network for USE by a workgroup. An administrative installation installs a source image of the application onto the network that is similar to a source image on a CD-ROM. Users in a workgroup who have access to this administrative image can then install the product from this source. A user must FIRST install the product from the network to run the application. The user can choose to run-from-source when he installs and the installer uses most of the product's file directly from the network. Administrators can run an administrative installation from the command line by USING the /a command line option. The ADMIN action is the top-level action USED to INITIATE an administrative installation. When this action is executed the installer calls the actions in the AdminExecuteSequence and AdminUISequence tables to perform the administrative installation.

Syntax: Msiexec /a package

The Windows Installer can perform an administrative installation of an application or product to a network for use by a workgroup. An administrative installation installs a source image of the application onto the network that is similar to a source image on a CD-ROM. Users in a workgroup who have access to this administrative image can then install the product from this source. A user must first install the product from the network to run the application. The user can choose to run-from-source when he installs and the installer uses most of the product's file directly from the network. Administrators can run an administrative installation from the command line by using the /a command line option. The ADMIN action is the top-level action used to initiate an administrative installation. When this action is executed the installer calls the actions in the AdminExecuteSequence and AdminUISequence tables to perform the administrative installation.

Syntax: Msiexec /a package

It MEANS that, the Availability of an application to users or others with out actually the FULL Installation. There are TWO TYPES of Advertising.

Assigning: An Application appears (shortcuts, files & registries) to a user or others, when an Application is “ASSIGNED”. When the user tries to open, it is installed upon demand.

Publishing: No Entry points appear to a user or others, when an Application “published” to the group. It is activated only if the group Application activates the published Application i.e. Installation on Demand.

Syntax

Ø msiexec /j [{u|m}] package
Ø msiexec {u|m} package /t TransformList
Ø msiexec {u|m} package /g LanguageID

Parameters

Ø /j : Advertises a product.
Ø u : Advertises to the current user.
Ø m : Advertises to all users of the computer.
Ø package : Specifies the Windows Installer package file.
Ø /g LanguageID : Identifies the language.
Ø /t TransformList : Applies transform to advertised package.

It means that, the Availability of an application to users or others with out actually the full Installation. There are two types of Advertising.

Assigning: An Application appears (shortcuts, files & registries) to a user or others, when an Application is “assigned”. When the user tries to open, it is installed upon demand.

Publishing: No Entry points appear to a user or others, when an Application “published” to the group. It is activated only if the group Application activates the published Application i.e. Installation on Demand.

Syntax

Ø msiexec /j [{u|m}] package
Ø msiexec {u|m} package /t TransformList
Ø msiexec {u|m} package /g LanguageID

Parameters

Ø /j : Advertises a product.
Ø u : Advertises to the current user.
Ø m : Advertises to all users of the computer.
Ø package : Specifies the Windows Installer package file.
Ø /g LanguageID : Identifies the language.
Ø /t TransformList : Applies transform to advertised package.

Resiliency: Resiliency can be inconsistent with repackaged applications because the repackager UTILITY may not fully understand the component dependencies or what the key paths of the application should be. Therefore, an application may be packaged into one LARGE feature that gets entirely reinstalled if a component keypath is missing. If it were broken up into multiple smaller features it would enable a more manageable resiliency. COM/ActiveX

Registration: Component Object Model (COM) and ActiveX controls may not be PROPERLY registered. Prior to Windows Installer, COM and ActiveX registration was a black box. Except for the exported functions DLLRegisterServer and DLLUnregister server, COM and ActiveX controls offered very few hints of their registration process. RegSvr32.exe was responsible for calling the previously mentioned functions and then the DLL was responsible for registering itself. There is no utility that can view a DLL, an OCX, or an EXE and figure out what goes on inside DllRegisterServer and DllUnregisterServer for that file. There are standard registry entries that most COM and ActiveX controls register, such as HKCRCLSID, HKCRProgID, and HKCRTypeLib. Information on COM registration may or may not get entered into the APPROPRIATE MSI tables by the repackager.

Shortcuts: Shortcuts may not be created as Windows Installer descriptor shortcuts, which enable resiliency. Legacy setup shortcuts were .lnk files that pointed to an executable in most cases. Sometimes when the repackager runs, all it knows is that an .lnk file was copied to a directory. For example, a legacy Setup.exe INSTALLED a shortcut to C:WindowsProfilesUser1Desktop. The repackager would copy the .lnk file directly to the directory listed previously. Therefore, the repackager is not actually copying a Windows Installer shortcut, but rather it is copying a file without any resiliency capabilities included.

Isolated Components: The only way to take advantage of isolated components is to author a new MSI package. Repackagers currently do not support this feature. Application Removal:When uninstalling a repackaged application, it is possible that the AllUsers profile.

Resiliency: Resiliency can be inconsistent with repackaged applications because the repackager utility may not fully understand the component dependencies or what the key paths of the application should be. Therefore, an application may be packaged into one large feature that gets entirely reinstalled if a component keypath is missing. If it were broken up into multiple smaller features it would enable a more manageable resiliency. COM/ActiveX

Registration: Component Object Model (COM) and ActiveX controls may not be properly registered. Prior to Windows Installer, COM and ActiveX registration was a black box. Except for the exported functions DLLRegisterServer and DLLUnregister server, COM and ActiveX controls offered very few hints of their registration process. RegSvr32.exe was responsible for calling the previously mentioned functions and then the DLL was responsible for registering itself. There is no utility that can view a DLL, an OCX, or an EXE and figure out what goes on inside DllRegisterServer and DllUnregisterServer for that file. There are standard registry entries that most COM and ActiveX controls register, such as HKCRCLSID, HKCRProgID, and HKCRTypeLib. Information on COM registration may or may not get entered into the appropriate MSI tables by the repackager.

Shortcuts: Shortcuts may not be created as Windows Installer descriptor shortcuts, which enable resiliency. Legacy setup shortcuts were .lnk files that pointed to an executable in most cases. Sometimes when the repackager runs, all it knows is that an .lnk file was copied to a directory. For example, a legacy Setup.exe installed a shortcut to C:WindowsProfilesUser1Desktop. The repackager would copy the .lnk file directly to the directory listed previously. Therefore, the repackager is not actually copying a Windows Installer shortcut, but rather it is copying a file without any resiliency capabilities included.

Isolated Components: The only way to take advantage of isolated components is to author a new MSI package. Repackagers currently do not support this feature. Application Removal:When uninstalling a repackaged application, it is possible that the AllUsers profile.

The Product CODE is a GUID IDENTIFYING a PARTICULAR Application or product.

The Product Code is a GUID identifying a particular Application or product.

The Package Code is a GUID IDENTIFYING a PARTICULAR Microsoft Windows Installer package. It ASSOCIATES an .MSI FILE.

The Package Code is a GUID identifying a particular Microsoft Windows Installer package. It associates an .MSI file.

Microsoft utility to VIEW, update, VALIDATE MSI & MST FILES.

Microsoft utility to view, update, validate MSI & MST files.

• PICTURE TAKER
• Windows Install MASTER
• InstallRite
• RegMon
• FileMon
• procmon
• Process Explorer
• CsDiff
• ICON Extractor & Icon Builder
• RegExtractor
• WiLogUtl
• WiseComReg

Deploying APPLICATIONS through the ACTIVE DIRECTORY is done through the use of group policies, and therefore applications are DEPLOYED either on a PER user basis or on a per computer basis.

Deploying applications through the Active Directory is done through the use of group policies, and therefore applications are deployed either on a per user basis or on a per computer basis.

Intelli Mirror management technologies are a set of POWERFUL features for change and configuration management. It ensures that USERS’ data, SOFTWARE, and personal settings are available when they MOVE from one computer to another, and persist when their computers are CONNECTED to the network.

Intelli Mirror management technologies are a set of powerful features for change and configuration management. It ensures that users’ data, software, and personal settings are available when they move from one computer to another, and persist when their computers are connected to the network.

Software restriction policies provide administrators with a POLICY-driven mechanism to identify software running on computers in a domain, and CONTROL its ability to EXECUTE. This policy can be used to block malicious scripts, help lockdown a COMPUTER, or prevent unwanted APPLICATIONS from running.

Software restriction policies provide administrators with a Policy-driven mechanism to identify software running on computers in a domain, and control its ability to execute. This policy can be used to block malicious scripts, help lockdown a computer, or prevent unwanted applications from running.

When an EXECUTABLE is wrapped within an MSI then that msi is CALLED WRAPPER msi.

When an Executable is wrapped within an MSI then that msi is called wrapper msi.

If the user having the privileges of MSI FEATURES (Windows Installer) is called as ELEVATED User You can create through “gpedit.msc” in the run COMMAND or registry keys HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftWindowsInstaller

TYPE: DWORD Key: Always Install Elevated Value: 1

If the user having the privileges of MSI features (Windows Installer) is called as Elevated User You can create through “gpedit.msc” in the run Command or registry keys HKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftWindowsInstaller

Type: DWORD Key: Always Install Elevated Value: 1

ADMINISTRATORS use Group Policy to DEFINE options for managing, configuration of servers, desktops, and groups of users. It is used to set policies across a GIVEN SITE, domain, or range of organizational units. Use “gpedit.msc” in the run command to set the policy.

Administrators use Group Policy to define options for managing, configuration of servers, desktops, and groups of users. It is used to set policies across a given site, domain, or range of organizational units. Use “gpedit.msc” in the run command to set the policy.

One of the more critical aspects to MANAGING a WINDOWS environment is the ability to deploy NEW applications, updates, upgrades & patches. Distributing new or updated SOFTWARE is called as Software Distribution.

One of the more critical aspects to managing a Windows environment is the ability to deploy new applications, updates, upgrades & patches. Distributing new or updated software is called as Software Distribution.

• Group policy (Active DIRECTORY)
• Software Update SERVICES (SUS)
• WINDOWS Update Web site
• Systems MANAGEMENT service (SMS)

When two or more APPLICATIONS install the same system files (DLLs, .VBXs, and .OCXs), Windows registry, and other ITEMS. To detect, Conflict MANAGEMENT should be use and for resolve the SOFTWARE conflicts, Application Isolation CONCEPT should be use.

When two or more applications install the same system files (DLLs, .VBXs, and .OCXs), Windows registry, and other items. To detect, Conflict Management should be use and for resolve the software conflicts, Application Isolation concept should be use.

Will CHANGE with TIME.

Will change with time.

The LATEST VERSION of WINDOWS INSTALLER is 4.5

The latest version of Windows Installer is 4.5

It is USED for the REGISTRATION of .NET ASSEMBLY FILES

It is used for the registration of .Net Assembly files

It MEANS that to prevent overwriting of previous VERSIONS of SHARED components, and ensures that other applications do not overwrite your VERSION of shared components.

a) MANIFEST file concept
b) Local file concept

It means that to prevent overwriting of previous versions of shared components, and ensures that other applications do not overwrite your version of shared components.

a) Manifest file concept
b) Local file concept

App Search ACTION is used to search for EXISTING versions of PRODUCTS (Files, Registry, INI, Directory & Component)

App Search action is used to search for existing versions of products (Files, Registry, INI, Directory & Component)

Launch CONDITION is USED to check system requirements on the destination COMPUTER.

Launch Condition is used to check system requirements on the destination computer.

1. Always Execute: This action execute in all sequences
2. Run first time: This action execute only the first time WINDOWS Installer encounters it.
3. Run once per PROCESS:This action execute only ONE time either Execute sequence that should not run if the INSTALLATION is running in silent mode.
4. Run only if UI sequence was run: This action execute only if either Execute sequence is run following User Interface sequence.

A) Synchronous: Windows Installer runs the custom action SYNCHRONOUSLY to the main installation. It WAITS for the custom action to complete successfully before continuing the main installation.

b) Synchronous, ignore EXIT code: Windows Installer runs the custom action synchronously to the main installation. It waits for the custom action to complete before continuing the main installation; the action can be either success or fail.

c) A synch, wait at END of sequence: Windows Installer runs the custom action simultaneously with the main installation. At the end it waits for the exit code from the custom action before continuing.

d) A synch, no wait: Windows Installer runs the custom action simultaneously with the main installation. It doesn’t wait for completion of the custom action and doesn’t check the exit code ALSO.

A) Synchronous: Windows Installer runs the custom action synchronously to the main installation. It waits for the custom action to complete successfully before continuing the main installation.

b) Synchronous, ignore exit code: Windows Installer runs the custom action synchronously to the main installation. It waits for the custom action to complete before continuing the main installation; the action can be either success or fail.

c) A synch, wait at end of sequence: Windows Installer runs the custom action simultaneously with the main installation. At the end it waits for the exit code from the custom action before continuing.

d) A synch, no wait: Windows Installer runs the custom action simultaneously with the main installation. It doesn’t wait for completion of the custom action and doesn’t check the exit code also.

• If the Custom ACTION which INSTALLS or MODIFY a file under the INSTALLDIR or Installation should be run in “DEFERRED in User CONTEXT”.
• If the Custom action which installs or modify the system file directly should be run in “Deferred Execution in System Context”.

• Immediate CUSTOM actions, can be SEQUENCED anywhere within any of the sequence tables
• Deferred custom actions can only be sequenced between the INSTALL Initialize and Install Finalize actions in execute sequence tables
• Immediate custom actions have access to the INSTALLATION database
• Deferred custom actions doesn’t have access to the Installation database
• Immediate custom actions can only run in the User Context
• Deferred custom actions can run both in the context of the user and elevated using the system context.

a) Immediate Execution

Immediate custom actions, can be sequenced anywhere within any of the sequence tables. It has access to the installation database (read & set installation properties, modify feature & component states, add temporary columns, rows, and tables).

B) Deferred Execution – User Context

Deferred custom actions can only be sequenced between the Install Initialize and Install Finalize actions in execute sequence tables. It doesn’t have access to the installation database. Deferred custom actions are not executed immediately. Instead they are scheduled to run LATER during the execution script. The execution script isn't PROCESSED until the Install Execute, Install Execute Again, or Install Finalize action is run. If the Current User doesn’t have the elevated privileges (Custom actions make changes in the system DIRECTLY), the custom actions should run in Deferred Execution in User Context only.

c) Rollback only

This Action should be executed during the Installation of the Rollback script or if the Installation is Unsuccessful.

d) COMMIT only

This Action should be executed during the Installation of the Commit script.

e) Deferred Execution – System Context

Deferred custom actions can only be sequenced between the Install Initialize and Install Finalize actions in execute sequence tables. It doesn’t have access to the installation database. Deferred custom actions are not executed immediately. Instead they are scheduled to run later during the execution script. The execution script isn't processed until the Install Execute, Install Execute Again, or Install Finalize action is run. If the Current User have the elevated privileges (Custom actions make changes in the system directly), then it should run in Deferred Execution in System Context only.

a) Immediate Execution

Immediate custom actions, can be sequenced anywhere within any of the sequence tables. It has access to the installation database (read & set installation properties, modify feature & component states, add temporary columns, rows, and tables).

b) Deferred Execution – User Context

Deferred custom actions can only be sequenced between the Install Initialize and Install Finalize actions in execute sequence tables. It doesn’t have access to the installation database. Deferred custom actions are not executed immediately. Instead they are scheduled to run later during the execution script. The execution script isn't processed until the Install Execute, Install Execute Again, or Install Finalize action is run. If the Current User doesn’t have the elevated privileges (Custom actions make changes in the system directly), the custom actions should run in Deferred Execution in User Context only.

c) Rollback only

This Action should be executed during the Installation of the Rollback script or if the Installation is Unsuccessful.

d) Commit only

This Action should be executed during the Installation of the Commit script.

e) Deferred Execution – System Context

Deferred custom actions can only be sequenced between the Install Initialize and Install Finalize actions in execute sequence tables. It doesn’t have access to the installation database. Deferred custom actions are not executed immediately. Instead they are scheduled to run later during the execution script. The execution script isn't processed until the Install Execute, Install Execute Again, or Install Finalize action is run. If the Current User have the elevated privileges (Custom actions make changes in the system directly), then it should run in Deferred Execution in System Context only.

1. NORMAL USER Interface
2. Normal Execute IMMEDIATE / Deferred
3. Administrative User Interface
4. Administrative Execute Immediate / Deferred

•  DLL file stored in a BINARY table stream
•  DLL file that is installed with a product
•  EXE file stored in a Binary table stream
•  EXE file that is installed with a product
•  DISPLAYS a specified error message and RETURNS failure, terminating the installation
•  EXE file having a path specified by a property value
•  EXE file having a path REFERENCING a directory
•  JScript file stored in a Binary table stream
•  JScript file that is installed with a product
•  JScript text specified by a property value
•  JScript text stored in this sequence table
•  VBScript file stored in a Binary table stream
•  VBScript file that is installed with a product
•  VBScript text specified by a property value
•  VBScript text stored in this sequence table
•  Property set with formatted text
•  Directory set with formatted text
•  Installation of a package nested inside of the first package. See Nested Installation ACTIONS
•  Installation of a package that resides in the first application’s source tree. See Nested Installation
•  Actions
•  Installation of an application that is advertised or already installed. See Nested Installation Actions.

The Microsoft Windows INSTALLER PROVIDES many built-in actions for performing the installation process. For some cases the developer writes an ACTION to execute his own installation is called CUSTOM action.

The Microsoft Windows Installer provides many built-in actions for performing the installation process. For some cases the developer writes an action to execute his own installation is called custom action.

There is no RESTRICTION on the NUMBERS of transforms which can be supplied in the COMMAND LINE.

There is no restriction on the numbers of transforms which can be supplied in the command line.

There is no RESTRICTION on the numbers of TRANSFORMS which can be created for one Vendor MSI.

There is no restriction on the numbers of transforms which can be created for one Vendor MSI.

a) Embedded transform

Embedded transforms are stored inside the .msi file of the package.

b) Secured transform

Secured transforms are stored LOCALLY on the user's COMPUTER in a LOCATION where, on a secure file system, the user does not have write access. Such transforms are cached in this location during the installation or advertisement of the package. During subsequent installation-on-demand or maintenance installations of the package, the installer uses the cached transforms.

c) Unsecured transform

Transforms that have not been secured are CALLED unsecured transforms. To apply an unsecured transform, pass the transform file names in the TRANSFORMS property or command line STRING during the installation.

a) Embedded transform

Embedded transforms are stored inside the .msi file of the package.

b) Secured transform

Secured transforms are stored locally on the user's computer in a location where, on a secure file system, the user does not have write access. Such transforms are cached in this location during the installation or advertisement of the package. During subsequent installation-on-demand or maintenance installations of the package, the installer uses the cached transforms.

c) Unsecured transform

Transforms that have not been secured are called unsecured transforms. To apply an unsecured transform, pass the transform file names in the TRANSFORMS property or command line string during the installation.

A transform is a WINDOWS installer file with the EXTENSION (.MST). It should be used along with a MSI to CUSTOMIZE or change the installation package without modifying the MSI. The installer can only APPLY TRANSFORMS during an installation.

A transform is a windows installer file with the extension (.MST). It should be used along with a MSI to customize or change the installation package without modifying the MSI. The installer can only apply transforms during an installation.

When a USER or application activates an ADVERTISED FEATURE or product, the installer PROCEEDS with installation of the needed components.

When a user or application activates an advertised feature or product, the installer proceeds with installation of the needed components.

If a Feature or Component is advertised, only the INTERFACES REQUIRED for loading and launching the APPLICATION are installed to the user or others. If a user ACTIVATES an advertised interface the installer then proceeds to install the NECESSARY Components & Features.

If a Feature or Component is advertised, only the interfaces required for loading and launching the application are installed to the user or others. If a user activates an advertised interface the installer then proceeds to install the necessary Components & Features.

It means that, the Availability of an application to USERS or others with out actually the full Installation. There are two types of Advertising

Assigning : 

An Application appears (SHORTCUTS, files & registries) to a user or others, when an Application is “assigned”. When the user TRIES to open, it is installed upon demand.

Publishing : 

No Entry POINTS appear to a user or others, when an Application “published” to the group. It is activated only if the group Application activates the published Application i.e. Installation on Demand.

It means that, the Availability of an application to users or others with out actually the full Installation. There are two types of Advertising

Assigning : 

An Application appears (shortcuts, files & registries) to a user or others, when an Application is “assigned”. When the user tries to open, it is installed upon demand.

Publishing : 

No Entry points appear to a user or others, when an Application “published” to the group. It is activated only if the group Application activates the published Application i.e. Installation on Demand.

msiexec /i <MSI> ARPSYSTEMCOMPONENT=1

FOLLOWING entries are various ARP properties:

a) ARPAUTHORIZEDCDFPREFIX
b) ARPCOMMENTS
c) ARPCONTACT
d) ARPINSTALLLOCATION
e) ARPNOMODIFY
f) ARPNOREMOVE
g) ARPNOREPAIR
h) ARPPRODUCTICON
i) ARPREADME
j) ARPSIZE
k) ARPSYSTEMCOMPONENT
l) ARPURLINFOABOUT
m) ARPURLUPDATEINFO

msiexec /i <msi> ARPSYSTEMCOMPONENT=1

Following entries are various ARP properties:

a) ARPAUTHORIZEDCDFPREFIX
b) ARPCOMMENTS
c) ARPCONTACT
d) ARPINSTALLLOCATION
e) ARPNOMODIFY
f) ARPNOREMOVE
g) ARPNOREPAIR
h) ARPPRODUCTICON
i) ARPREADME
j) ARPSIZE
k) ARPSYSTEMCOMPONENT
l) ARPURLINFOABOUT
m) ARPURLUPDATEINFO

msiexec /i &LT;MSI&GT; ADDLOCAL=<Feature Name>

msiexec /i <msi> ADDLOCAL=<Feature Name>

We can give permission for files & folders through VB Script by using the CACLS & XCACLS commands:

1. CACLs should only run on NTFS partitions.
2. CACLS – Changes Access Control ListS
3. “Cacls <file name> [/T] [/E] [/C] [/G user: PERM] [/R user [...]] [/P user: perm [...]]
4. [/D user [...]] “
5. /T Changes ACLs of specified files in the CURRENT directory and subdirectories
6. /E EDIT ACL instead of replacing it
7. /C Continue (ignore) access denied errors
8. /G user: perm where access rights granted can be: R C F (read, change, full control)
9. /R user Revoke specified user's access rights (only valid with /E)
10. /P user: perm Replace specified user's access rights. Permission can be: N R C F (NONE, read, change, full control)
11. /D user DENY specified user access

E.g. “cacls c:myfile.txt /E /G <user name>: F”

We can give permission for files & folders through VB Script by using the CACLS & XCACLS commands:

E.g. “cacls c:myfile.txt /E /G <user name>: F”