Terminal Server Roaming Profile Issue - Java won't load on some profiles

My company is going into the second phase of deploying a web-based
application, and they would like to make sure it is usable from our
terminal server farm. The issue we are having is that Java appears to
work for some users in Terminal Server but not for others.

Java was first installed on the Terminal Servers about three weeks
ago. Users who had their profile created in the last year don't seem
to have a problem. Any profile older than that does not seem to
work. The major change that happened around that time was converting
from Server 2003 Standard to Server 2003 Enterprise x64.

I can replicate the issue. If I create a test user and log them into
our sole 32-bit terminal server (which is not part of the farm), and
then log them into the 64-bit Farm, Java will not work. If I
completely delete their profile and then log them into the 64-bit
farm, it does work.

I did run a comparison of NTUSER.dat files using WinMerge from a user
who can and cannot use JAVA. I created a .REG file with all the
registry pointers to Java and had it apply to a test account that was
created on a 32-bit terminal server via GPO startup script, but that
did not fix the issue.

I also ran Procmon while trying to load Java with these two accounts,
and the one main difference that I could see was that there was a
registry key in HKU that the broken account was looking for. I could
not find this key while searching the NTUSER.dat file account that can
use Java.

Is there anything else that I can look at or try to fix this issue? I
would like to avoid deleting all our Terminal Server profiles as it
would be a logistical nightmare, but if that is what we need to
resolve this issue, I can accept that.
.

Relevant Pages

  • Re: Help with configuration
    ... option cleared on the RDP-tcp connection Client properties tab for "Use ... If I do NOT specify a roaming profile path, do I still need to enable ... Users should logon to the workstation using their domain account ... Your GPO settings do not apply to your Terminal Server. ...
    (microsoft.public.windows.terminal_services)
  • Re: Help with configuration
    ... Users should logon to the workstation using their domain account ... Your GPO settings do not apply to your Terminal Server. ... Folder under "All Users" on the TS. ... local workstation profile, which includes application ...
    (microsoft.public.windows.terminal_services)
  • Re: Help with configuration
    ... OK, so your GPO is working now, good! ... local profile, both on their clients and on the TS. ... account profile is blank, also). ... Your GPO settings do not apply to your Terminal Server. ...
    (microsoft.public.windows.terminal_services)
  • RE: Java Apps over the Internet
    ... Microsoft MVP - Terminal Server ... "Patrick Rouse" wrote: ... RAM consumption. ... as it consumed 130MB of RAM just to load the java applets ...
    (microsoft.public.windows.terminal_services)
  • Re: Accessing a Terminal server with a domain login (not local login)
    ... Could have something to do with your profile. ... settings in your AD account. ... When You Try to Log on to a Terminal Server ... > can logon using a local username and password to administrer ...
    (microsoft.public.windows.terminal_services)