Once the browser has been opened in the virtual environment with a legacy Java version attached, there is nothing to stop the user continuing to use the browser window to go about their daily business, where they are a potential open target for malware.Unfortunately this causes issues when we are virtualising legacy plugins and do not want the native browser to see them! App-V 5.0 SP2 now virtualises ActiveX control and Browser Helper Objects and presents them to the local Internet Explorer.Also to make it more complicated, these issues can often affect some users but not others. Mostly the browser opens in the virtual environment with the desired version of Java, but sometimes it can ignore that and open the locally installed version. The solution does not always work as intended.There are a few problems that I have commonly seen with this: Then the locally installed Java version can be kept up to date, or even removed entirely. It is required by various business critical applications, yet it is the number one target for malware, made worse by the fact that people don’t always apply the latest security updates because they have an application that depends on an older version (or simply not bothering to regularly test their applications with each new release!).Ī great solution to this is to use App-V to virtualise older Java versions then link them to the applications (or browser shortcuts) that depend on them. Java is a necessary evil in today’s enterprise desktop.
Sequencing Java - The Definitive Guide Part 1
0 kommentar(er)
