This resolved the Java RE 1.7.0 issue for ALL USERS. However, I want all users to function so I then modified the keys to be HKLM (HKEY_LOCAL_MACHINE) and then imported the keys. So I first tried simply importing this key into the RDP user and this worked for the specific user account.
These keys existed for the functioning user but were missing for the RDP user accounts. HKCU\Software\Classes\CLSID\\InprocServer32 However, I find it really odd that I haven't found anybody else mention this on the web.Īfter a lot of tracing with Sysinternals Procmon.exe I found a specific difference in Registry Keys between the Installed Console user and the RDP user. I'm thinking there is something in the Java RE 1.7.0 that is not installing properly for Terminal Services under Windows Server 2003.
#JAVA 1.7.0 DOWNLOAD 32 BIT INSTALL#
The other two VMs behaved in the exact same manor making any user other than the Install user unable to use Java RE 1.7.0. In order to test this I went ahead and fired up a couple of my Windows 2003 VMs that have Group Policies & Terminal Services setup in a similar fashion to test. Tested using (set as "Trusted Sites" to ensure security settings are lowered): After installing 1.7.0 none of the RDP Clients are able to run Java even though "Use JRE 1.7.0_5 for (requires restart)" is checked in their Advanced Internet Explorer 8 Internet Options page.Įven accounts that have Administrator privileges that are not the account used to install are unable to use Java RE 1.7.0. During the updates I uninstalled all the previous Java RE versions restarted and then installed Java RE 1.7.0 under an Administrator Login using Add/Remove Programs (for Terminal Services Install Mode). Recently, I was performing updates on one of our Windows 2003 Terminal Services.