Is there any MSI wrapper that works from a command line? Or even an MSI creator that could be automated?
I have a client that requires an MSI file to roll out into their windows server environment. What I need to package is a .exe file (windows Zabbix agent) that installs itself as a service from wherever the file is located when you run it.
Currently I have a self-extracting .exe that runs a batch file, and then I use a free MSI wrapper to convert it to MSI.
I'm trying to automate this so my co-workers can change zabbix config files and then run a batch that creates the package for them. I can do everything up to creating the MSI.
Try to use http://www.suiviperf.com/zabbix/.
Or check Zabbix forum, it contains similar questions:
e.g. https://www.zabbix.com/forum/showthread.php?t=22688
You can try Advanced Installer, it has a free 30 days trial for you to test. The Professional edition can help you create and MSI that wraps your EXE (one or many).
Also, it has a command line interface, so you can automate the build process for the setup package.
Related
I have created installer using install-shield 2013. Installer deploys the file and there is one executable file. I did some changes in executable file and created installer again.
When I upgraded using installer then I found my executable is not replaced with new one.
In Install-shield, I went to "Releases", go to the "Setup.exe" section and there's a field called "MSI Command Line Arguments" and provided REINSTALLMODE=emus REINSTALL=ALL but it did not work.
Please suggest for same.
Regards,
Rashi
The requirement is to convert an msi to a executable file. There are tools available to convert the msi to .exe . But here while executing the msi a lot of parameters passed . This is achieved by writing a batch script and running it from the location of .msi . Now the requirement is to convert the .msi to .exe with parameters passed during conversion.
Is there a way to achieve this using programming/ any tools available?
Thanks in advance
You can try to use any installer tools like InstallShield, Advanced Installer, etc. which have prerequisites support. Then, you can add the MSI as a prerequisite to an EXE installation package.
I've built an installer using InstallShield 2011. I need to do a silent install so I ran the setup.exe with the -r flag to record the response file. However, the installer doesn't appear to actually generate a file (I've looked in the windows directory for the .iss file - in fact I've looked over my entire hard disk for .iss files)
I'm installing on Windows 7 64 bit Ultimate Edition and running from an elevated command prompt
Has anyone seen this before or have any ideas why the file isn't getting generated?
I've Visual Studio setup project for creating installation for my project. After build Visual Studio create two files: *.msi file and setup.exe file.
MSI file contain all project files, information about destination, registry entries, etc. Setup.exe just bootstrapper for running msi file, but end-user is able run only msi file without setup.exe and program will be installed correctly.
What setup.exe do? Should we run installer only using setup.exe or we can distribute our product without setup.exe?
Yup .MSI version is enough.
Check this other post.
What are the benefits of a MSI installer over a standard setup.exe?
Best Regards
I have a windows installer msi package with the setup.exe bootstrap. Works fine everywhere.
However the client has supposedly uninstalled the application and then tried to run the setup.exe again and gets the following error in the log file: Launching Application. Error: Unable to locate application file 'xyz.msi'.
Now the setup.exe and the msi file are in the same folder. Is this even possible in any scenario?
I think it is looking somewhere daft for your MSI, probably in the MSI cache or System32.
I'd suggest using procmon to capture the file system searches and then search that output for your MSI file name. You'll see it is not found a few times but that will show you where it is looking.
Ryan
If you're looking for a quick, one-time fix you could also just try to run the .msi directly.