Wednesday, June 15, 2011

Using SCCM 2007 to deploy Java Runtime Engine Updates

Here’s some instructions for updating staff computers to the latest version of JRE using Microsoft System Center Configuration Manager 2007. These steps will allow you to silently deploy JRE and then I’ll cover how to disable automatic updates so users aren’t prompted when a new version is available.

1) First download the latest version of JRE
2) 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.6.0_<version>\
3) Copy the .msi file to your desktop before installation completes, otherwise the file will be automatically removed
4) 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
5) To disable Java updates in registry, browse to HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Update\Policy and create a new DWORD value called EnableJavaUpdate with a value of 0.  You should have something like this. 

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.
  • 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.
  • Now go to the advertisement and click the action to Rerun the advertisement.

* 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.


No comments:

Post a Comment