Software Deployment

[font="trebuchet ms"]Unfortnuately in 1.5.x even if you set the properties to 0, the update tab in the Java control panel still exists and the tick box is checked to auto update. There is a great VBScript posted by turbokitty in this post http://itninja.com/question/how-do-you-roll-out-new-machines?4295

[font="trebuchet ms"]I used the VBScript late in the execute sequence within the MSI editor and it worked like a charm.
[font="trebuchet ms"]
[font="trebuchet ms"]Hope that helps!
[font="trebuchet ms"]
[font="trebuchet ms"]Cheers

I tried putting the vbscript before install finalize. Deferred Execution - System. Not sure how to test if users will not get prompted to upgrade.
According to that last posting update will not run, since there is no entry HKCU\..\Run for the jusched.exe to load on startup???
You should find that in earlier versions of J2SE (i.e., 1.5.0_07), setting the aforementioned MSI properties WILL NOT untick the automatic updates box in the control panel. However, you will find that the MSI will not add an entry to HKCU\..\Run for the jusched.exe to load on startup, which means that the update settings will be irrelevant. As such, updates will not come down to the PC, despite the tick in the update box. If you install over the top of earlier versions -- of the same major and minor versions, but different patch level -- the settings will be retained from that earlier version *I think*.

Thank you very much for reply....

Not sure how to test if users will not get prompted to upgrade.This implies that you don't have a testing environment and a dummy test user account. Ouch...

I'd strongly advise you to get either a test PC with your standard build on it and install Ghost (or similar) or, better yet, install VMWare or MS Virtual PC (it's free!) on a well-specified box. The latter will allow you to have many builds, even different OSs, running on the host PC. Then you can build, install and test on different virtual machines and, when finished, return to a known state at the click of a button.

[font="trebuchet ms"]Ogeccut,
[font="trebuchet ms"]
[font="trebuchet ms"]From what I have been reading, you are correct that with this version of JRE, you could simply modify the reg key you mentioned and the updates will not happen regardless of the Java control panel tick box. For me, that VBScript in the package simply removes the 'Update' tab in the Java control panel which was simply 'peace of mind.' I'm not really sure how you would test that the auto-update config actually worked.

VBScab, Thank you for reply. I have test machines and test accounts. and some Vm's as well. Maybe i am missing something, but how do i test if java will prompt a user to update in the future?
Thank you very much.

Change the PC date to trigger a timed update?

Edit the registry so that a previous version number is indicated? I think HKLM\Software\JavaSoft\Java Runtime Environment\CurrentVersion is the one which is referenced but don't quote me. Set up a VM with updates enabled and play with it to see which key/value is the trigger. Then simply alter it on the test VM and check whether an update prompt appears or whatever.