It’s that time again. You guessed it, another fun-filled Tuesday with no less than a new Java update. Or, if you’re getting tired of checking for (or being surprised by…) another critical Java update. Maybe it’s time to schedule an Auto Deployment for Java.
Automate a Silent Install for Java 8
Using the Package Library in PDQ Deploy (download it free here) you can quickly get access to ready-to-deploy silently installing packages. The Package Library has the Java 8 update 71, but not update 72. Oracle recommends update 71 for most users (read more here). If you find yourself needing Java 8 update 72, you can still get it deployed by building your own package.
Here, you’ll see how you can use the Java package in an Auto Deployment to stay up-to-date on Java in just four steps. Get an Enterprise trial license to access the complete library and use the Auto Deployment feature.
- Select the Java 8 Package
- Click Add Auto Deployment to Schedule or Set Deployment Trigger
- Choose Targets
- Review Options and click OK
Go to the Package Library and select the Java 8 package. If you’d like there is also a 64-bit version available. You also might notice a Java 8 – ALTERNATE package. Don’t use this package on your machines unless you are experiencing errors when deploying. The alternate is there to help resolve issues such as
Java error 1603.
Select target computers by either adding them in or linking to them. Using
Link To makes it easy to get your deployments to the right computers. If you have
PDQ Inventory Enterprise mode you can link to a collection from the Collection Library that already has computers sorted by old vs. new Java versions. (Scroll down to read more on using the Collection Library.)
It’s always good to check your options before deploying. Below are the defaults (generally recommended) but you can also set up an email notification so you know when your deployment is complete. You may also find it helpful to use the Retry Queue if some of your computers are offline at the time of the deployment.
After clicking OK, you’re done. PDQ Deploy will check for a new version for you on the schedule you set (see schedule tab), and get that new version deployed to the selected targets after the approval period. (Change your approval setting under File > Preference > Package Library.) You can also run your schedule whenever you’d like by selecting the schedule and clicking Start Schedule in the upper right panel.
Using the Collection Library
Linking your Auto Deployment to a PDQ Inventory collection is a great way to target machines that specifically need the update. You can build your own collections in PDQ Inventory, or save yourself a little time with pre-built and regularly updated collections.
Yes, there is a collection that sorts your computers by Java update status. Collections are updated the same time that new PDQ packages are created. This means that you can be sure when your deployment is kicked off that those computers with out-of-date Java installations will be deployed to and updated.
Note: PDQ Inventory will inventory both Java 8 updates 71 and 72 as up-to-date (new). Lower versions will be counted as out-of-date (old).
Note: If you need to customize or change settings in Java’s Control Panel, please refer to this post on managing Java’s control panel and exception site list.