Help Center

Follow

Java Collections

With all the recent press about the 0 Day vulnerability affecting Java 7 Updates 1 - 6 we thought it would be nice to provide some useful Collections and Reports that you can import.

Note that importing Reports requires Pro Mode.

Extract the attached Inventory-Java.zip file. From PDQ Inventory select File > Import. 

Here is a screenshot of the Java Collections provided. Please make sure you have recently scanned your systems.

Collections-Java-20120830.png

If you want to deploy the latest version of Java (at this writing it is Java 7 Update 7) you can download the Installer from the PDQ Deploy Installer Library. You can then deploy the latest version to your "All Systems with Java (JRE) 7 Missing Latest Update" collection.

 

Here is a screenshot of the three Java reports (Must have Pro mode to import these)

Reports-Java-20120830.png

 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

6 Comments

  • 0

    Hello Shane,

    is there another way to get the right result under "Java less than version 7" ? We know that the result is right, but only on the half way. Because your pdq installer for Java 7 Update 7 doesn´t uninstall or upgrade the installed java 6 version. And we have right now the problem that we have both version installed on our machines. We can only do now a manually uninstall of the old version 6 of java on our machine. Only after that we get a right result of the scanned workstation with Java 7. Normaly your installer need to do a uninstall of all installed java version before the new version will be installed. Maybe this is a adobe installer problem !?

  • 0

    Hi Andreas,

    Yes, by default Java only upgrades earlier versions within the same Major version. Java 7 Update 7 will remove Java 7 Update 6. It will not remove pre-version 7 of Java.

    Did you try uninstalling Java 6 via PDQ Inventory? See if that works for you. If it does, them you can simply create a new Installer which includes a Command Step. The command to run would be the Uninstall string for Java. Something like:

    MsiExec.exe /qn /X{26A24AE4-039D-4CA4-87B4-2F83216031FF}

    You could also edit the existing Java 7 Update 7 Installer by placing the Command step before the 7 is updated. Then it would remove Java 6. Just make sure to uncheck the Stop Deployment If This Step Fails because this would fail if Java 6 didn't exist. (See attached image)

  • 0

    Love the Inventory reports and collections, but have two questions.  Number 1 - I accidentally imported this collection twice, including all the reports.  Where can I go to remove the extra copies of the reports I now see?  Number 2 - I know that the command line is available to uninstall older versions of Java through Inventory and Deploy.  Is there a way to get ALL of the command lines for older versions, even if we don't have them installed to create an ultimate Java uninstaller?  Obviously a user would have to use caution and make sure to remove certain versions from the Uninstaller Package so they don't adversely affect older programs reliant on older versions of Java.

  • 0

    To remove previous java versions, you have to use a batch

    jre-uninstall.cmd

    for /f %%a in (jre-uninstall-list.txt) do MsiExec.exe /uninstall %%a /passive /quiet

    jre-uninstall-list.txt

    see attachment

    the jre-uninstall.cmd itterates trough the jre-uninstall-list.txt and executes the uninstallation on every ID.

  • 0

    That is a great list.  I am working on this project for about 90 sites and one concern is making sure that the people I'm sending this to have the ability to go in and "keep" a version of java that they need for an older program so they really need to see visually a way to identify the version in the list.  I know how to read the code at the end and decipher the version, but my original plan was to take all of these and build an PDQ Deploy uninstaller package that eventually I could export out and they could import and then edit.  The one I did for my site only included the versions of Java that I showed on scans and I set the command lines to run, but not fail and stop the job if it didn't work or run.  I would effectively be able to uninstall every old version of Java in one foul swoop thereby eliminating security risks from older versions being installed.

  • 0

    As I said, the batch iterates trough the list and does not care if the version exists or not. If it exists the uninstall is silently executed.

    I assume that pople who work with PDQ Inventory and PDQ Deploy should have the knowledge what is happening and how to identify the package.

    For those who are reading this a example:

    since the installer has been last time changed, the uninstall ID has the following format.

    {26A24AE4-039D-4CA4-87B4-2F8321*6010FF} < the marked characters imply that ita JRE version 6u10. So

    {26A24AE4-039D-4CA4-87B4-2F8321
    7008*FF} is JRE 7u8

Article is closed for comments.