In our earlier post we explained how to extract an MSI from the Setup.exe. The MSI is normally extracted to the %temp% directory.
In some applications when you try to run these MSI’s that are extracted they will throw the following error message “This application cannot be installed. Please run the application from SETUP.EXE
1. Installing an msi from command line
MSIEXEC /I “PATH TO MSI”
2. Installing an msi from command line silently
MSIEXEC /I “PATH TO MSI” /QB Displays progress bar and cancel button
MSIEXEC /I “PATH TO MSI” /QB+ pops up a status windows after the installation
MSIEXEC /I “PATH TO MSI” /QB! Displays progress bar without cancel button
MSIEXEC /I “PATH TO MSI” /QN Displays nothing
MSIEXEC /I “PATH TO MSI” /QN+ pops up a status window after the installation
3. Installing an msi from command line silently and creating a log file.
MSIEXEC /I “PATH TO MSI” /QB /L*v “c:\logs\example.log”
1. Active setup is a process that runs automatically during the login process.
2. It is mainly used to complete specific run once setup tasks for each user as they log in to a given machine after an active setup based package is installed.
In the recent times most of the installation files that are provided by the vendors are in .MSI format. However some vendors do provide installation files in Setup.exe format. The Setup.exe’s that are build by installshield has an embedded .msi files in it.
It is easier to package these types of applications by extracting those .msi files and creating Transforms for these MSI’s.
Note: DONOT USE SETUP CAPTURE OR USE REPACKAGER TOOL TO PACKAGE THESE TYPES OF EXE’S.
Installshield Setup.exe allows creating a Response file. Response file is set of instruction captured in the process of installation. The iss file contains the customizations that were captured during installation. This is very helpful during deployment in large enterprises as it facilitates silent/unattended installation.
/r or -r
/f1 or -f1
/f2 or -f2