Java has released a new update (Java 8 update 66) which is available to silently install from the Package Library as of November 11, 2015) Yes, it’s that time again, the infamous Java quarterly release. This is (of course) a critical patch with multiple security vulnerability fixes. Not the least of which can be exploited remotely without authentication, so you’ll want to get this update out ASAP.
You can read more about these vulnerabilities here as reported by Oracle here. Let’s get these updates out to your company’s computers remotely.
PDQ Deploy packages are ready-to-deploy and built to silently install. So all that’s left is to send your deployment out to your target machines (you can select your targets from Active Directory, PDQ Inventory, Spiceworks, etc.)
Simply select the appropriate Java package and import it, then with that package selected, click the Deploy Once button, and then you’ll be taken to this screen to select your targets, settings and if you want to schedule or deploy Java right away.
There are two kinds of silently deploying packages available. The Java 8 package is the one we recommend installing first. Only use the Java 8 – ALTERNATE package if you run into errors such as the Java error 1603 or error 1618. The reason being that the ALTERNATE package also goes through the registry so it’s not something to lightly send around. It is very effective, use it if you need it. If you don’t, then don’t.
If you only have the free version of PDQ Deploy, no worries you can still get Java installed. However, silently installing Java this way can lead to more errors as the full package as available in the Package Library closes out browsers and uninstalls past versions of Java.
1. Make sure you get the offline version of Java. Online versions are smaller in size and will not silently install successfully.
2. Extract the Java MSI. The reason you want the Java MSI over the EXE is that MSIs have already defined silent parameters, which you must have for a successful deployment. If you don’t have silent parameters you could see error messages, have failed deployments or worse…
3. Now you’re ready to build your deployment package. Add the Java MSI to the Install File line, and be sure to select Include Entire Directory. Then you’ll want to add the following parameters on the parameters line to disable auto updates and machine reboots:
JU=0 JAVAUPDATE=0 AUTOUPDATECHECK=0 RebootYesNo=No
Simply save and deploy and you’re on your way.
Note: There is also a Java 8 update 66 out. This update is for commercial customers. If you do have a commerical license from Java and want to push out this update you will need to build the package yourself as it is not available in the Package Library. The Java collection in the PDQ Inventory Collection library counts both update 65 and 66 as being up-to-date.