Deploying Java updates

  • Thread starter Thread starter PoD
  • Start date Start date

PoD

PoD

PoD

Associate
Joined
8 May 2004
Posts
1,244
So on my companies domain I have everything automated to roll out nicely via GPO's, but the one issue I have is with Java.

Applications are locked to install/update for the standard user and I have WSUS, WDS and MDT, along with using GPO's, but don't haven't got SCCM as of yet.


How do you currently roll out updates to Java?
 
Not a very big network by all means, but I update my GPO with the latest Java MSI, and then add the old Java version to my uninstall, start up script which removes the old version silently.

The only annoying thing I had to do was go around a handful of PCs to check which versions of Java were on them, in total, there was about 8 different versions (old person left it in a bit of a mess).

Sorry if I misunderstood your original post!
 
Java is truly the work of Satan, but there are a few tricks which help...

The MSIEXEC uninstall GUID is identical for all versions of Java 7 (and Java 8 but a slightly different GUID) apart from the major and minor version numbers, and the processor architecture. For example:

REM Uninstall Java JRE 7u75 x86
MSIEXEC.EXE /X {26A24AE4-039D-4CA4-87B4-2F03217075FF} /QN /NORESTART
REM Uninstall Java JRE 7u75 X64
MSIEXEC.EXE /X {26A24AE4-039D-4CA4-87B4-2F06417075FF} /QN /NORESTART

The last part of the GUID refers to the processor architecture (32 or 64) and these are for Java 7 Update 75. Thus for Java 7 Update 67 they would be:

REM Uninstall Java JRE 7u67 x86
MSIEXEC.EXE /X {26A24AE4-039D-4CA4-87B4-2F03217067FF} /QN /NORESTART
REM Uninstall Java JRE 7u67 X64
MSIEXEC.EXE /X {26A24AE4-039D-4CA4-87B4-2F06417067FF} /QN /NORESTART
 
You must log in or register to reply here.
Back
Top Bottom