Hi All,
Let me first start by saying I know next to nothing about SCCM or its inner workings so I hope I can at least get a direction by posting here.
We have a customer who, of course, is deploying our .msi package via SCCM. During this install, we place a secondary, native 64 bit install package on systems of that architecture. We need to run this installer to place third party related files and registry values in native 64 bit areas. Lame, I know, but development is currently unwilling and/or unable to move the base application to 64 bit so I have to live with this for now. Near the end of what I'll call the parent install for lack of a better term we launch a widget that waits for the parent .msi process to clear then fires the secondary 64 bit installer.
The monitoring and install firing Custom Action widget that runs is set as Asynchronous - no wait.
At the customer's sites, the secondary installation is not installing on 64 bit systems. I'm not quite sure what is happening, but I have a few guesses. What might be happening is the parent install is detecting the need for reboot and does so following completion, thus killing the asynchronous monitor/fire widget and the installation of the secondary package.
My first thought was to leverage Windows Installers ReplacedInUseFiles. If set (reboot required from parent), I would write a RunOnce key to launch the secondary installer. If not set, I would just launch the 64 bit installer. However, what if my next guess is in play...
The main install finishes without the need for reboot, but SCCM is causing or forcing reboot in some manner. Again, I'm guessing there are some settings that might control this.
That's the summary so feel free to ask questions for more detail. I've seen some mention of Task Sequencing and wonder if that can be put into play somehow. Maybe we supply the secondary installer separately to our SCCM folks -- they could run the parent first through SCCM then the 64 bit Installer. ??
Any help is GREATLY APPRECIATED!!!
THANK YOU IN ADVANCE!!!!
