Hi guys - just been handed Adobe Reader 8 to 'troubleshoot'..

It has been deployed to various machines for a while now and it seems that the update mechanism has not been removed.
The usual menu item to force an update is missing so the previous packager (not packaged by myself) has made some attempt to stop updates.. I've read the Package Knowledgebase about disabling updates but my question is not dealt with there... so here goes - is there any way to manually trigger an update?

I reckon if I can somehow trigger the Adobe upate when I want, then at least I'll have a test to make sure whatever steps I take to disable the update actually work or not.

The only thing the previous packager has done is to add a modified 'AdobeUpdaterPrefs.dat' to
C:\Documents and Settings\username\Local Settings\Application Data\Adobe\Updater5\
with the field <AutoCheck>1</AutoCheck> changed to <AutoCheck>0</AutoCheck>
(I thought it was a registry setting to remove the menu item from within Adobe but as far as I can see no special registry modifications have been made to do this - strange)

I can go ahead and throw the whole of the reg. keys and removal of Add-ins detailed in the knowledgebase into the mst, but I I'd like to test to see if the update has been stopped i.e test what should have been tested in the first place.

Any ideas?
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


Decided to reply to myself here in case some one else is wondering about the same thing.

The package I was looking at had already been modified by a packager and Auto Updates turned off - or so it seemed.
As it is a core build application it came as a surprise to see it prompt users to install available updates over the last few days.
I asked if I could trigger an 'update' on demand so that I could test if my preventative measures I introduced would work.

Well the previous packager included a javascript file in the installation directory (javascript) folder - this is picked up and run by the app at each launch.
This script disables specified buttons. By commenting out some code in this script I re-enabled the Update button in the Help menu. This button was previously unavailable and was the packagers attempt at disabling the update facility. In fact it only hides the button - nothing else.
This done I could force an update when I wanted to test.

So i followed the steps detailed in the package knowledgebase and used the update button to test...all good .. no more updates launching.
Set the button back to hidden..Job done.

Answered 10/30/2007 by: sh79
Senior Yellow Belt

Please log in to comment