Hallo Everybody,
i deploy Adobe Acrobat 6 with the original MSI-File and a MST-File that i have created with the Adobe Install Shield Tuner. The installation off Adobe Acrobat 6 runs perfekt and sucessfully.
But now i have to change something:
My Firma want to have, that when any user open a PDF-File, the PDF-File must be opened by Acrobat Reader and not with the later installed Adobe Acrobat 6.
Normaly there is no Problem to change automatically the Registry after the automatic installation auf Adobe Acrobat 6. But when you change the Registry keys after the automatic Installation of Adobe Acrobat 6 the WindowsInstaller correct the changes when sometimes something is wrong with the aplication and the make a reinstallation.
So i had to find a solution to change the registry settings in the original MSI-File from Adobe Acrobat 6 that in future PDF-Files opened with the Adobe Reader and not with Adobe Acrobat 6. Now I have edit the registry on the MSI-File with the WiseInstaller on following keys:
I delete all the HKEY_CLASSES_ROOT entry´s that contains the CLASSID from the Adobe Acrobat 6 because the CLASSID from the Acrobat Reader are the same and still there on every Client PC.
The following things happend now:
I install the Acrobat Reader and checked the registry keys. All registry keys are there and contains the correct exe File to start Acrobat Reader when click a PDF-File. After i install the Adobe Acrobat 6 with the MSI-File that i have edit, all registry keys are changed or overwritten with the Adobe Acrobat 6 settings and PDF-Files are open it with Adobe Acrobat 6.
I did not understand this, because i have delete the registry keys in the MSI-File. There must be something more information in the MSI File that correct the missing keys automatically and overwrite so the correct existing keys from the Acrobat Reader...........

Have anybody an Idea ?????

0 Comments   [ - ] Hide 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.
Answer this question or Comment on this question for clarity


I was in the same boat so what I did is remove the PDF file extention from the Acrobat MSI. I am assuming that you are advertising file extensions. The Acrobat application was redeployed and then I make a logon script solution. The logon script checked to see if it ran then if not inject the registry entries to have a PDF open with Acrobat Reader. The reason I did a logon script solution is because we were deploying Acrobat as a per-user install via active directory and we had to make sure every profile got fixed after the fact. So things might be more simple if your MSIs are not in production yet.
Answered 09/17/2004 by: kkaminsk
Ninth Degree Black Belt

Please log in to comment
Hallo kkaminsk,
thank you for your answer.
But where on the MSI-File did you remove the file extansions ???
hope you give me a second answer.....

Answered 09/20/2004 by: littlerambo
Senior Yellow Belt

Please log in to comment