Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sofware: Java Runtime Environment 1.6.0_21

OS: Windows XP Professional 32-Bit, SP3

Situation: a new piece of web based software is being deployed this week and prior to this all the company desktops need to be set up to meet the requirements of this software. One of these requirements is JRE 1.6.0_21.

I have successfully scripted the removal of all other Java versions and the installation of the required version, however I cannot get it configured properly.

One of the requirements is that the Java console be set to disabled - if it is not it can cause an issue with a particular function. I have pushed out a deployment.config and deployment.properties but the console just will not disable itself.. I know the config is being read correctly because the update tab is being correctly disabled and removed.

deployment.config:

deployment.system.config=file\:C\:/WINDOWS/Sun/Java/Deployment/deployment.properties
deployment.system.config.mandatory=true

deployment.properties:

#deployment.properties
#Fri Jun 15 09:34:31 EST 2012
deployment.version=6.0
deployment.console.startup.mode=DISABLE
deployment.javaws.autodownload=NEVER
deployment.javaws.autodownload.locked=

There is no change if I set the console to ENABLE either - it remains on the default of hidden.

I'm sure I can disable the console with a registry change of some form but my preference is to have it done via the deployment files as it gives the option of centralising the properties file to a network share if we wish.

If anyone has any suggestions it would be appreciated.

share|improve this question
    
Couldn't you do it trough Active Directory (GPO)? This would also be "centralised" –  MichelZ Jun 19 '12 at 4:54
    
I could, but as far as I'm aware the only way to manage Java though group policy is just by using it to modify the registry - technically yes this is also centralised but I still prefer to use the built in management methods. –  user125137 Jun 19 '12 at 6:12
    
GPO is all about registry... :) –  MichelZ Jun 19 '12 at 6:32
    
By the way... The valid properties for deployment.console.startup.mode are: •"HIDE" to hide the Java Console; •"SHOW" to show the Java Console; •"DISABLE" to disable the Java Console; Can you test SHOW to see if it would work? (You seem to have used "ENABLED") –  MichelZ Jun 19 '12 at 6:36
    
Sorry that was a typo, I had tried it on SHOW as well. As it turns out this morning it's working.. I have no idea why, nothing was so much as rebooted before I went home but today, logged the test machine off then back on again and everything is fine. –  user125137 Jun 19 '12 at 23:14

1 Answer 1

OK - it is now working. I have no idea why - I changed nothing last night before I went home, came back this morning and logged back into the test machine (which hadn't even been shut down) and found it working exactly how it should.

If anyone has an idea why it might of happened would be nice to leave here for anyone else who has the same problem.

share|improve this answer
    
Personally, I wouldn't install Java on the system. I would simply copy a JDK (not JRE) installed directory from another machine into C:\Java\JDK1.X.0_XX and then define JAVA_HOME and put JAVA_HOME/bin in the PATH. Then you don't need to worry about any JRE stuff that the JRE or JDK installed on the system. –  djangofan Nov 15 '13 at 23:18

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.