Home > e-infrastructure, Glitches&Errors, Translation, translation-software > How to configure Java not to check for updates in the frozen computer lab

How to configure Java not to check for updates in the frozen computer lab

  1. Many applications – both web-based or standalone – in the LRC rely on Java. They currently all start Java with the autoupdater:
  2. image
  3. and may at least temporarily allow for Java versions not tested for compatibility with LRC applications
  4. which should not cause permanent problems, since the computers are frozen, but does cause client s unnecessary hassle and delays
  5. provided that
    1. the LRC applications have been tested to work with the reasonably recent version of Java in the LRC image
    2. and staying on this version for, say, a term, causes no overarching security concerns (if it does, the more recent Java version should be frozen into the underlying software image anyway, after testing for compatibility with  LRC applications).
  6. The answer how to shut out the autoupdater is likely in the Java control panel. This screenshot is from version 7.51 while we have 7.45, but likely similar image
  7. Registry keys note 32-bit and 64-bit)
    1. HKLM\SOFTWARE\JavaSoft\Java Update\Policy    EnableAutoUpdateCheck
    2. HKLM\SOFTWARE\Wow6432Node\JavaSoft\Java Update\Policy    EnableAutoUpdateCheck
    3. HKLM\SOFTWARE\JavaSoft\Java Update\Policy    EnableJavaUpdate
    4. HKLM\SOFTWARE\Wow6432Node\JavaSoft\Java Update\Policy    EnableJavaUpdate
  8. For programmatically configuring this, a quick web search finds this:
  9. deployment.expiration.check.enabled

    Boolean

    true

    Must be “true” to prompt users to update the JRE when an out-of-date JRE is found on their system. Set to “false” to suppress the prompt.

  10. This is a setting in here:  The deployment.config file is used for specifying the System-Level deployment.properties in the infrastructure. By default no deployment.config file exists; thus, no system-wide deployment.properties file exists. If deployment.config exists, it is located in one of the directories shown in the following table.
    Operating System:Windows
    Location
    • <Windows Directory>\Sun\Java\Deployment\deployment.config
    • ${deployment.java.home}\lib\deployment.config
  11. in addition, likely this should be included: “SomeKey=SomeValue, may be locked by including another key, SomeKey.locked … so that the user cannot change it”.
  12. Information is from http://docs.oracle.com/javase/7/docs/technotes/guides/jweb/index.html which may likely contain other information needed to configure JAVA in the LRC environment.
  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: