To find the nested msi sequence
hi ,
I am packaging an app which is having a wrapper exe which calls a msi AdobeAfterEffects ,
which inturn is responsible for the installation of five other msi's ,I am unable to find out where actually
these msi's are being called.
I have found only one msi in the custom actions that to in the deffered mode,
kindly help me to know the sequence .
cheers,
Akram
I am packaging an app which is having a wrapper exe which calls a msi AdobeAfterEffects ,
which inturn is responsible for the installation of five other msi's ,I am unable to find out where actually
these msi's are being called.
I have found only one msi in the custom actions that to in the deffered mode,
kindly help me to know the sequence .
cheers,
Akram
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
anonymous_9363
16 years ago
I'd be willing to bet a fairly substantial wedge that this is being done by function calls to custom DLLs, something which is a) becoming all too common and b) a royal PITA for corporate packagers. Does performing an admin install extract these MSIs? Failing that, enable logging for a normal install: that should at least show you where in the sequence MSIEXEC gets called.
Posted by:
nheim
16 years ago
Hi Akram,
welcome to the Adobe CS3 affected deployment people! :-(
Look at this thread: http://itninja.com/question/how-do-you-roll-out-new-machines?6716
There, i have quick and dirty posted my findings about this setups so far.
The real installation gets started by the CA 'Adobe_ID0E6B' (at least in Photoshop) in 'WinBootstrapper.msi', it's the second last sequence in 'InstallExecuteSequence'.
What i don't have, are all the necessary prestaging things that the 'setup.exe' (and WinBootstrapper.msi) portion of the installation does.
Maybe, a capture with Wise or IS could enlighten this things.
Hope, this gives you some ideas to dig further.
Typical Adobe again, i must say. Never doit the standard way, allway make it very difficult for Administrators. And it's the same on the OSX-side! :-(
Regards, Nick
welcome to the Adobe CS3 affected deployment people! :-(
Look at this thread: http://itninja.com/question/how-do-you-roll-out-new-machines?6716
There, i have quick and dirty posted my findings about this setups so far.
The real installation gets started by the CA 'Adobe_ID0E6B' (at least in Photoshop) in 'WinBootstrapper.msi', it's the second last sequence in 'InstallExecuteSequence'.
What i don't have, are all the necessary prestaging things that the 'setup.exe' (and WinBootstrapper.msi) portion of the installation does.
Maybe, a capture with Wise or IS could enlighten this things.
Hope, this gives you some ideas to dig further.
Typical Adobe again, i must say. Never doit the standard way, allway make it very difficult for Administrators. And it's the same on the OSX-side! :-(
Regards, Nick
Posted by:
jmcfadyen
16 years ago
a verbose log should determine pretty quickly whats going on behind the scenes.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
