Java vs Terminal Server 2003 - CLSID

Users were experiencing a Red Cross for the applet, yet my administrative account was able to load the applet.

Looks like java or the installation process for java is not writing all the registry keys to HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Wow6432Node\CLSID\{CAFECA-00xx…..

In IE, Java has a catch all applet version – which will always work (aka the latest version)

<OBJECT classid="clsid:8AD9C840-044E-11D1-B3E9-00805F499D93

But most java call specific versions of java (for example).

<OBJECT classid=”clsid:CAFEEFAC-0015-0000-0013-ABCDEFFEDCBA




The server(s) for some reason didn't have all the keys in classes root, where compared to my windows 7 desktop.

I believe the install for some reason is writing the keys to HKCU instead of HKLM \classes...etc.

So fix is to add all the version to HKEY_LOCAL_MACHINE\SOFTWARE\Classes

http://pastebin.com/YhmwPTq7 contains my fix for 1.6u24 version

btw, Monitoring the registry when tick/untick the “use next generation java” in the java control panel, it just write all the entries to HKCU.