Java 6 Update 10 Issue
Hi,
I am using the MSI file to install Java Version 6 Update 10 and all I want is to have it install silently with updates disabled.
I am using ORCA to edit the Transform file (.MST) and I can find and change the below entries:
JAVAUPDATE=0
AUTOUPDATECHECK=0
JU=0
All goes well I use the below command to start the install:
MSIEXEC /i jre1.6.0_10.msi TRANSFORMS=SP1033.MST
(I have not made it silent yet not until I’m happy with the install.)
All goes well the install goes through the motions but when I open up the control panel settings the Update page still has the tick in "Check for Updates Automatically"
I have tried changing the MSI file itself and get the same result.
I have also tried passing in the values by changing the command (see below) still the same result.
MSIEXEC /i jre1.6.0_10.msi JAVAUPDATE=0 AUTOUPDATECHECK=0 JU=0
This is onto a Vanilla install of XP using SP3 for each test. To retry the test I have removed Java using Add/Remove programs with no restarts and tried again.
Any ideas?
Cheers
Scott
By the way love this forum I have used so much information from here now I decided to sign up finally.
0 Comments
[ + ] Show comments
Answers (5)
Please log in to answer
Posted by:
jmcfadyen
15 years ago
have a look here there is multiple solutions to this issue
http://www.appdeploy.com/packages/browse.asp?cat=alpha&str=j
http://www.appdeploy.com/packages/browse.asp?cat=alpha&str=j
Posted by:
scott.shepard
15 years ago
Posted by:
joedown
15 years ago
Looking through the info on JRE there are many ways listed to accomplish this but none of them appear to get to the root of the issue as to why it is enabled. If you add the registry entry to the Registry table Software\JavaSoft\Java Update\Policy and set it to a value of 0 Process Monitor will show that it will get overwritten later during the install. Why is this and how would one go about narrowing it down to the custom action, or whatever, etc that is changing the value after it was already written?
Posted by:
anonymous_9363
15 years ago
Why is this and how would one go about narrowing it down to the custom action, or whatever, etc that is changing the value after it was already written?Joe, do I recall correctly that you're a Wise Package Studio user? If so, why not step through the install with WPS's Debugger? With the MSI/MST loaded for editing, hit Ctrl-E and the debugger will start. You can set break-points using F9 and step through an action at a time using F8 (exactly the same as VB/VBA). With that set up alongside ProcMon, you can pinpoint exactly the point at which the registry changes.
For IS AdminStudio, I think you're restricted to creating a debug log but I'm happy to be corrected - I'm not a big-time IS AS user these days, nor have I ever used this facility. You need a registry entry like this:
[HKLM\Software\InstallShield\AdminStudio]DebugLogLevel="3" which will cause a file AdminStudio.LOG file to be created in the same folder where AdminStudio.EXE is located.
Posted by:
joedown
15 years ago
No, unfortunately my only available software is Admin Studio Zenworks edition. That's why I try and do most of my work in Orca. I only use Admin Studio to capture legacy setups to MSI. That feature in Wise to step through sounds like a really cool troubleshooting tool. Maybe InstEd will eventually include a feature like that.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.