Software Deployment

Re-package into an MSI. You can then specify the '/qb' switch against MSIExec.EXE to present a basic UI when installing.

Thanks VBScab. Unfortunately it appears this exe was created using InstallShield. That being said it creates a temp directory when run that has the extracted MSI,cab and other files contained within. Even running the msi copied directly out of the temp folder appears to do nothing. I checked the event log and it reports that the install completed but nothing appears in program files, or anywhere else I can find, for the app.

It sounds like the main IS executeable installs a bunch of stuff, then extracts and executes an MSI. Typical vendor shambles...You could prove whether or not that's the case by examining the uninstall string entry in the package's 'Uninstall' registry entry. If that's the case, I would:

- execute the extracted MSI so that it installs as a kind of pre-requisite
- capture the IS install into your own MSI.

Thanks again! I don't have experience with locating the uninstall string, I'll look into that ASAP.

The exe certainly appears to have several built in components, aside from the app itself.

I will do some additional testing and post my findings. Again many thanks for time and assistance offered thus far.

I don't have experience with locating the uninstall stringIt'll be in the registry, under HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall\[ProductCode | ProductName]

A ProductCode is a standard GUID, enclosed in braces, e.g. {90120000-0020-0409-0000-0000000FF1CE}

I don 't want to be rude but if you have no understanding of this basic element, you'll find packaging a challenge unless your employer springs for some training.