applicationPackaging created the topic: What is MSI Script?
MSI Script™ contains the sequences of actions that make up an installation. The action sequences are pre-defined following the Windows Installer guidelines for creating sequences. The actions are in the recommended order, and, where appropriate, conditions are set. It is recommended that we should not delete or move any standard actions.

The existing action sequences are sufficient for most installations. If you need specialized functionality not offered by Windows Installer, you can add custom actions to an installation. With custom actions, you can call .EXEs, .DLLs, WiseScripts, JScripts, and VBScripts. You can set installation properties and directories and call nested .MSI files. You can also perform many other functions such as launching a Web page or downloading a file from a Web site

Tagged : MSI

applicationPackaging created the topic: What is Advertisement Installation in MSI Script
They contain standard Windows Installer actions, dialog actions, and custom actions. All installation modes are included in every Windows Installer installation you create, but each mode is run only under certain circumstances. Installation modes are not used with merge modules.
Normal Installation:

User Interface
Execute Immediate
Execute Defferred

Call Custom DLL From Destination
Call Custom DLL From Installation
Call Custom DLL From Installed Files
Call DLL From Installation
Call DLL From Installed Files
Call JScript From Embedded Code
Call JScript From Installation
Call JScript From From Installed Files
Call JScript From Property
Call VBScript From Embedded Code
Call VBScript From Installation
Call VBScript From Installed Files
Call VBScript From Property
Display Message
Download File From Internet
End Statement
Call VBScript From Destination
Call VBScript From Installation
Call VBScript From Installed Files
Call VBScript From Path
If Statement
Install MSI From Destination
Install MSI From Installation
Install MSI From Relative Path
Launch Web Page
Open Document From Installed Files
Pause Installation
Post Data To HTTP Server
Remark
Run WiseScript From Destination
Run WiseScript From Installation
Run WiseScript From Installed Files
Set Directory
Set Feature State
Set Property
Terminate Installation

Tagged : MSI

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.

Tagged : MSI

applicationPackaging created the topic: Implements Nested MSI Based on Featutre Selection
Any body talk about Implements Nested MSI Based on Featutre Selection?

Tagged : MSI

applicationPackaging created the topic: Implements Nested MSI Based on Featutre Selection
Purpose
Use Patch Creation to create a Windows Installer patch file (.MSP) that updates installed versions of a Windows Installer-based application. A patch file can update one or several previous versions. Unlike full installations, a patch installation contains only the information necessary to update an installed version of the application.
________________________________________
Note
If this tool is disabled, it means you do not have a license to use it. With Enterprise Management Server, it might also mean you do not have permission to use it.
________________________________________
Before You Begin Read about what you need to create a patch in the online help.
How to Use
1. Double-click the Patch Creation icon.
The Welcome dialog appears, listing the basic steps for creating a patch file. The wizard guides you through each step.
2. Click Next.
The Specify Patch Settings File dialog appears.
3. Mark one of the following:
? Create a new patch file
This creates a new patch settings file (.PCP).
? Open an existing patch settings file (.PCP file)
If you mark this, also specify the .PCP file.
4. Click Next.
The Specify Previous Versions dialog appears, where you select .MSI files of previous versions that this patch will update, referred to as targets. When this patch is run on a destination computer, it verifies that a valid target exists before installation. You must add at least one previous version to this list.
5. To add a previous version, click Add, complete the Previous Version Details dialog, and click OK.
6. If you are prompted to run an administrative installation, click Yes.
The administrative installation is performed. After it finishes, the Specify Previous Versions dialog appears again.
7. Repeat the steps above to add additional previous versions.
8. When you finish, click Next on the Specify Previous Versions dialog.
The Specify Upgrade Version dialog appears.
9. Complete the dialog:
? Upgrade MSI path
The earlier versions of the application will be upgraded to the version you specify here. By default, the path to the current installation’s .MSI appears.
? Advanced
Click this to enter advanced settings. The Advanced Upgrade Version Details dialog appears. Complete the dialog and click OK.
? Add a Digital Signature to the Patch
(Windows Installer 3.0 or later.) Mark this to digitally sign the patch.
10. Click Next on the Specify Upgrade Version dialog.
11. If you are prompted to run an administrative installation again, click Yes. If you are prompted to update the package code, click Yes.
If you marked the option to add a digital signature, the Specify Digital Signature Settings dialog appears. A warning message appears if the original installation was not signed.
12. To add a digital signature to the patch, complete the Specify Digital Signature Settings dialog and click Next.
13. If you are prompted to run an administrative installation again, click Yes. If you are prompted to update the package code, click Yes.
If Windows Installer 3.0 or later is installed on your computer, the Patch Sequencing dialog appears. Complete the dialog and click OK. Otherwise, the Compile Patch dialog appears.
14. Complete the Compile Patch dialog:
? Output .MSP file
Specify a full path for the patch file that you distribute to end users.
? Advanced Settings
Click Advanced to display the Advanced Patch Settings dialog. Complete the dialog and click OK.
? Patch Removal
To make this patch removable through Add/Remove Programs, click Allow Removal and complete the Patch Removal Settings dialog.
? Multi-patch Media Settings
During patch creation, entries are made in the Media table of the patch installation. Options in this section populate the Media table. For each subsequent patch, the file sequence start number and the disk ID start number must be higher than the one in the previous .MSI or patch file. To enter these numbers accurately, you must have access to the most recent patch file distributed to end users. Click Browse to specify the patch file; the file sequence and disk ID numbers are read from the patch.
15. Click Next to begin the patch creation process.
During patch creation, you might see a message stating that the versions between the target image (previous version) and upgrade image (new version) do not match. This is normal; click Yes if this message appears.
The Compile Patch dialog notifies you when patch creation is completed.
16. Click View Log to view a log file of all actions performed to create the patch.
If the patch file could not be created, use this log file to determine the source of the error.

