'WriteGroupStatusFile','193','LAPUTILS_BINARY','WriteGroupStatusFile' 'SetARPINSTALLLOCATION','51','ARPINSTALLLOCATION','' Here is a list of entries under custom actions table I did but I couldn t find anything about DB2 MSI install.IBM suggests to use the original setup.exe with a response file but company policy where I work, it has to be in MSI format for all the good reasons we know. It is always worth checking at /packages for any commercial software you need to package, as there is a large database of information on how to package generated by other users, and it can save you a heap of work. Once you have cracked this first step, you can then follow VBScab's advice on other aspects of the install. These have been documented elsewhere, but as a general rule if you are using a deployment system you have to deploy ISScript.MSI separately for things to have any chance of working. Versions of ISScript.MSI at V7 and some V8 releases did not deploy correctly using SMS due to DCOM issues. This needs to be installed prior to the main MSI. If you managed to grab the MSI from the temp folder after running the EXE, look for the associated version of ISScript.MSI as well.

With the arrival of V12, the product was finally updated so that the scripting engine was no longer required for the Installshield MSI to work. The scripting engines were required to allow users familiar with the legacy Installshield tools to migrate to MSI technology without having too big a learning curve. The following version numbers are ones I include in standard operating system builds wherever possible - V7, V8, V9, V10, V10.5, V11 and V11.5

During the lifetime of the 'not quite MSI compatible' Installshield MSI tools, there were several versions of the ISScript.MSI scripting engine released, which are a pre-requisite to these MSI installs. A lot depends on which version of Installshield was used to create the original package.

Installshield msi wrapper