InstallSheild-Setup silent installation not working.
Hi,
I am having issues deploying an InstallShield setup installation. I have created the setup.iss file by using the "setup.exe /r", and I have been trying to install it using "setup.exe /S /SMS" and it doesnt work.
I've even tried packaging it up in InnoSetup, dumping it to C:\TEMP and getting InnoSetup to run it, no joy.
From what I have read, setup.exe is just a stub that calls another install process hence the "/SMS" switch to keep setup.exe in memory.
The only problems I ever have with installers on SMS are with InstallShield installers, so any input or advice would be greatly appreciated.
thanks in advance
James
I am having issues deploying an InstallShield setup installation. I have created the setup.iss file by using the "setup.exe /r", and I have been trying to install it using "setup.exe /S /SMS" and it doesnt work.
I've even tried packaging it up in InnoSetup, dumping it to C:\TEMP and getting InnoSetup to run it, no joy.
From what I have read, setup.exe is just a stub that calls another install process hence the "/SMS" switch to keep setup.exe in memory.
The only problems I ever have with installers on SMS are with InstallShield installers, so any input or advice would be greatly appreciated.
thanks in advance
James
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
omniwolf
17 years ago
Posted by:
jimmycal77
17 years ago
It doesn't work in that, setup.exe is not kept in memory so when setup.exe spawns the installation process it hands back to the user who does not have admin rights. As the setup.exe has been called with the silent "/s" switch, and an error is encountered, the install silently fails.
The /SMS switch is meant to keep setup.exe in memory so all process spawned from there can run with elevated privileges.
The /SMS switch is meant to keep setup.exe in memory so all process spawned from there can run with elevated privileges.
Posted by:
Bladerun
17 years ago
Late post, but are you running this from a read-only source location? If so try re-directing the log file as it usually defaults to logging to the same directory as setup.exe (use the -F2 command if memory serves.
Also, have you verified that the command you need is indeed '-s'? I've seen some variants of the installshield installer that need a '-silent' or 'responsefile=', etc.
Also, have you verified that the command you need is indeed '-s'? I've seen some variants of the installshield installer that need a '-silent' or 'responsefile=', etc.
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.