Hi,
Some vendor provided MSI packages may insist on being run from a setup.exe. This is to ensure that the latest version of InstallShield Script is present on the system. This too is an MSI, so deploy it separately and then make the following changes via a transform (MST) to stop the MSI from checking to see if it was run from its setup.exe file...
1) Add the property ISSETUPDRIVEN to the property table via the Direct Editor and give it a value of 1.
2) 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.
Regards
Mike.