Software Deployment

You need a type 7, 23 or 39 custom action to run an msi from within an msi.

But chaining msi's is not recommended as it becomes messy. Especially when it comes to upgrading

If I were in your situation I would create a wrapper script to run your msi's or depending on your deployment tool use pre-requisites

Hi

I am not launching MSI from MSI, my MSI is doing the following things

1) Unpack and copy file to temp folder (Test01.msi, Test02.msi and Test03.exe)
2) Then before completing the MSI launch batch file to execute Test01.msi, then Test02.msi and then Test03
3) once batch file is completed then run 2nd batch file to remove temp folder

But while my MSI is still running on the background the test01.msi fails because it detects that original MSI is still running. This is not for upgrade, this is only one time MSI which has all the prerequisite MSIs and EXEs.

Also where do I need to type 7, 23 and 39 and under what section. I am not expert in Packaging :)

Many thanks

I am not launching MSI from MSI, Er...yes, it is.

The MSIs will be in the Binary table. Use InstEdit or Orca to extract them then build your wrapper to execute them.

what tool are you using to create your msi?

I think your using an msi unnecessarily, why not install the lot from your batch file?

What's made you wrap it in an msi?

Well all the files are on different locations and it has been a pain to use all or run those from different locations to prepare the machine for development or QA. My Manager came up the idea to package those and then MSI installs it... BUT I think I have made my mind up now and going to zip the files and ask to launch the Batch file.

Many thanks

Probably a good move. It doesn't sound like there are any grounds here to use an MSI.