Jump to content

Recommended Posts

Posted
Why brother worrying about the new update warning

 

Just keep the lastest java deployed, then you have not got to worry

 

because they update it so frequently its hard to keep ontop of. I remember once doing i think it was 6r15 and later that day/tomorrow the next version came out

Posted
Right. So which registry key am I to use?

 

Sorry, getting a bit confused! CM you could put your package somewhere? :cool:

 

 

It's this key

 

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Update\Policy]
"EnableJavaUpdate"=dword:00000000

 

 

There's no package as such just the msi that you download from Sun and make those changes using Orca. I can try to put it somewhere if you like.

Posted

In addition to the obvious properties I've got two reg settings (acquired around update 12 and kept ever since, just in case):

 

HKLM\SOFTWARE\JavaSoft\Java Update\Policy\EnableAutoUpdateCheck => 0

HKLM\SOFTWARE\JavaSoft\Java Update\Policy\EnableJavaUpdate => 0

 

I didn't have to, and you really don't want to faff around with active setup. Not 100% sure but I think the setting the property EULA_JAVAFX_ACCEPT to "yes", sorted that. If you go to the java.com, do the version check then run the test app and don't get a pop-up eula then it worked.

 

I also take out the quick start service footprint with a "jqs.exe -unregister".

 

And the fairly important top-secret (unless you RTFM) bit: You can get the EXE installer to spit out different versions of the MSI.. one will install over an existing java (patch in place), another will install alongside... I think you need to read their expanation.

  • Thanks 2
Posted
In addition to the obvious properties I've got two reg settings (acquired around update 12 and kept ever since, just in case):

 

HKLM\SOFTWARE\JavaSoft\Java Update\Policy\EnableAutoUpdateCheck => 0

HKLM\SOFTWARE\JavaSoft\Java Update\Policy\EnableJavaUpdate => 0

 

I didn't have to, and you really don't want to faff around with active setup. Not 100% sure but I think the setting the property EULA_JAVAFX_ACCEPT to "yes", sorted that. If you go to the java.com, do the version check then run the test app and don't get a pop-up eula then it worked.

 

I also take out the quick start service footprint with a "jqs.exe -unregister".

 

And the fairly important top-secret (unless you RTFM) bit: You can get the EXE installer to spit out different versions of the MSI.. one will install over an existing java (patch in place), another will install alongside... I think you need to read their expanation.

 

 

 

Yes they finally added a switch that will remove old versions a while back but as you say they completly fail to mention it anywhere.

Posted (edited)

I missed a setting that you'll need to change. Using Orca edit the property table so the EULA is 0 "EULA"="0" when I do that I don't have to set the below setting.

 

I didn't have to, and you really don't want to faff around with active setup. Not 100% sure but I think the setting the property EULA_JAVAFX_ACCEPT to "yes", sorted that. If you go to the java.com, do the version check then run the test app and don't get a pop-up eula then it worked.

 

 

Then the only key i've added using a .bat file or Group Policy Preferences is the one below it seems to work fine now for me. Try it on a couple of PC's and go to java.com and see if the EULA pops up.

 

 

Windows Registry Editor Version 5.00

 

[HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Update\Policy]

"EnableJavaUpdate"=dword:00000000

 

 

So all you need to do once you've made the EULA change to the msi is.

 

1. Deploy the msi using group policy to a test PC not forgetting to add the mst file.

2. Deploy the reg setting and check using regedit that it has applied.

 

That should be it.

Edited by cookie_monster
Posted

Right, so I'm going to be using a CMD file to install this and the registry changes.

 

Something like:

 

pushd "\\srv001\Location\To\Packages\Java\v1.0.0.0"

 

start /wait java.msi /S

 

regedit /S regedits.reg

 

Now.. how can I include the transform file? I never got on with them before so I just edited the MSI directly and saved it as an MSI.

Posted (edited)
Right, so I'm going to be using a CMD file to install this and the registry changes.

 

Something like:

 

pushd "\\srv001\Location\To\Packages\Java\v1.0.0.0"

 

start /wait java.msi /S

 

regedit /S regedits.reg

 

Now.. how can I include the transform file? I never got on with them before so I just edited the MSI directly and saved it as an MSI.

 

 

 

Are you not going to use group policy to deploy the app?

 

