Problem setting up JRE 1.6.0 using properties
Hello!
I have the following problem with the new JRE 1.06 (the JRE 1.5.0.10 seems to have the same prob):
It doesn't matter whether I change the necessary properties with ORCA to create an MST or start the setup with parameters (AUTOUPDATECHECK, JAVAUPDATE, etc.), I just can't turn off the automatic updates during the setup (manually and GPO).
The associated registry entries (HKLM/...) are definitely changed after the setup, but the problem is that these settings are no longer used to setup the automatic updates in either way - the critical setting is now placed under "HKCU/Software/JavaSoft/Java Update/Policy" in the binary key "EnableAutoUpdateCheck" with a hex value.
So far I have no solution for this issue.
beay
I have the following problem with the new JRE 1.06 (the JRE 1.5.0.10 seems to have the same prob):
It doesn't matter whether I change the necessary properties with ORCA to create an MST or start the setup with parameters (AUTOUPDATECHECK, JAVAUPDATE, etc.), I just can't turn off the automatic updates during the setup (manually and GPO).
The associated registry entries (HKLM/...) are definitely changed after the setup, but the problem is that these settings are no longer used to setup the automatic updates in either way - the critical setting is now placed under "HKCU/Software/JavaSoft/Java Update/Policy" in the binary key "EnableAutoUpdateCheck" with a hex value.
So far I have no solution for this issue.
beay
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
gmorgan618
17 years ago
Beay,
Current_User settings in a multiple user environment, or in an environment where you deployment tool installs applicaitons in the system context is a little tricky.
Active Setup is the easiest solution - it only involves adding - 1 registry key and 1 value called "stubpath" (you can add more)
Look here for a complete write up(or almost complete):
http://www.etlengineering.com/installer/activesetup.txt
I'm not sure if the article states this, but once the active setup has run for a user - it creates the same key that you will create in HKLM, in the same location under the HKCU - if you ever need it to run again for that user, just delete that key in HKCU.
If this doesn't help, just let me know and I can write an explanation of Active Setup, but i'm trying to avoid that...
-Grant
Current_User settings in a multiple user environment, or in an environment where you deployment tool installs applicaitons in the system context is a little tricky.
Active Setup is the easiest solution - it only involves adding - 1 registry key and 1 value called "stubpath" (you can add more)
Look here for a complete write up(or almost complete):
http://www.etlengineering.com/installer/activesetup.txt
I'm not sure if the article states this, but once the active setup has run for a user - it creates the same key that you will create in HKLM, in the same location under the HKCU - if you ever need it to run again for that user, just delete that key in HKCU.
If this doesn't help, just let me know and I can write an explanation of Active Setup, but i'm trying to avoid that...
-Grant
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
