SCCM and Install Shield MSIs
I have been out of the SCCM deployment scenario for a while and now I need help to understand whats going wrong with install shield MSIs deployed from SCCM. I have a bunch of install shield packages that are failing on me for one or the other reasons. One of them had the ROT table issue which would not go away even with the popular appdeploy vbscript. So I gave in and installed the setup.exe with silent parameters. (This still works only when the user is not logged in to the machine)
Now, I have two more install shield MSIs, which return Success on install from SCCM in the verbose log but they havent actually installed. I run the same MSI manually on the system and it installs fine.
Commandline:
msiexec.exe /i PixTools-6-4.msi TRANSFORMS=PixTools-6-4.mst /passive /l*v C:\Windows\Temp\Pixtools-6.4.log
Now, I have two more install shield MSIs, which return Success on install from SCCM in the verbose log but they havent actually installed. I run the same MSI manually on the system and it installs fine.
Commandline:
msiexec.exe /i PixTools-6-4.msi TRANSFORMS=PixTools-6-4.mst /passive /l*v C:\Windows\Temp\Pixtools-6.4.log
0 Comments
[ + ] Show comments
Answers (6)
Please log in to answer
Posted by:
anonymous_9363
12 years ago
Posted by:
jmaclaurin
12 years ago
Posted by:
pjgeutjens
12 years ago
I have found many installshield MSI's that are hooked to the setup.exe and can't be run separately as of late. I even found one that would not run silent unless it was called from a silent.bat. New trend I guess and it sure is annoying.
I assume these are not the standard "ISSETUPDRIVEN=1" type of MSIs?
Posted by:
jmaclaurin
12 years ago
Posted by:
Matias M Andersen
12 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.