Deploy Windows Installer 4.5 via SCCM 2007

hope this helps


http://sms2003-sccm2007.blogspot.com/2010/04/windows-installer-msiexec-silent.html

Thanks for the link.  I have the setup parameters I want to use - /quiet /norestart.  I am able to run the setup successfully from command line on the local machine.  I used the same commands/parameters when creating the software package in SCCM.  The installation fails.  I'm currently researching what logs to look at in troubleshooting failed software deployment.  My experience thus far is that any .exe file I use fails.  I have been able to extract a setup file and use an .msi, or download an .msi format and deployment is fairly easy.  However, there are only .exe files after extracting the Windows Installer 4.5.  I've tried specifying the update.exe from the extracted files, which installs the update when ran from the GUI.  This fails also.

this should fix it

https://www.experts-exchange.com/questions/25410618/Deploy-Windows-Installer-4-5-through-GPO.html

Thanks npsingh123.  I had to add the right parentheses at the end of line 17.  But, the script works on the local machine.  Now I just have to make it work from SCCM.  I don't think deploying it as a GPO startup script is preferable in this scenario because we have XP and Windows 7 mixed throughout.  Hopefully, I'll post a little later with success.

I believe that WSUS also can update lower versions of Windows Installer to 4.5 and above. You solution maybe as simple as approving/pushing this update.

We don't have WSUS installed as I am anxiously waiting for a server upgrade.  I don't know how much more the system will handle.  Windows Installer 4.5 is not available through Windows Update though
http://social.technet.microsoft.com/Forums/uk/configmgrsum/thread/192ec521-89e2-4b57-a350-8d976e2866ab 

It was this thread that made me think deploying it via SCCM shouldn't be that difficult.

I have been able to deploy it, but not without user interaction.  When the script is called, it pops up a box to Run or Cancel the executable.  This is the behavior when run locally as well.  I was hoping it would run without interaction from SCCM like other software programs.  I've tried using this:

cscript.exe //nologo //b “installscript.vbs” which was found here http://7front.wordpress.com/2010/05/19/correctly-install-software-using-vbscripts-in-sccm-2007/ 

This did not work either.  If I could get past this I would be good to go.

This will work.  Thanks a lot for your help!