Java 8 has been released and is, of course, available in the PDQ Deploy Package Library.
While there are many, many changes to the JRE, not a lot has changed with how it is deployed. We still call the Java MSI file (jre1.8.0.msi) and we modify some of the default properties. We have removed, at this point, many of the steps found in Java 7 packages. It appears that Java is actually *gasp* honoring the properties which disable Auto Update therefore the additional steps used previously appear to be unnecessary for the 32-bit Java. Here is the data that we provide in the Parameters field.
JU=0 JAVAUPDATE=0 AUTOUPDATECHECK=0 RebootYesNo=No WEB_JAVA=1
The first three parameters are used to disable Java updating or even checking for updates. The RebootYesNo=No obviously suppresses rebooting and WEB_JAVA=1 instructs the installation to register Java with the installed browsers (IE, Chrome, Firefox, Opera, etc.)
Deploying Java to all of your computers is impressively easy when you use PDQ Deploy. The Java 8 package is available for Pro Mode and Enterprise. You can see a video of a deployment below.
Here are a few things that you should know.
- Don’t deploy Java 8 if your end-users don’t need it.
- Deploy the 32-bit version of Java. This is very important. Just because a target computer runs 64-bit Windows does not necessarily mean it needs the 64-bit Java. The vast majority of browsers are 32-bit (Chrome, Firefox, Opera) or run in 32-bit mode (Internet Explorer). This means that these browsers will NOT be able to utilize a 64-bit Java. I can’t stress this point enough without resorting to my usual profanity-laced method of communication. If your users run 64-bit Java apps then, by all means, deploy the 64-bit Java.
- Java 8 is its own family. Other Java JRE families (Java 7, Java 6, etc.) will NOT get removed when you install Java 8. There are Java Uninstall packages available in the Package Library if you want to uninstall earlier Java versions.
- Unless you change the default behavior Java 8 will be registered as the preferred JRE for your browsers. Many Java applets in the wild were written for Java 7, Java 6 and, in some unbelievably pathetic cases of overt deniability, Java 5. This means that they may not work with Java 8. Remember, Java 8 is effectively a new-born baby. It’s wet, wrinkled, maybe a little squishy in the head and your friends won’t say it’s ugly. As it gets older it will start to fill out and you can actually make it do some chores. Keep this in mind.
We will get some other blog posts describing some advanced methods of deployment if you need them.
It’s 2 PM… where’s my Guinness?!