suppress reboot
Hi There,
I have created an answer file.iss and I made sure the BootOption=0 in the end of the file. Although the installation is silent but the PC does get reboot in the end. Is there away to suppress the reboot throught a command line. During the manual install I clicked cancel to restart the computer and that have reflected on the answerfile.ISS but not sure with running it through the command line the PC restarts itself.
This is the command line I used.
Setup.exe /s /F1"C:\temp\answerfile.iss"
Any suggestions will be helpful.
Thanks
I have created an answer file.iss and I made sure the BootOption=0 in the end of the file. Although the installation is silent but the PC does get reboot in the end. Is there away to suppress the reboot throught a command line. During the manual install I clicked cancel to restart the computer and that have reflected on the answerfile.ISS but not sure with running it through the command line the PC restarts itself.
This is the command line I used.
Setup.exe /s /F1"C:\temp\answerfile.iss"
Any suggestions will be helpful.
Thanks
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
jcarri06
15 years ago
Smart,
Have you tried passing parameters to the msi through /v? The syntax escapes me a bit right now, but you should be able to do something along the lines of:
Setup.exe /s /F1"C:\temp\answerfile.iss" /v"REBOOT=ReallySuppress"
Not 100% of the order there.
Good luck,
J
Have you tried passing parameters to the msi through /v? The syntax escapes me a bit right now, but you should be able to do something along the lines of:
Setup.exe /s /F1"C:\temp\answerfile.iss" /v"REBOOT=ReallySuppress"
Not 100% of the order there.
Good luck,
J
Posted by:
anonymous_9363
15 years ago
Your response presumes that there's an MSI involved which, for InstallShield, isn't always the case. If there was an MSI, the OP could of course bypass using the set-up stub altogether and add the relevant properties to a transform.
Posted by:
jcarri06
15 years ago
ORIGINAL: VBScab
Your response presumes that there's an MSI involved which, for InstallShield, isn't always the case. If there was an MSI, the OP could of course bypass using the set-up stub altogether and add the relevant properties to a transform.
Ok, my above post is "assuming the Installshield setup invokes an MSI". So, if it doesn't... hm...Have you considered repackaging it to MSI? I know it sounds a bit extreme to avoid a reboot...but if you really really really really need it, so be it. Plus, you're deploying an MSI instead, which is always good :).
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
