Using SCCM 2007 / 2012 to deploy Java Runtime Engine Updates

Original article can be found here: http://seth.killey.me/?p=288

Here’s some instructions for updating staff computers to the latest version of JRE using Microsoft System Center Configuration Manager 2007 / 2012. These steps will allow you to silently deploy JRE

LAST TESTED: JRE 7.55 on Windows 7

For info on upgrading from version 6 to version 7

1) If Java is already installed on your test computer, first uninstall all versions of Java
2) Download the latest version of JRE http://www.java.com
3) You’ll get an .exe file, but you can get the .msi file by launching the .exe.  When the installation wizard starts, click next to start the download and when the program starts the actual installation navigate to the LocalAppData folder.  On Windows 7 this is located at C:\Users\<user>\AppData\LocalLow\Sun\Java\jre1.7.0_<version>\
4) Copy the .msi file to your desktop before installation completes, otherwise the file will be automatically removed
5) On your SCCM server setup your software distribution package according to your environment.  As far as program parameters, make sure you specify the /qn switch for a quiet unattended installation.  If you also wish to suppress reboots you can specify /qn REBOOT=ReallySuppress

Going forward you can easily refresh the package as new versions are released in SCCM.

  • First thing to check is if the advertisement was created with a mandatory schedule which hasn’t expired yet.
  • For SCCM 2007, select the package and launch the Manage Distribution Points wizard, select the option to Update Distribution Points and complete the wizard. Verify if the new version of the package and the updated files have reached the distribution point. On SCCM 2012, right-click on the package and choose “Update Distribution Points”.
  • For SCCM 2007, now go to the advertisement and click the action to Rerun the advertisement.  On SCCM 2012, right-click on package and click “Deploy” to create a new deployment task.

* It would probably be easiest to first rename the .msi file to something generic like JRE.msi so when you update the distribution point you can just overwrite the existing .msi.  Otherwise, make sure to update the program to point to the newest .msi file before updating the distribution point.