Deploying InstallScript MSI Installations
AdminStudio 2021 R2 | 22.0 | Package Distribution Wizard
When deploying an InstallScript MSI installation, the file setup.exe needs to be deployed with the InstallScript .msi installation file. The setup.exe file is required because it launches a file (isscriptn.msi) that installs the InstallScript engine required to run the InstallScript code. The n in installscriptn.msi indicates the version of the InstallScript engine that was used to create the InstallScript MSI installation.
If you want to deploy an InstallScript MSI installation without using setup.exe, such as when using Active Directory, you need to first deploy the same version of the InstallScript engine that was used to build the InstallScript MSI installation.
Installing the InstallScript Engine
Sometimes the isscriptn.msi file (the file that installs the InstallScript engine) is located in the same directory as the InstallScript .msi file. However, in some instances, the isscriptn.msi file is compressed within the setup.exe file and cannot be accessed.
If the isscriptn.msi file is compressed within the setup.exe file, you have the following options:
| • | If you know which version of the InstallScript engine was used to create your InstallScript MSI installation, you can get a copy of the InstallScript engine from the AdminStudio installation CD. All the major releases of the InstallScript engine are available in the InstallScript_Engines folder on the AdminStudio installation CD. |
Note:For more information, see the Update to the Latest InstallShield Installation Engines Knowledge Base article at:
| • | If you do not know which version of the InstallScript engine was used to create your InstallScript MSI installation, contact the software vendor to find out the exact version. |
Deploying an InstallScript MSI Installation
To deploy an InstallScript MSI installation, configure the setup and the target system in the following manner:
To deploy an InstallScript MSI installation:
| 1. | Run the isscriptn.msi file to install the appropriate InstallScript engine on the target machine (where n is the version of the InstallScript engine that was used to create the application’s InstallScript MSI installation). |
| 2. | Create a transform for the InstallScript MSI that includes the following changes: |
| a. | Add the property ISSETUPDRIVEN to the property table via the Direct Editor and give it a value of 1. |
| b. | Add a condition to the OnCheckSilentInstall custom action in the InstallExecuteSequence via the Direct Editor that will always resolve to false or remove the custom action from the sequence. |
| c. | Make any additional changes in the transform, such as populating the serial number, modifying shortcuts or feature states, depending upon your organization’s needs and the features and requirements of the application. |
| 3. | Next deploy the InstallScript .msi package. |
If deploying the package via Active Directory, make sure that you set the Installation User Interface to Basic and specify any transforms that you created for the InstallScript MSI package.