Java Runtime Environment Version 6.0 Update 27

op .

Gebruikerswaardering: 5 / 5

Ster actiefSter actiefSter actiefSter actiefSter actief

Oracle has released "Java Runtime Environment Version 6.0 Update 27".

This update release contains important enhancements for Java applications:

  • Improved performance and stability
  • Certification for Firefox 5

Java SE 6u27 contains Olson time zone data version 2011g. For more information, refer to Timezone Data Versions in the JRE Software .


First of all download and run either jre-6u27-windows-i586-s.exe for Windows 7/ XP 32-bit or jre-6u27-windows-x64.exe for Windows 7 / XP 64-bit. If you use 32-bit and 64-bit browsers interchangeably, you will need to install both 32-bit and 64-bit Java in order to have the Java plug-in for both browsers. These installers are available in the Java download section of Oracle's Java website.

When the License Agreement screen pops up, look in the "c:\Documents and Settings\<username>\Local Settings\Application Data\Sun\Java\jre1.6.0_27 directory" when you're using Windows XP or "C:\Users\<username>\AppData\LocalLow\Sun\Java\jre1.6.0_27\" when your're using Windows 7. In that directory you will find the 'jre1.6.0_27.msi' and a file. The jre1.6.0_26.msi file is the one we can use to deploy "Java Runtime Environment Version 6.0 Update 26" by using MSI technology. Don't forget

Start up the AdminStudio Tuner and create a response transform file. It's as simple as that if you want to do a default deployment. For an advanced deployment you can further tweak you J2RE configuration two ways:

  • by changing the 'Setup Properties'
  • by changing registry settings

The result is the same. You can change some basic 'Setup Properties' in the Tuner:

  • AUTOUPDATECHECK - Java Update mechanism - on {1} or off {0}
  • EULA - popup the EULA when you first start a Java applet - on {1} or off {0}
  • IEXPLORER -  indicates that the Plug-in should be registered with the Internet Explorer browser - on {1} or off {0}
  • JAVAUPDATE - indicates that the Java Update feature should be disabled (the Update tab in the Java Plug-in Control Panel will not appear) - on {1} or off {0}
  • MOZILLA -  indicates that the Plug-in should be registered with Mozilla 1.1 and later browsers - on {1} or off {0}
  • SYSTRAY - System Tray Icon on {1} or off {0}

... but you can also collect the JRE's registry settings to tweak the JRE a little more.

Launch the "Java Control Panel" (available in c:\Program Files\Java\jre6\bin\javacpl.exe). Most settings you will change by using this utility will then be stored in the registry in [HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft]. Some examples:

  • Click on the "Update" tab. If you uncheck the "Check for Update Automatically" you will shutdown the Java Update mechanism. This may be wise, because we want to deploy newer versions by using ZENworks and not automatically by using the Java Update mechanism.

  • If you want to disable the 'Update' tab, then use this registry setting to enable (00000001) or disable it (00000000):

    [HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Update\Policy]

  • Click on the "Advanced" tab. If you open up the "Miscellaneous" node by clicking on the + sign, you can uncheck "Place Java icon in system tray". Which just does what is says. Now it has become more difficult for users to fiddle around with the J2RE configuration. If you change this setting, this registry setting is changed:

    [HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Plug-in\1.6.0_27]


Some settings however are stored somewhere else. Some examples:

  • Click on the "General" tab. Click on 'Network Settings'. The settings you configure here are stored in:

    C:\Documents and Settings\%USERNAME%\Application Data\Sun\Java\Deployment\

    This '' file is used for storing and retrieving deployment configuration properties in the Java Control Panel. They are also used for customizing runtime behavior for both Java Plug-in and Java Web Start. There is always a User-Level file. Its location, which is non-configurable, is described here. There may also be an (optional) System-Level file. If it exists, its location is determined by a System Administrator through the deployment.config file as described here.