We are in the process of upgrading our Win7 master image and currently deployed images from JRE 1.6.0_31 to 1.6.0_38 (can't move to v7 yet).
I am deploying Java JRE 1.6.0_38 using the following CMD line. The variables listed are defined earlier in the CMD file.
:: Install Java JRE 1.6.0_38
%SRCDIR%\%SRCEX% /s INSTALLDIR=\"%INSTDIR%\" STATIC=1 JAVAUPDATE=0 JU=0 UPDATECHECK=0 AUTOUPDATECHECK=0 /L %JREILOG%
JRE seems to install correctly, however as part of the post-install verification process that I perform before packaging for deployment, I noticed that the following registry string is still showing *1.6.0_31* (even after a reboot).
Everything else in the registry, the Java CPL etc... is displaying the correct version. The correct version is also displayed when checking the version via http://javatester.org/version.html.
Shouldn't the Java6FamilyVersion string update to reflect the newer version (1.6.0_38)?
I can of course manually adjust the value in the script, but I am not sure if the value listed is by design and changing it will break something. If the Data value is in fact supposed to reflect the new version, that seems to indicate a bug with the installer.