WSUS Package Publisher: Deploy updates Java [Quick Guide]
after seeing the WSUS Package Publisher Setup (WPP) and Flash Player updates deployment , we will look at a another software very often updated, and where the principle of integration of WSUS Package Publisher is different than Flash Player.
This is particularly due to the fact that since the latest versions of Java, the MSI Setup file is no longer included and it should be now to cope with the EXE format Setup file – thanks Oracle.
We’ll see how to deploy updates with WSUS Package Publisher Java , with the 8 101 Update Java version which is the last exit to where I write these lines.
II. download Java
To download Java: Java offline
take the 32-bit version or 64-bit according to your needs, awaits a 50 MB download. Then store this good EXE warm within your library of updated, for example:
now for the creation of the update.
III. create a new update
open WSUS Package Publisher and create a new update:
specify the path to the EXE in Java file and continue:
then, he will have to fill in the Publisher, product name, etc… Because as it is not an MSI, WPP is not able to extract this information from the installation package, unlike the MSI that is designed to precisely provide information.
Also indicate ‘0’ as a return to the ‘Success’ result code
In the field “ command-line ‘, indicate this:
AUTO_UPDATE = Disable INSTALL_SILENT = Enable REBOOT = Disable REMOVEOUTOFDATEJRES = 1
these options in order to disable the automatic update to Java (which will prevent the icon in the taskbar that there is an update, and do not pollute the user), activate silent installation. do not restart and uninstall older versions of Java on the machine to let only the last.
That the characteristics of our package.
Now we have to add a rule to the package level (via ‘ edit this group “‘”) that will allow to check if this version Java is already installed on the machine or not. To do this, let’s look at whether or not a software on the machine with the Product Code for the version of Java is already installed.
We therefore creates a “Product Msi installed” rule with the following values:
here is the Product Code of Java 8 Update 101 (only this version):
- 32-bit: 26a24ae4-039d – 4ca 4-87 b 4 – 2f 32 1 8 0 101 f0
- 64-bit: 26a24ae4-039d – 4ca 4-87 b 4 – 2f 64 1 8 0 101 f0
you will get this :
note: the product code versions of Java are always constructed in the same way and contain the version number, I put in bold in the previously assigned numbers the values corresponding to the Java Update 101 8.
Continue and for the rule that lets you know if it is installed, we will say: it is installable if it is not installed. Let’s do this by the same rule as in the previous step, but reversing through the option provided for this purpose. We’ll keep the same product code and the same type of rule, but we’re going to reverse the condition:
you get this:
basically, the first rule lets you know whether it is installed or not, and with the second he told it is installable if it is not installed. Of many other rules can be created, for example, for those who deploy the 64-bit version you can add a second rule that the update is installable if the PC is 64-bit.
It remains more to continue and wait while the generation of the installation package:
the last step is to approve the update on our allocation groups, as we did in the tutorial on the Flash Player update:
that is, I leave you the pleasure of testing the functioning on a guest post now 😉
Note : I met a case quite surprising at a client, where I could not deploy the Java via WSUS Package Publisher update on certain positions, where they had an updated Java updated previously by GPO. Strange behavior.