This content has been marked as final. Show 15 replies
This other thread has some suggestions but everyone's results have been varied.
The specified item was not found.
This is just ridiculous. SO many properly managed situations where this is causing headaches. Oracle needs to be slapped right now.
Maybe a prompt after a version is SEVERAL versions old would be tolerable, but not the VERY next version. This is stupid.
Thanks for the link. Unfortunately none of those solutions worked for me.
Its sort of ridiculous that these prompts even show up when logged in with non-admin accounts. The worst bit is if a user hits the Update button, and can't complete the update due to not being admin, every time that a java app tries to load, it redirects the user to the download page for Java.
So far nothing has worked for me either. I may be about to try and downgrade us entirely to update 10 (I think that's the last version before this new 'feature' came out)
To prevent prompting for "Your version of Java is insecure":
Its depend what way are you using to configure Java.
You can add properties listed below to your configuration file (per-user, per-machine) or registry keys.
The solution is to add two rows (entries):
In our company per-machine deployment.properties file is used (c:\windows\sun\java\deployment\deployment.properties)
And it is working.
I tried adding the options you mention. I get a different prompt now. It's still a Java is insecure message, but a different window this time. I have the options of Update, Block, or Later with a checkbox to not ask again until the next update.
This is what I have in the config file... perhaps some settings are conflicting?
There aren't any conflicting settings, maybe you should delete user config file (c:\Users\%username%\AppData\LocalLow\Sun\Java\Deployment\deployment.properties).
This works on clean installation, maybe some properties are applied from user config file.
You will be asked only to run java applet cause security level is set (this is configured by editing security level to custom + without prompting)
Has anyone been able to figure out how or where Java gets the security baseline and how it is updated?
I've also tried this with no luck. I delete the deployment.properties from C:\Documents and Settings\user\Application Data\Sun\Java\Deployment - then add the deployment.properties into the C:\WINDOWS\Sun\Java\Deployment folder. For whatever reason it doesn't seem to work correct - because I get the prompts and the deployment.properties (auto-generated) show up in C:\Documents and Settings\user\Application Data\Sun\Java\Deployment again.
Any ideas? I am stuck with this one
It is not enough to put only deployment.properties into C:\WINDOWS\Sun\Java\Deployment..
You should also read how to set system level properties.
And then use my tip
I'm currently Testing Java 7 Update 11. I have test with given setting in my environment but none of it work. It still prompt's for Java insecure for 7 update 11. It really make me Mad on Java. Is there any new finding for this issue.
Please advise. Thanks in advanced. :)
While not perfect, this is what I came up with for a workaround (most of the time)
Oracle seriously needs to fix this.
I wish Oracle would post a definitve answer to this issue, I am struggling to replicate this issue, so cannot fix.
We are getting so many helpdesk calls.
Is there a version of 1.7 which works? i.e. an earlier version.
& why are Oracle locking these threads?????
This is a user to user forum. Oracle will not reply here. File a SR.