Installing Java Silently and setting so won't check for updates later on?

[Sam_Brown]

Currently pushing out Java using SCCM and have the install command as "msiexec /i "jre1.8.0_25.msi" /qn"

 

This works well and installs with no issues on our machines however once a new version of Java comes out it will keep prompting to update Java. Are there any install switches to suppress this or group policy templates that will let me set this centrally as while we do try and keep Java up to date we can't always package up on the day a new release comes out and have complaints over the Java popup.

[sllorep]

In SCCM, I use the following:

 

msiexec /i jre1.8.0_25.msi /quiet /norestart ADDLOCAL=ALL IEXPLORER=1 NETSCAPE=1 MOZILLA=1 REBOOT=Suppress JAVAUPDATE=0

 

Hope this helps!!

 

Ash

[Sam_Brown]

Working great. Thanks.

[Arthur]

FWIW, the following link lists all of the properties that are officially supported by the JRE 8 MSIs.

 

http://docs.oracle.com/javase/8/docs/technotes/guides/install/config.html

 

The IEXPLORER=1, NETSCAPE=1 and MOZILLA=1 properties listed in Ash's post are no longer relevant. They have been replaced with WEB_JAVA=1.

 

This is what I use with SCCM.

 

msiexec /i jre1.8.0_31.msi AUTO_UPDATE=0 EULA=0 JAVAUPDATE=0 NOSTARTMENU=1 SPONSORS=0 WEB_ANALYTICS=0 WEB_JAVA=1 WEB_JAVA_SECURITY_LEVEL=H /qb

 

Currently pushing out Java using SCCM and have the install command as "msiexec /i "jre1.8.0_25.msi" /qn"

Your JRE is already out of date by the way.

 

Update 31 was released a month ago.

 

If you are deploying Update 25 your users will see a message saying the JRE expired on 20th January 2015 (or 20th February 2015 if you blocked javadl-esd-secure.oracle.com on your proxy).

 

The JRE expires whenever a new release with security vulnerability fixes becomes available. Critical patch updates, which contain security vulnerability fixes, are announced one year in advance on Critical Patch Updates, Security Alerts and Third Party Bulletin. This JRE (version 8u25) will expire with the release of the next critical patch update scheduled for January 20, 2015.

 

For systems unable to reach the Oracle Servers, a secondary mechanism expires this JRE (version 8u25) on February 20, 2015. After either condition is met (new release becoming available or expiration date reached), the JRE will provide additional warnings and reminders to users to update to the newer version. For more information, see JRE Expiration Date. (Source)

Edited February 20, 2015 by Arthur

[sllorep]

Thanks Arthur,

 

You learn something every day - I've been using mine for years and years with no problem. I'll try the newer install properties for the next release!

 

Ash.