Could someone confirm that it is NOT possible to create a properly working MSI package for either Acrobat Professional or Standard 6.02 using the normal repackaging method, for example with Wise Package Studio (running setup.exe to install initiallyto craete the snapshot not the original. msi of course) ?

I thought I had success until I noticed that the file association part did not work, it is not possible to open Acrobat by clicking on any .pdf files. The system claims that this functionality is only for products which are installed. So this would indicate something to do with a product code or a Class ID or something.

Adobe uses it's own product code all over the place and I have even replaced all of these with the Wise newly regenerated code. Basically over one week, I tested dozens of variants packaging this. Today my last attempt was to use Installshield Admin Studio just for trying and the same problem occurs.

I really need to report back to Management whether I have to use the approach of using the original .msi from Adobe and apply a transforms to it instead ?

Thanks for your support

Nathalie O'Flynn
0 Comments   [ + ] Show Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.


Acrobat is a problem package for many people that post here. http://www.appdeploy.com/messageboards/searchpro.asp?forumid=4&phrase=acrobat

Here is the link for the enterprise deployment tools. You can use the Installshield Tuner to create your Acrobat .MST. http://www.adobe.com/products/acrobat/deployment.html
Scroll down to the bottom for the tuner download.

The answer is that you have to use the original.msi with your custom transform.
Answered 10/11/2004 by: Garrett
Orange Belt

Please log in to comment
it is possible but its a little annoying.

I did one up to 6.03 repackaged however it doesnt support per user based installation
Answered 04/10/2005 by: jmcfadyen
Fifth Degree Black Belt

Please log in to comment
I have repackaged both Standard and Pro 6.02 with the Office 2003 updates.

I have deployed it Published to users and it works perfectly.

The trick is to capture the Multi_SZ keys correctly and create a custom action to install and uninstall them.
Answered 04/11/2005 by: MSIMaker
Second Degree Black Belt

Please log in to comment
Answer this question or Comment on this question for clarity