Software Deployment

kindly let me know the process followed for the sameTo do what, exactly? please clarify wat it is you need help with.

Hi VBScab,
Thanks for your reply.
The source file of this application has setup.exe and two update files which needs to applied to the main appliction.
After extracting these exe it has msp and msi respectively.
I need deliverable as msi/mst for this package.
Any help is really appeciated.

Regards,
Sumi

I suspect you are deploying via Group Policy, hence the need for only a single MSI and an MST?

You need, therefore, to explore how the MSP is being used. If it's being applied as a patch - in the traditional way - then the simplest route is to create an Administartive Installation Point, patch that using the MSP and then create tthe transform from the resulting MSI. If, however, HP (or whoever owns BO this week) has taken Bill's shilling and is using MSPs as "transforms on steroids", in the same way that Office 2007 is, it may be that the MSP can just "sit" with the MSI, whereupon it will be processed, presumably by a Custom Action in the MSI.

Does the vendor not have explicit instruction on GP deployment?

I just finished a package for BO XI FP 2.3.
Basically, for the updates in the form of an msp I made an AIP, like Ian said, and installed from there.
The fixpacks however were complete standalone MSIs that had to be installed alongside the main BOXI installation.

So you might be forced to split up the installers for the main application and the fixpacks...

Also, make sure of 2 things:

- the installation from the msi actually completes successfully, we had issues with the fixpacks not finding the main install's version and failing. Had to add a property to the command line to skip certain version checks. If this happens to you you'll find the property name in the event log on your test machine.

- after your install compare the machine to a manually installed one. Those setup.exe files that you use for manual installs are more than meet the eye. I've run into some that did extra DLL registration outside the MSI. This also ties into point one since those MSIs would then fail on dll registration when running outside of the setup.exe

Hope this helps you out.

PJ

after your install compare the machine to a manually installed one. Those setup.exe files that you use for manual installs are more than meet the eye. I've run into some that did extra DLL registration outside the MSI. This also ties into point one since those MSIs would then fail on dll registration when running outside of the setup.exe ...something which you should be doing anyway, where a set-up stub is used.