Tagged : MSI

installanywhereExpert created the topic: Features of Scriptlogic Desktop Authority MSI Studio
Popular Features

Discover all the features that make MSI Studio the most complete software packaging and application installer.

*
Repackage On Any Machine

Connect to a target computer to monitor the files and settings changed by a legacy application installer and capture them in an MSI.
*
Comprehensive MSI Editor

Intuitive graphical interface to change installation preferences. Components and Features are displayed in a tree view allowing easy drag-and-drop of resource items between them.
*
Wizards

Walk through many of the most common MSI management tasks with a easy to use Wizard.
*
Compare MSI Packages

View the difference between 2 MSI files by viewing the changes in the table view with color coded rows, or export the differences to a text file.
*
Legacy Application Support

Monitor changes from a legacy application installer and create a well structured MSI.
*
Completely Customizable Projects

The Custom Action wizard allows you to create any type of custom action and add them to your sequence. Easily set the processing type, execution and scheduling.
*
Access to Deleted Project Components

A recycle bin allows you to reintroduce any deleted rows.
*
Complete COM Entry Management

Convert registry table entries to COM table entries and back to registry tables. Extract COM entries from the files in your project and add to the registry table.
*
Modular Design Architecture

Create merge modules from files in your project. Once stored as modules, you can search for merge modules to add to new projects.
*
Access to CAB Contents

Easily extract cab files and their contents from within MSI files.
*
Multiple Validation Options

Projects can be validated (ICE or MCE) and errors are displayed in the output window.
*
Self-Extracting Options

Create a self-extracting bootstrapped executable for your MSI. Check and install the windows installer runtimes from the bootstrapper.

Tagged : MSI

installanywhereExpert created the topic: script to update file sequence in a MSI
If we have to add 1000 new files to a MSI all the new files will have the file sequence to ‘0’ . Is there a way to update the sequence of the files? Sould we use a script or something to update the file sequnce of the files? If yes, could someone please point me to the script for this purpose?

applicationPackaging replied the topic: Re: script to update file sequence in a MSI
How are you adding the 1000 files?

If you add the files using the Wise GUI, then the file sequence count will be set automatically.
So are you adding the files using the automation interface?
If so, you are already coding for it, so incrementing the file sequence count in the file table will be a trivial addition to your code. You will of course also need to update the media table to identify which CAB the file sequences are contained in.

Tagged : MSI

created the topic: Excellent opening for MSI Packaging CMM 5 MNC IT Company!!!!
FROM: hr@headsnminds.com

We have excellent opening for MSI Appliation Packaging!!!!!

Location: Hyderabad

Experience: 3 yrs- 6 yrs

Skills & Experience Required

Skills: MSI Adminstudio OVCM , MSI Adminstudio OVCM

Experience Required(Description) : Essential • Windows Installer technology specifications • Windows MSI Best Practices • Macrovision AdminStudio Enterprise version 7.5 • Macrovision Workflow Manager 3.5 • VB Scripting/Windows Scripting • Microsoft Compatibility List • Windows 2000 and Windows XP Professional • Adminstudio, Trouble shooting tools , ORCA, • HP OVCM

Roles & Responsiblities

Qualifications • 3/5 years experience in application packaging for Windows Installer. • Experience in Visual Basic scripting. • A strong understanding of software deployment tools. • Past experience with a Windows 2000 to XP migration • Experience Publishing applications into the HP OVCM environment • Good knowledge of the HP OVCM Configuration Manager/System Explorer structure and functions • Background with Active Directory and related skills such as GPO; • Must have a strong knowledge of Microsoft operating systems such as Windows XP, Windows 2000, Windows Vista. • Must have a background with Enterprise level Systems Integration. • Must have experience in testing and evaluating software installation on Microsoft Platforms • Good verbal and written English communication skills • Must be strong team player. • Outstanding Customer service skills required.

Please revert with your update profile with following details:
Total Experience:
Current CTC:
Expect CTC:
Notice Period:
Reason for Leaving:
Current Location:
Preferred Location:
Willing in Shift:
Date of Birth:
Place of Birth:

About Our Client:
Our client, a corporation among the top Indian IT Companies, is a global provider of consulting, IT Services, and outsourced R&D, infrastructure outsourcing and business process services. They are the first PCMM Level 5 and SEI CMM Level 5 certified IT Services Company in the world. They provide comprehensive IT solutions and services, including systems integration, information systems outsourcing, package implementation, software application development and maintenance, and research and development services to businesses globally.

Also forward this mail to your friends & colleagues

Thanks and Regards,

Sugandha

headsnminds
Management Consultancy

0091 22 64573440
0091 22 64573441/42/43/44
www.headsnminds.com
hr@headsnminds.com

Tagged : MSI

InstallerExpert created the topic: Creating MSI for 64bit machine

Hi
I want to develop a 64 bit MSI.
I have already developed 32 bit MSI. But now if i had to modify it for 64 bit machine, what changes do i need to make?
For eg:Package/@Platform , Component/@Win64, file/@ProcessorArchitecture

or will candle -arch command build 64 bit MSI for me?

Tagged : MSI