Java 7 Update 45 Install Notes:
First install the standard Java x86 & x64 packages from Sun.
Obtain Cab and MSI from Vista/7 Directory: C:\Users\<yourusername>\AppData\LocalLow\Sun\Java (XP: C:\Documents and Settings\username\Local Settings\Application Data\Sun\Java)
The jre folders therein contain the uncompressed installers; your results may be undesirable if you attempt to uncompress the jre executable installer with 7zip or winRAR and then try to use those installers to create a package; just something I ran into a
while back, FYI.
I use the .cab / .msi because of various errors and problems I’ve encountered using the EXEs; Sun recommends using the MSI and cab like I do. Save yourself the headache and skip the EXEs; I encounter new issues with each release.
Next, get the install strings for the java release you're deploying; I have listed them for convenience, but you can see how I found them below.
7u45 updater string: (Unchanged since 7u21)
You can find these by using the WSUS Package Publisher and going to tools > MSI Reader, loading the MSI, and going to the property table. The install string is labeled "ProductCode".
Now to create the package!
I used the guide as a template, (https://www.codeplex.com/Download?ProjectName=WsusPackagePublisher&DownloadId=691788
) so you may need to read
that to fill in some gaps, but in summary here's how I built my x86 update:
A. Start Custom Update from WPP
- Define variable “Return Code” as an integer as in guide
- Stop Service JavaQuickStarterService
- Allow to execute a file with following strings:
Path to file:
/i jre1.7.0_45.msi /quiet /norestart AUTOUPDATECHECK=0 IEXPLORER=1 JAVAUPDATE=0 JU=0
Kill process after 15 minutes, link to "Return Code"
Add Exit code, link to "Return Code."
- You are now done with custom update XML generator, continue on.
B. Add .CAB and .MSI files to the package; Mark it as an update - Critical update.
I mostly followed the guide from this point on, except for my install rules; for “already installed”, I used the guide, but for “installable”, I set the x86 java package to install on x86 & x64 machines (since most browsers are 32-bit.) I used the not equal
to Itanium CPU type rule to allow for x86 and x64 installation.
On the 64-bit package, for “installable” values, I set the x64 architecture type and the <not><MSI> value.
Also, the x64 installer doesn't have an updater package anymore; for more information in what command line options java's MSI accepts, see the slightly outdated article from Sun:
To test, approve for WSUS test group. If retrying a package, or flushing a deleted test package on a test machine, you can stop the Windows Update service, delete “datastore” and “download” folder contents from local cache in C:\Windows\SoftwareDistribution,
then check for Windows Updates. (Leave the folders, just delete the contents.)
I hope you find these tips helpful; your mileage may vary. Credit: The people at WSUS Package Publisher who wrote that excellent documentation. I never would have gotten this package working right without the Documentation section.