Jinitiator Packaging
Hi,
When packaging Jinitiator_8.1.18.1.6 there is an additional customization to be made that is to disable the following Web Bowser Option " Display PDF in browser" in the Adobe Acrobat Reader Application under EDIT->PREFERENCES Menu.
The MSI creatd to do the following action updates the changes in the Administrator mode but it is not reflected in the Power user mode though the application gets installed in this mode.
I tried to get a snapshot of the changes in the registry formed during this installation in the power user mode and tried to incorporate these changes in the MSI created but it seems it is not updating the keys.
Why is this so .. any other methods to resolve this isue. Plz suggest.
Regds .. !! Thanks
When packaging Jinitiator_8.1.18.1.6 there is an additional customization to be made that is to disable the following Web Bowser Option " Display PDF in browser" in the Adobe Acrobat Reader Application under EDIT->PREFERENCES Menu.
The MSI creatd to do the following action updates the changes in the Administrator mode but it is not reflected in the Power user mode though the application gets installed in this mode.
I tried to get a snapshot of the changes in the registry formed during this installation in the power user mode and tried to incorporate these changes in the MSI created but it seems it is not updating the keys.
Why is this so .. any other methods to resolve this isue. Plz suggest.
Regds .. !! Thanks
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
ab2cv
20 years ago
Could it be that the registry key in question lies in the HKCU hive? If so, then it will only be written in for each new user that logs on if the MSI detects that it is not present. You would need to make sure that the registry keys in question are the keypath for the component that installs them. Secondly, you need to find some way of triggering the self healing/advertising of the MSI package. The only way i know is through advertised shortcuts - but I don't think that JInitiator installs any by default.
Our workaround was to put a dummy shortcut in the startup shortcut folder that runs an exe in the package (but does nothing). This is enough to trigger off the auto-repair of the MSI, which then checks all the component keypaths, finds that the HKCU keys are missing and consequently writes them in.
Alan
Our workaround was to put a dummy shortcut in the startup shortcut folder that runs an exe in the package (but does nothing). This is enough to trigger off the auto-repair of the MSI, which then checks all the component keypaths, finds that the HKCU keys are missing and consequently writes them in.
Alan
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
