JDK-6681595 : Vista: Roaming profile users fail to access/use disabled Cache location Change button
  • Type: Bug
  • Component: deploy
  • Sub-Component: deployment_toolkit
  • Affected Version: 6u10
  • Priority: P2
  • Status: Closed
  • Resolution: Duplicate
  • OS: windows_vista
  • CPU: x86
  • Submitted: 2008-03-28
  • Updated: 2011-02-04
  • Resolved: 2011-02-04
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availabitlity Release.

To download the current JDK release, click here.
JDK 7
7Resolved
Related Reports
Duplicate :  
Relates :  
Description
FULL OS VERSION :
Windows Vista Business

Reported Against:
Java Platform, Standard edition. Version 1.6.0 build 1.6.0_03-b05
and Version 1.6.0_04-b12

Tested Reproducible with following JRE version(s):
JRE: 6u03-b05, 6u04-b12 and 6u05-b13 and 6u10-beta-b20

BROWSER VERSION:
Internet Explorer IE 7

Quoted from a system administrator report:
"We are having problems getting Java VM Runtime Environment Version 6 update 3 and 4 working with roaming profiles. We are using Vista Business as our SOE. Java settings in control panel are not being held onto when a user is logging. The settings are saved as a default user.
The main problem is the java cache files are not being stored or created in the profile. The javacontrol panel settings keeps referencing a sun folder on the root of C:\ drive for its cache files which, in an enterprise environment, user's don't have permission to write to. Can we force the Java to always use the LocalLow folder in the users AppData or even better the Roaming folder in the Profile Appdata??"

Reproducibility: This is being tested with multiple JRE versions -
6u03, 6u04, 6u05 and 6u10-beta-b20 (latest build). Cache button is disabled by default, leading to inability for sys admins to use JCP settings for critical changes desired as mentioned in the above report. (Also see attached screenshots)

Comments
EVALUATION After fix for 7012538 we are not storing data in the roaming profile by default. Closing as duplicate for now. Please file new report if this does not solve original problem.
2011-02-04

EVALUATION On vista, our deployment user's folder is now under the user's appdata locallow directory, which is the directory where a normal vista user can write to. The cache location cannot be changed, before we need read/write access to the cache, and the user's appdata/locallow location is the only location that a user can read/write into, even when he runs in IE protected mode with low integrity. Roaming profile is something different, and more investigation is needed on that.
2008-11-19