Menu
![Batch Batch](/uploads/1/2/5/5/125526251/653924961.png)
Execute Script/Batch File allows developers to enter the text of a script or batch file which the installer executes on the target system. When this action runs, it first. Some project-specific differences are noted where applicable. InstallShield lets you specify commands that you want to be run at various stages of the build process. For example, if you are developing a Basic MSI project, you may want to modify the.msi package that InstallShield creates at build time before InstallShield digitally signs it and streams it into the Setup.exe file.
Depends on the Installer
If this is an InstallShield package, you can create a response file.
Run the installation with the /r switch, and select your installation options as normal. Once installation is complete, you should have a setup.iss file in either c:windows or c:windowssystem32. Copy this file to the same directory as the installation file.
You can now run the installation file silently using test.exe /s
A lot of .exe installers are 'wrapped' installshield or MSIs, that generally expand to a temporary location, and run from there.
Run the installation as normal until it requests some interaction, then look in C:temp, or wherever your temporary directory is, and it may have expanded itself there.
If it does, then copy the new folder to another location, as they get deleted when the installation completes.
If the contents contain an installshield package, then you can then follow the instructions above. If it contains an MSI, then your best bet would be to create a transform file (MST), and install using the MSI and the MST (not the exe).
As an aside, what is the installation for? If it's an off-the-shelf/downloaded package, the I might be able to give you specific instructions.
Run the installation with the /r switch, and select your installation options as normal. Once installation is complete, you should have a setup.iss file in either c:windows or c:windowssystem32. Copy this file to the same directory as the installation file.
You can now run the installation file silently using test.exe /s
A lot of .exe installers are 'wrapped' installshield or MSIs, that generally expand to a temporary location, and run from there.
Run the installation as normal until it requests some interaction, then look in C:temp, or wherever your temporary directory is, and it may have expanded itself there.
If it does, then copy the new folder to another location, as they get deleted when the installation completes.
If the contents contain an installshield package, then you can then follow the instructions above. If it contains an MSI, then your best bet would be to create a transform file (MST), and install using the MSI and the MST (not the exe).
As an aside, what is the installation for? If it's an off-the-shelf/downloaded package, the I might be able to give you specific instructions.
Share Flag
Try this one
There is a nice program called AutoIt. I've used it to create administrative installs for users who don't have admin rights. I haven't created a scripted install like you are trying to do but this program can do it from what I have read.
Give it a whirl and let us know what you think.
http://www.autoitscript.com/autoit3/
Give it a whirl and let us know what you think.
http://www.autoitscript.com/autoit3/
Share Flag
The tool to automate software installation
Another useful tool is Silent install builder. It allows to fully automate installation of the software.
http://silentinstall.org
http://silentinstall.org
Share Flag