Attached is a working MST file to install Java 18 (actually, I created it for v17, but it still works fine with v18). This mst does the usual - disables autoupdate, links into IE and kills the tray icon.
I'd be interested in comments about coordinating deployment - in practice, I've had quite a few problems with PCs hanging up on deployment, usually because they've got pre-v11 Java manually installed. This I can understand a little, but on occasion I've had it hang-up during update from v17 to v18. My only working theory is registry corruption, but it's a pain. The only reliable way seems to be to remove any manually installed Java before you deploy the GP policy. This is hard if you have an AD group with 350 computers in it (that's just the curriculum group), so I have to organise some jiggery pokery to effect this room by room.
We use a startup script that looks for the java uninstall string for the relevant version, if it doesn't exist it'll issue a sc stop jqs and then deploy the .msi
Thanks Pete, that's very useful information, because I had overlooked that we omitted to disable JQS on the older computers (at that stage, we didn't realise it was a constructive thing to do). Furthermore, I hadn't thought of using the startup script in this context :D
Just installed on a test machine, installed fine.
But just doubled checked the autoupdate seemed to be set to check on the 20th of the month?
Is that a registry setting or from the setup control panel? When I used that MST, the update tab disappeared entirely from the Java control panel. That's what's supposed to happen, anyway. If the settings don't work, it generally means that the MST isn't being merged properly.
I've tried numerous suggestions for the "older" version of Quicktime but still not able to translate all that is requred to get it working for a GPO deploy for version 7.6.6 of Quicktime. Has anyone been able to get this deployed by GPO successfully? If so do you have a step-by-step for the MST modifications in order to get it working (or able to provide your MST file for download).
Thanks in adavance!
Extract QuicktimeInstaller.exe using 7zip or similar. Grab Quicktime.msi and AppleApplicationSupport.msi.
Use Orca to modify the Quicktime.msi. Specifically:
- Change the Summary info to include “0” and 1033 in the languages line (language-agnostic + US English). View → Summary Information, under Language delete all except for 1033 and add 0.
- Search for a row containing - LaunchCondition → NOT BNEWERPRODUCTISINSTALLED and (if the test package doesn’t install), drop the row.
- Save Quicktime.msi / save the transform.
- Place Quicktime.msi and AppleApplicationSupport.msi in a folder like \\server\applications\apple\quicktime-7.66
- Add Quicktime.msi and AppleApplicationSupport.msi to a GPO
Since the GPO pushes software in alphabetical order by default, AppleApplicationSupport.msi will be installed before Quicktime.msi (this is what we want).
Im not sure but when you install java 1.6 update 19 from the exe it install another msi call additional media support of somethin like thta (You cant see this in add/remove, only from the windows installer folder, you can find that easy by you the details icon view and having the subject information field, to find the msi)
Not sure if that msi installs if you install it the msi thats extract from the msi, so this may be the case with auto updater is still enabled on your method above, so seems to have changes from a few releases ago, of no one has noicted this. So somehow we would need to uninstall that msi. Not sure how we would do that through.
Has with quicktime, could someone make me the MSTs that are needed with the lastest version, would be extremlly gratefull (I have tried doing this myself serveral times, just cant get it to work) We are having to use an really old version for some program to work (6.5)
I think I have pretty much nailed my MST. If anyone is interested, I have attached it to this post. Comments welcome. :)
There are two MSTs included in the attachment. Both of them can be used together since they do slightly different things.
The first one is for installing Java with the usual things disabled (including the JQS service); while the second (SunConfig.mst) deploys the deployment.config and deployment.properties files to the %SystemRoot%\Sun folder as part of the installation. Although this is optional, it does enable you to restrict what users can change under the "Advanced" section of the Java Control Panel. I have added screenshots showing the difference this makes below. You can also modify these files if you don't like the defaults, but do not change the folder structure.
Is anyone getting certificate wierdness on Window 7 from recent (_18,_19,_20 tested so far) jre installs? Been playing around with a Win7 image for a computer room and I'm getting prompts re missing CRL info for a couple of bundled certs during install.
Doesn't appear on XP and there's no Win7-specific policies on the domain atm.