COMPLETELY disabling updates in JRE1.5.0 1

[cameramonkey]

We have a new application that absolutely requires a specific, predetermined version of Java to run. Updates cannot be run or it may break the functionality.

We can specify any version of the JRE we want, but once we go to that version, we absolutely cannot change.

We have found a way to push the specific version to the desktop and prevent the updater from running automatically. However the first time the user initiates the Java app, the system prompts the user if they want to schedule update checks. We cannot count on our users to select "never update".

Is there a way to completely prevent the update from activating? I tried renaming \bin\jucheck.exe and \bin\jusched.exe so that they couldnt run, but jusched would magically appear in the process list if the user selects check for updates.

Can it be COMPLETELY disabled so that there is no possible way our users can turn on updates? The only way they should be able to update is by manually downloading the new version from sun.

 

[manarth]

We have a new application that absolutely requires a specific, predetermined version of Java to run. Updates cannot be run or it may break the functionality.

Ouch. One of the most portable code languages in the world, and people do this to it. I find it hard to believe that there's a valid reason for this (beyond incompetence).


Can you clarify what platform your users are on? (Windows, *nix...)

---
Marcus
better questions get better answers - faq581-3339
accessible web design - zioncore.com

 

[cameramonkey]

I agree. One of the deployment specialists claims she has run various versions with no problems. However, the developers are telling us that it has to be a specific version. Chances are its a CYA because we are dealing with payroll software, but I will side with the developers on this one.

Our client environment is 100% windows xp.

 

[cameramonkey]

One other option is that as a last resort I can blackhole the sun update servers that the update software looks to in the event that a user ignores our instructions and enables java updates. Its not pretty or perfect, but since I now have less than 2 weeks to figure this out...

Anyone know what that server address is off hand?

 

[cameramonkey]

answered it myself...

A quick break down of what each does in this MST (based on observations):

IEXPLORER=1 (default=0)
- This selects the IE plugin

JAVAUPDATE=0 (default=1)
- This turns off part of the JavaUpdate

AUTOUPDATECHECK=0 (default=1)
- This turns off part

JU=0 (default=1)
- I'm pretty sure this is the property everyone hated. This is the new property in Update 5 and 6 that turns on that update prompt and leaves JavaUpdate on even if the JAVAUPDATE property is set to 0
- If were trying to figure out how to get rid of "PromptAutoUpdateCheck" under [HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Update\Policy] to avoid the first run prompt, setting JU=0 takes care of this.

MOZILLA=1 (default=0)
- This selects the Netscape/Mozilla plugin

SYSTRAY=0 (default=1)
- This turns off the system tray icon when java applets are active

WEBSTARTICON=0 (default=1)
- This disables the creation of the web start link on the desktop (I think, always had this off)