The new application model in SCCM 2012 quickly became one of my favorite features, and has remained so across every deployment I work on. With its comparatively advanced deployment and detection methods, it is extremely useful for applications of all sorts, even those that require frequent updates.
In SCCM 2007, everytime a new version of Java or Adobe Reader came out, you’d have to create a new package and advertisement, and then turn around and update all of your task sequences. This was at best tedious. Sure, there are tools like SCUG that can help with this, but they are not always available to all organizations, and they had their own problems and limitations.
By making use of the new application model, administrators can much more easily keep up on these updates.
Begin by downloading the bits: http://java.com/en/download/manual.jsp
The 64-bit version is for 64-bit browsers. So you’ll probably still need the 32-bit version for 64-bit Windows.
Get the MSI:
Launch the executable. Once the splash screen appears, the files will have been extracted. Navigate, for the 32-bit version to
and for the 64-bit version to
Copy the files to your source location for SCCM packages.
Make the transform:
Next, use Orca to edit any custom settings you need. Some of the most common ones can be found under the Property table. In this example, I’ve changed AUTOUPDATECHECK, JAVAUPDATE, and JU all to 0 to prevent any kind of updating. I’ll also change IEEXPLORER and MOZILLA to 1 to enable java in browsers.
You may have other changes to make, such as a custom install location, all of those kinds of changes can be made into a transform with Orca. Once finished, I then save the custom transform in the application source directory and create it in SCCM.
Be sure to edit the installation method to include your new custom transform file:
msiexec /i “jre1.7.0_17.msi” TRANSFORMS=custom.mst /q
Now, you can set this application to supersede the previous version of Java you are using. Or, if this is the first version of Java your placing into SCCM, then you can use this method to keep your Java clients up to date. When a new version comes out, build it this way and have it supersede the old version. You’re now one your way to automating that much more of your environment.
You may also want to look into removing old versions of Java if you’re trying to get old versions out of your environment.