Customize Adobe Acrobat Reader 7.0 installation
I have some problems adjusting the Acrobat Reader 7.0 MSI to our company needs.
In order to have user profile fixup working I grouped all the HKCU files into 1 component and assigned it to a separate feature which I placed as parent of all other features.
With the advertised shortcuts, the self-healing process starts whenever a new user logs on that didn't allready have the HKCU settings in his profile, but when launching a file with the pdf extension, this doesn't seem to work. Although I added the file association to the MST.
Anyone who has some experience with this?
kr,
Tim
In order to have user profile fixup working I grouped all the HKCU files into 1 component and assigned it to a separate feature which I placed as parent of all other features.
With the advertised shortcuts, the self-healing process starts whenever a new user logs on that didn't allready have the HKCU settings in his profile, but when launching a file with the pdf extension, this doesn't seem to work. Although I added the file association to the MST.
Anyone who has some experience with this?
kr,
Tim
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
VikingLoki
19 years ago
Unfortunately that's how self healing works. The self-heal check is only peformed when the app is launched via a shortcut created by an MSI, a file association won't do it.
There are workaround tricks though. You can add a dummy executable to the msi, which does nothing but terminate. Then you create an additional shortcut within the MSI located in All Users\Startup that launches the dummy executable whenever anyone logs in. If the profile stuff is there, the dummy executable will promptly terminate. If the profile stuff isn't there, the self-heal will kick in and set up the user profile, then run the dummy executable which will promptly terminate.
There are workaround tricks though. You can add a dummy executable to the msi, which does nothing but terminate. Then you create an additional shortcut within the MSI located in All Users\Startup that launches the dummy executable whenever anyone logs in. If the profile stuff is there, the dummy executable will promptly terminate. If the profile stuff isn't there, the self-heal will kick in and set up the user profile, then run the dummy executable which will promptly terminate.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
