/build/static/layout/Breadcrumb_cap_w.png

Java 6 update 13 (or update 14) EULA prompt

Hello,

Hopefully someone can help me with my problem. I was reviewing the Package KB's for Java 6.x and I had seen a couple different methods that have been followed to suppress the EULA prompt a user gets when they go to a page with Java content for the first time.

Basically, I can't get any of the methods provided to work. A couple users recommended using the command line switchs AGREETOLICENSE=Yes" or "EULA=1" (also tried EULA=0 just for kicks).

Other users suggest extracting the .MSI from the original JRE .EXE by retrieving it from my %APPDATA% directory. However, when I do that, I find that I can't actually launch the .MSI file or modify it because it appears to be incomplete without the .CAB file.

Basically, I hate to ask, but would someone be able to walk me through this process? I've had plenty of experience building packages with snapshot type applications but repackaging is almost an entirely new game altogether.

My main goals with this package are the following:

1. Silent install through a batch file
2. Disable auto-updates
3. Disable EULA agreement prompt

I appreciate any help you guys can provide!

-Chris

0 Comments   [ + ] Show comments

Answers (4)

Posted by: turbokitty 14 years ago
6th Degree Black Belt
2
This is what I do (vbs). I'd add some error checking.

Option Explicit
Dim ObjShell, objFso, InstallCommand
Dim strKeyPath, strValueName, strValue, oReg, strComputer

Set ObjShell = Wscript.CreateObject("WScript.Shell")
Set objFso = CreateObject("Scripting.fileSystemObject")

'***INSTALL CLIENT ****************

InstallCommand = "jre-6u14-windows-i586-s.exe /qn ADDLOCAL=ALL SYSTRAY=0 EULA=0 IEXPLORER=1 JAVAUPDATE=0 MOZILLA=1 AUTOUPDATECHECK=0 JU=0 REBOOT=ReallySupress /L C:\Logfiles\java_runtime_160u14b08.log"
objShell.Run InstallCommand,,TRUE


'disable autoupdates
const HKEY_LOCAL_MACHINE = &H80000002
strComputer = "."
Set oReg=GetObject( _
"winmgmts:{impersonationLevel=impersonate}!\\" &_
strComputer & "\root\default:StdRegProv")
strKeyPath = "SOFTWARE\JavaSoft\Java Update\Policy"
strValueName = "EnableJavaUpdate"
oReg.SetDWORDValue _
HKEY_LOCAL_MACHINE,strKeyPath,strValueName,00000000
Posted by: dunnpy 14 years ago
Red Belt
1
Chris,

I've just done Java 1.6.0.14 by grabbing the MSI file and transforming it.
Details are on the Package KB.

The EULA property is:

EULA_JAVAFX_ACCEPT = yes

To disable the updates I used Sun's preferred method, using the 'deployment.properties' file

Details are linked from this post

Hope this helps,

Dunnpy
Posted by: anonymous_76053 14 years ago
Senior Yellow Belt
0
Awesome! Your script works great for me and it also seems to have helped me fix my original batch file as well.

I'm not sure why but here's what I was originally using for my install string:


Y:\java\java6u13.exe /qn Agreetolicense=Yes ADDLOCAL=ALL IEXPLORER=1 NETSCAPE6=1 MOZILLA=1 REBOOT=Suppress JAVAUPDATE=0 SYSTRAY=0 EULA=0


Here's what I'm using now:


Y:\java\java6u13.exe /qn ADDLOCAL=ALL SYSTRAY=0 EULA=0 IEXPLORER=1 JAVAUPDATE=0 MOZILLA=1 AUTOUPDATECHECK=0 JU=0 REBOOT=ReallySupress


I took my original code straight from another users post in the KB article. I believe it might be due to the no longer valid options "Agreetolicense" and "NETSCAPE6".

Thanks very much for your assistance! If this message board distributed points on a scale from 1-10, you'd get at least 13 from me! =)
Posted by: turbokitty 14 years ago
6th Degree Black Belt
0
You're very welcome. For future reference, you can only call public (the ones in CAPS) properties from the command-line.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