I have a PC manufacturer who wishes to bundle our product on their machines at build time. It is one of several pre installed packages they wish to bundle with the machine and needs to be run silently. However, after running the install command from a CMD window, controls is immediately returned to the user before the MSI is unpacked, allowing the user or a batch command to immediately launch another installer which would then fail due to two MSIs running at the same time.
After investigation I suggested using the start /WAIT switch, namely:
This seems to work at our end. Trouble is the feedback loop is through a variety of account managers and across 3 timezones and is troublesome, meanwhile the timescales are critical. So the question is, is there a better way of doing it? We got one comment back stating that their other packages handles this without the need for the cmd line switch.
I have to confess that our product is still using IS 11.5, do newer versions of IS provide a built in method?
Basic MSI with a Setup wrapper.
After investigation I suggested using the start /WAIT switch, namely:
start /WAIT Setup /s /v/qn
This seems to work at our end. Trouble is the feedback loop is through a variety of account managers and across 3 timezones and is troublesome, meanwhile the timescales are critical. So the question is, is there a better way of doing it? We got one comment back stating that their other packages handles this without the need for the cmd line switch.
I have to confess that our product is still using IS 11.5, do newer versions of IS provide a built in method?
Basic MSI with a Setup wrapper.