Software Deployment

If you're lucky, this might work out for you. What you want to do is copy the unpacked install files to a virtual machine of some shorts, clear the application logs and then start the installer for a CLIENT install. Make sure you added .Net 3.5 or whatever pre-reqs it needs. After you install the client, have a look in the (Application) Event logs for MsiInstaller, this will hopefully let you know which msi installer was run to install the client, you will probably need to dig around in the registry for your company settings, you can add them to a transform (so when you install they will be added as well).

Top line, installer running logged event, bottom bit shows where the msi was run from.

Once you have all the MSIs, you can install one by one and see if you get the desired client install, once again you will most likely need to add some registry files. Unless its nice enough to shove them into a ini file - I noticed you can install to a UNC path, hence the ini suspicion.

This is a exe wrapper that launches the msi installers for the required install type. You could also deploy it with a config passing it the exe, I see you have looked into that - its definitely worth giving them a ring to see if there product supports a enterprise unattended deployment. I would try and make sure you cant use a config.ini passed to the setup before going down the road of pulling out MSIs from the installer package. The former would be a lot easier than the latter.

Once you start getting into Transforms etc, it starting to get pretty complex, this is basicly a applications packagers job - sooo ahh, good luck!