·         I deploy java with SCCM 2007 I use a TS and have a simple package created and use an .mst file created with Orca. Above that nothing fancy. I use oracles/Java's patch in place method.  I recently level set all users to the same version and we are clean in that respect since 7u51. 

·         When I use SCCM to deploy any version the registry populates with a list of version for 7u51, 7u55, and the current 7u65.  [HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Runtime Environment] 

·         If I install it manually using just the msi I do not get these errant entries.  I removed the .mst  file from the sccm package and it still adds the errant entries.

·         I can GPO the removal of the reg entries but would rather get to the root cause.  The only issue they really cause is that should you check the java version it reports the correct and latest one, but also indicates the presence of these older version which are actually not installed.

·         If I use a newly imaged machine that has not even seen a prior version it still populates the "flag" for 7u51 and 7u55....

         Any ideas how/where these reg entries are coming from?






4 Comments   [ + ] Show Comments


  • Enable verbose Windows Installer logging on a guinea pig machine. That'll tell you, for example, what the source folder is. You may be able to work backwards from there.

    My other thought is...is there possibly a GPO-deployed package which has the scope of 'Authenticated Users', i.e. every machine?
  • Thanks... I'll try the logging. Sadly I was not even aware of its existence.
    We don't use GPO's for package deployment and I am a little befuddled as to why it only happens via SCCM not the manual MSI stand-alone install. Obviously SCCM is at play here
  • I tried to figure out the syntax to do this from the cmd line as I do not have that reg entry in my winows 7 (64) enterprise sp.1 I'd take the wildcard "gimme everything" option but I'm doing something wrong
    MSIEXEC "/l "*" /log Javalogfile.txt" "jre1.7.0_65.msi" TRANSFORMS="Java7u65.mst"

    Should you kindly respond I may not as I need to be out for two days. jm
  • Try this.
    Msiexec /i jre1.7.0_65.msi TRANSFORMS=Java7u65.mst /l*v %locationoflogfile%\Javalogfile.txt
Please log in to comment



Almost certainly this is by design.

The Java runtime 6.xx series would install a bunch of registry keys going back through every Java version to 1.x. This happened on first running the browser after installation but as it slowed the browser startup it was later done a different way.  I suspect something similar is happening with Java runtime series 7 - it will be some form of backward compatibility even though you don't have the older versions present.

Answered 08/04/2014 by: EdT
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity