Software Deployment

I would suggest you to follow these steps to findout the problem with your package.

1.Install the MSI created by you in a clean machine and do the intial scan using wise.
2.Install the source on top of this and do the final scan.
3.You will get the missing resources in your package by performing this.

One more thought on Adobe 6.0

First of all Adobe will be in the form .EXE file Pulling a MSI.So you need to create only transform.

It is the best practice.

Hope it will help you

Regards,
Adaptability.

Hi,

I did all 3 steps and included some of missing files. But still throws same error.

Soundgct,

Acrobat 6 and Acrobat Reader 6 are already in .msi format - although they sometimes require a little tweaking to acheive the desired results.

You may want to do a search on the forums here to see how others have modified the .msi's as they come from Adobe.


Craig --<>.

I've repacked the version 6.0.1 of Adobe Reader

Fetgor,

I am not saying that you cannot repackage Acrobat Reader 6.0.1 - or the full Acrobat, for that matter. Best practices, however, say not to repackage an existing .msi into another .msi. The reasons for this are best explained here:

http://www.appdeploy.com/FAQ/detail.asp?id=6

Acrobat Reader is an ".exe wrapped" .msi. The .msi can be extracted very easily. Information on how to do this can be found here:

http://itninja.com/link/acrobat-reader-6.0-deployment-notes-from-the-field

The extracted .msi can be modified by creating an .mst file with the InstallShield Acrobat Tuner tool. The .mst (transform) can then be applied to the .msi at the time of install to acheive customization.

If there is something specific which cannot be acheived with the native .msi and a transform, then you have reason to repackage it. However, keep in mind the potential pitfalls of doing so. Your testing will have to be much more thorough than normal to make sure absolutely everything works.

Craig --<>.