Software Deployment

I would imagine that a Microsoft app would already be in MSI format, albeit wrapped in an EXE.

Re-run the installer manually and, when you see the first screen - normally a 'Welcome' screen - check the %TEMP% and %AppData% folders for new MSIs.

I tried the steps you metioned from a handful of different ponts in the installation but no joy. I also used the /x switch to extract the contents of the exe and this revealed 3 or so msi's but none of thoe msi's were enough to run on their own and were dependant on suport dll and the like files.

I presume the software installation of the gpo will only take 1 msi file and not all its supporting cast of files?

Thanks for your reply.

The WI engine cannot execute 2 MSIs at the same time so you're going to have to perservere with this one (or use a ZAP file to run a script to run the EXE - arrrrrrrrrrrrrrrrrrgh! Trust me, you don't want to go there). If there are support files required, capture just those and run the resulting MSI first.

You can chain MSIs (and associated MSTs) in a GPO. Just add them in the order of installation. Remember that you must add the transform at the same time as the MSI. If you forget one, you'll need to remove the MSI and start again.

I beleive the zap method only permits the app to be publised and not assigned so yeh ill give it a miss. The transform file method Im willing to explore this before I go for the silent install command line switch route.

I have googled for transform files using a combination of keywords, but I cant sem to get an straight explanation for what they do! and the steps for their usage. .mst files and their purpose & their creation is still somewhat obscure.

Regrettably, this isn't the right place for a course in Windows Installer. Apart from anything else, I simply don't have the time.

If packaging is something you're going to be doing much of in future, I'd recommend that your employer springs for a package authoring tool. There is now only one player of any note: InstallShield.

Before that, though, I'd recommend you read & digest Phil Wilson's ouevre, The Definitve Guide To Windows Installer since you'll find the process features a very, very steep learning curve unless you understand the fundamentals.

I fully understand. I was only looking for a description of what a transform file was and whether it was a straight forward process in creating one /special software/ chances of success / learning curve etc.

If creating a transform file is sonething that requires a course or disgesting a book then like that I dont have the time either as I have many jobs qued up and dont have that luxary. Im basically a field medic in a war zone where company just wants the msi and does not have a full appreciation of the matter.

The most effecient path I now know is the command line route so I least now I know its the best solution all in all.

I appreciate you help mate

Thanks.