J2RE 1.6r14 - Disable Java Update
Hi All
I'm trying to deploy the above and also disable updates. I've set the following keys to zero in the property table (saved in an MST)
AUTOUPDATECHECK
JAVAUPDATE
JU
I've also created the following entry in the registry table and set it to zero:
HKLM\SOFTWARE\JavaSoft\Java Update\Policy\EnableJavaUpdate (DWORD)
When I run the MSI, I've noticed that the above entry gets created almost straight away (before any other registry entries) and is set correctly to zero. But then, by the time th installation finishes, it's changed to 1 instead. I'm guessing that there's a property that needs to be set to zero in order for this to work, but I can't figure out what property it should be.
The entry above in the registry table is part of the same component as all the other registry entires, so I don't think that's the problem (and I don't think Java has many "components" in the MSI anyway as far as I know)
Does anybody have any ideas why the entry is changing back to 1 at all ? Thanks in advance for any help
I'm trying to deploy the above and also disable updates. I've set the following keys to zero in the property table (saved in an MST)
AUTOUPDATECHECK
JAVAUPDATE
JU
I've also created the following entry in the registry table and set it to zero:
HKLM\SOFTWARE\JavaSoft\Java Update\Policy\EnableJavaUpdate (DWORD)
When I run the MSI, I've noticed that the above entry gets created almost straight away (before any other registry entries) and is set correctly to zero. But then, by the time th installation finishes, it's changed to 1 instead. I'm guessing that there's a property that needs to be set to zero in order for this to work, but I can't figure out what property it should be.
The entry above in the registry table is part of the same component as all the other registry entires, so I don't think that's the problem (and I don't think Java has many "components" in the MSI anyway as far as I know)
Does anybody have any ideas why the entry is changing back to 1 at all ? Thanks in advance for any help
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
mekaywe
14 years ago
have a look at this
http://www.appdeploy.com/packages/detail.asp?id=38
http://www.appdeploy.com/packages/detail.asp?id=38
Posted by:
spartacus
14 years ago
Also, the following thread, (in particular the use of the deployment.properties may assist you).
http://itninja.com/question/jre-1.6.0_05-automatic-update---deployment.properties-problems
Regards,
Spartacus
http://itninja.com/question/jre-1.6.0_05-automatic-update---deployment.properties-problems
Regards,
Spartacus
Posted by:
y2k
14 years ago
Hi Guys
Thanks for the replies. I didn't realize that this is a known issue, I found that it's been logged with sun for some time under bug ID 6559583, but Sun claim it's by design ... bad design if you ask me :-)
Anyway, the solutions at the links below were useful, but the problem with using a script is that it's an additional file that you have to ensure is with the install source, and I couldn't find a way to make the source dynamic (ie, based on the location of the MSI). So instead, I created 2 custom actions which change the registry entry at the very end of the installation using "reg add":
CustomAction Table-
Action: DisableAutoUpdate
Type: 98
Source: SystemFolder
Target: reg add "HKLM\Software\JavaSoft\Java Update\Policy" /v EnableJavaUpdate /t REG_DWORD /d o /f
InstallExecuteSequence-
Action: DisableAutoUpdate
Condition: NOT Installed
Sequence: 3187
I did initially have the sequence just after the InstallJava sequence, but the entries were written too late. so I put them after the PostInstallComplete instead.
I'm not a windows installer expert, but I do know that this works for us. But if anybody wants to add any improvements/comments - feel free
Thanks for the replies. I didn't realize that this is a known issue, I found that it's been logged with sun for some time under bug ID 6559583, but Sun claim it's by design ... bad design if you ask me :-)
Anyway, the solutions at the links below were useful, but the problem with using a script is that it's an additional file that you have to ensure is with the install source, and I couldn't find a way to make the source dynamic (ie, based on the location of the MSI). So instead, I created 2 custom actions which change the registry entry at the very end of the installation using "reg add":
CustomAction Table-
Action: DisableAutoUpdate
Type: 98
Source: SystemFolder
Target: reg add "HKLM\Software\JavaSoft\Java Update\Policy" /v EnableJavaUpdate /t REG_DWORD /d o /f
InstallExecuteSequence-
Action: DisableAutoUpdate
Condition: NOT Installed
Sequence: 3187
I did initially have the sequence just after the InstallJava sequence, but the entries were written too late. so I put them after the PostInstallComplete instead.
I'm not a windows installer expert, but I do know that this works for us. But if anybody wants to add any improvements/comments - feel free
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.