If your doing it by command script then its /T to specify a transform but I haven't ever done it this way. You could possibly use Orca to make the transform changes part of the msi. I'd use group policy if at all possible.

 

Command-Line Switches for the Microsoft Windows Installer Tool

http://support.microsoft.com/kb/227091

Edited by cookie_monster
Posted

RM CC4. Edit directly in GP at risk of death.

 

I'll test /t to apply it on my test area and if that works, then great, otherwise I'll go down the route of editing in Orca like I have done for others.

 

Thanks so much for your help. There's a beer with your name on it.

Posted
RM CC4. Edit directly in GP at risk of death.

 

I'll test /t to apply it on my test area and if that works, then great, otherwise I'll go down the route of editing in Orca like I have done for others.

 

Thanks so much for your help. There's a beer with your name on it.

 

 

I thought RM CC3 and above used msi's for deploying software or you could use WinInstall to create msi's then deploy with RM package manager or whatever it's now called, I haven't used it since 2.4.

 

Can you not just deploy an msi with the native RM tools?

Posted

You can indeed. Just last time I tried I couldn't get the transform out. Should the MSI pick up the transform file? There's probably a way to include it.

 

I think to be fair if that is the route I am going down then I may as well just edit the MSI and include the changes in there, and scrap the MST.

 

In theory could create a new package entirely.

 

Run the Java MSI you gave me > Make the registry edits > Package

 

All done through WinLE.

 

Should do nicely. Ay?

Posted
In the MSI am I to edit the 'Property' table or the 'Registry'?

 

 

Edit the property table it seems to be more straight forward change EULA to 0. It worked in testing for me yesterday, I didn't see a licence prompt on javea.com.

Posted
You can indeed. Just last time I tried I couldn't get the transform out. Should the MSI pick up the transform file? There's probably a way to include it.

 

I think to be fair if that is the route I am going down then I may as well just edit the MSI and include the changes in there, and scrap the MST.

 

In theory could create a new package entirely.

 

Run the Java MSI you gave me > Make the registry edits > Package

 

All done through WinLE.

 

Should do nicely. Ay?

 

 

 

The MST contains allot of changes so you'll have to merge it with the msi file, i'm almost certain RM tools provide a way to add an MST. Put a post on the forums. Or you could repackage it using WinLE but it works so well with the MST i'd try to stick with that.

Posted
The MST contains allot of changes so you'll have to merge it with the msi file, i'm almost certain RM tools provide a way to add an MST. Put a post on the forums. Or you could repackage it using WinLE but it works so well with the MST i'd try to stick with that.

Yeh I merged them both in Orca.

 

Sorry, doing many things at the same time, and as a result I'm asking stupid questions which I could figure out if I sat down and thought. Apologies mate!

 

I've merged the transform, saved the MSI, and now I'm going to use LE to make a package that includes the registry changes. Then, if that works, I can put this baby to bed until they decide to release another next week. ;)

Posted

HKLM\SOFTWARE\JavaSoft\Java Update\Policy\EnableAutoUpdateCheck => 0

HKLM\SOFTWARE\JavaSoft\Java Update\Policy\EnableJavaUpdate => 0

 

There's no EnableAutoUpdateCheck so I assume I can skip this? Or do I need to add it? I've created it just in case but would be nice to know.

Posted
To apply an mst on a RM CC3 Network, copy the mst to the application folder and add the following line to the ini file:

 

WITransform=filename.MST

This is CC4 but it's not changed since CC3 to my knowledge. Thanks! Will save me time in future. :)

Posted
This is CC4 but it's not changed since CC3 to my knowledge. Thanks! Will save me time in future. :)

 

No need to do that with CC4. In fact I don't think it works like that anymore.

 

Go to the package properties and select the 'Contents' tab.

Under 'Command line arguments' add 'TRANSFORMS=.mst' to the 'Installation' line.

Posted (edited)

Okay, so that is done.

 

Now I need to work out how to make these registry changes!

 

This is giving me a headache.

 

I've got a regchanges.reg file with:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\JavaSoft\Java Update\Policy]

"EnableJavaUpdate"=dword:00000000

 

In CC4 you cannot put in a configuration file to tell it to run install.cmd with these changes in, which is what I wanted to do.

 

I tried creating a package with everything tied in put that didn't work either.

Edited by Edu-IT

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...