Oracle Application Server 10.1.2 with Webutil 1.0.6 using JRE 1.6.0

At this moment we are investigating the behavior of forms related problem where webutil won’t start off a new window in which it display’s generated output.
The OAS version is 10.1.2.3 where webutil is automatically upgraded to 1.0.6 (see more) .
Together with this upgrade a switch is made to use Sun Java JRE instead of Oracle Jinitiator.
After this we discovered that the pop-up would show when using JRE 1.6.0_12 and upwards, where any lower version than JRE 1.6.0_12 would fail to show the generated content on IE 6, 7, 8 on XP, Vista and Windows 7.

To update all 1000 clients in our network easily , we wrote a simple script to at least update our clients in silent mode to patch 1.6.0_17. ( Users that run a newer version will have 2 version on there system, we are aware of this )
Patch 17 is chosen for some other issues regarding newer versions and third party client applications.

This script can be used to run in a log-on procedure and executed for a specific group.

:Working versions but uninstall anyways

:Uninstall Java SE RunTime Ver 1.6.0_16
msiexec /x  {26A24AE4-039D-4CA4-87B4-2F83216016FF} /norestart /qb-!

:Uninstall Java SE RunTime Ver 1.6.0_15
 msiexec /x {26A24AE4-039D-4CA4-87B4-2F83216015F0}/norestart /qb-!

:Uninstall Java SE RunTime Ver 1.6.0_14
msiexec /x {26A24AE4-039D-4CA4-87B4-2F83216014F0}/norestart /qb-!

:Uninstall Java SE RunTime Ver 1.6.0_13
msiexec /x {26A24AE4-039D-4CA4-87B4-2F83216013F0}/norestart /qb-!

:Uninstall Java SE RunTime Ver 1.6.0_12
msiexec /x {26A24AE4-039D-4CA4-87B4-2F83216012F0} /norestart /qb-!

:Not Working versions so uninstall

:Uninstall Java SE RunTime Ver 1.6.0_11
msiexec /qn /x {26A24AE4-039D-4CA4-87B4-2F83216011F0} /norestart /qb-!

:Uninstall Java SE RunTime Ver 1.6.0_10
msiexec /qn /x {26A24AE4-039D-4CA4-87B4-2F83216010F0} /norestart /qb-!

:Uninstall Java SE RunTime Ver 1.6.0_07
msiexec /qn /x {3248F0A8-6813-11D6-A77B-00B0D0160070} /norestart /qb-!

:Uninstall Java SE RunTime Ver 1.6.0_05
msiexec /qn /x {3248F0A8-6813-11D6-A77B-00B0D0160050} /norestart /qb-!

:Uninstall Java SE RunTime Ver 1.6.0_03
msiexec /qn /x {3248F0A8-6813-11D6-A77B-00B0D0160030} /norestart /qb-!

:Uninstall Java SE RunTime Ver 1.6.0_02
msiexec /qn /x {3248F0A8-6813-11D6-A77B-00B0D0160020} /norestart /qb-!

:Uninstall Java SE RunTime Ver 1.6.0_01
msiexec /qn /x {3248F0A8-6813-11D6-A77B-00B0D0160010} /norestart /qb-!

C:Tempjre-6u17-windows-i586.exe /s ADDLOCAL=jrecore MOZILLA=1

Bare in mind that the jre-6u17-windows-i586.exe file needs to be available in de C:Temp on the client.

Normally this pushing method could be controlled / forced from the OAS itself, however , Sun Java decided to change this.
Background information ( metalink note 747227.1 )

“Highest Version of JRE is Used no Matter What is Specified in the Formsweb.cfg”

“In releases prior to JRE 5.0 Update 6, you could specify exactly which JRE release to deploy with
a Java applet.

As of JRE 5.0 Update 6, you can no longer specify the exact JRE release due to the potential
misuse of static versioning. Instead, all Java applets are run using the latest version of the JRE
software that is installed on the system. Note that this new behavior will not change if, after
installing JRE 5.0 Update 6 or a later release, you then install an earlier JRE release. ”