Vendor InstallShield EXE repackage
I have a vendor that send me an installshield .exe file that calls a .msi file. I am trying to make a silent install of this package to deploy to 2500 computers. Not all of our computers already (some are NT) have the windows installer service installed, so I have to use the .exe and not the MSI (The exe seems to install the windows installer service, then uses that MSI to install the program) I have tried opening the .exe file in installshield, but it won't allow it to be openend (so I can't edit it either). When I use the silent or answer file switches it never goes silent nor does it make an answer file.
Anyone have any suggestions on setting this up so it doesn't prompt the end user for any options? Is there any way to open an installshied setup.exe file without have the installshield project?
Thanks
Anyone have any suggestions on setting this up so it doesn't prompt the end user for any options? Is there any way to open an installshied setup.exe file without have the installshield project?
Thanks
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
VikingLoki
20 years ago
The easiest way to extract the files (no tools required) is to launch the install on a lab machine, let it extract the files to the temp directory, then let the install sit there. In the meantime you can copy the files out of the temp directory in the user profile. You'll find a couple of MSIs in there.
Ultimately, you are going to go through a step process to get your environment ready to use MSI installs, and InstallShield Script driven MSI installs.
1 - Get Windows Installer installed everywhere so all machines can run MSI installs.
2 - Get the ISScript.msi you extracted from the temp directory above. This is the InstallShield Script Engine and its a "normal" msi that can be transformed. Deploy this everywhere so you can deploy InstallShield Script driven MSIs.
Now you are capable of installing standard MSIs and InstallShield Script Driven MSIs. You don't need to do the steps above again for any other applicatoin unless newer versions come along.
Use this link for instructions on modifying the application's main MSI so it can be launched as a regular MSI, using the InstallShield Script Engine already installed on the machines.
http://itninja.com/blog/view/7.8-gigabyte-size-limit-in-nt''s-ntfs4
Ultimately, you are going to go through a step process to get your environment ready to use MSI installs, and InstallShield Script driven MSI installs.
1 - Get Windows Installer installed everywhere so all machines can run MSI installs.
2 - Get the ISScript.msi you extracted from the temp directory above. This is the InstallShield Script Engine and its a "normal" msi that can be transformed. Deploy this everywhere so you can deploy InstallShield Script driven MSIs.
Now you are capable of installing standard MSIs and InstallShield Script Driven MSIs. You don't need to do the steps above again for any other applicatoin unless newer versions come along.
Use this link for instructions on modifying the application's main MSI so it can be launched as a regular MSI, using the InstallShield Script Engine already installed on the machines.
http://itninja.com/blog/view/7.8-gigabyte-size-limit-in-nt''s-ntfs4
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
