P5
A DESCRIPTION OF THE REQUEST :
Currently the settings in the Java Runtime Environment must be set during the installation (properties in the MSI file). This means that for every new version customization is required.
To allow enterprise environments to upgrade easy to the latest JRE versions, it would be great if these options can be forced by Group Policies. By example we want to be able to disable auto-update, enable TLS 1.0 and disable destop integration.
When also security fixes are distributeed as MSP files, this would make managing JRE much easier.
JUSTIFICATION :
Make upgrades in the JRE much easier and standardize the settings in a corporate environment.
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
New version should be released as full versions (MSI-files) and as patches (MSP-files).
It should be possible to configure Java using Group Policies to minimize customization during the installations.
ACTUAL -
New versions are released as MSI files wrapped in executables. New versions do not remove previous version, leaving security vulnerabilities on the system. Settings must be made again in every new version and are not centrally managed from Active Directory.
Currently the settings in the Java Runtime Environment must be set during the installation (properties in the MSI file). This means that for every new version customization is required.
To allow enterprise environments to upgrade easy to the latest JRE versions, it would be great if these options can be forced by Group Policies. By example we want to be able to disable auto-update, enable TLS 1.0 and disable destop integration.
When also security fixes are distributeed as MSP files, this would make managing JRE much easier.
JUSTIFICATION :
Make upgrades in the JRE much easier and standardize the settings in a corporate environment.
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
New version should be released as full versions (MSI-files) and as patches (MSP-files).
It should be possible to configure Java using Group Policies to minimize customization during the installations.
ACTUAL -
New versions are released as MSI files wrapped in executables. New versions do not remove previous version, leaving security vulnerabilities on the system. Settings must be made again in every new version and are not centrally managed from Active Directory.