To install apps, always log on as a member of the local administrators group. At a command prompt, run the setup.exe for the program you want if you only want that account to access it. If you want all users to access it, type 'change user /install' and then run setup.exe. I used to make it a habit of always doing 'change user /install' before installing, even if it was an admin-only app, because if other admins needed to run the tool they couldn't without knowing my password; we just used disk and Registry ACLs to keep folks out.

There is a Registry Key under hklm\software\microsoft\windows nt\current version\terminalserver (or a close approximation thereof). When you do a 'change user /install', the Terminal Server service catches any Registry software settings the app is trying to make and puts it there. There are also some gyrations made to the HKU key.

You might want to take a look at the control's docs about where it puts its Registry droppings, and see if they are actually making it into the Terminal Server 'phantom locations'.

Also, you might want to take a look at where you have the whole thing installed in the first place. I have had the best luck when I think of the Terminal Server as a shared workstation, not a server, and install everything where I would as if I was running a standalone peecee. For example, keep all programs in c:\progra~1, etc.

Hmmm... Something else that worked for me on an install. I ran RegMon from the SysInternals geniuses, and watched all of the keys that were written when I installed an app (I did it on a standalone desktop). Then I created a regini .ini for all of the keys that were written. Then I took the .ini to the terminal server, and modified the usrlogon.cmd file to automatically regini myini.ini at user session start time, before any app kicks off. That way I was sure the whole environment was set (the .ini was read-only of course). I have found that RegMon is a great debugging tool when running apps under TSE, since things don't always act like you'd expect. I had to do the whole RegMon thing when supporting/integrating this horrible ORSOS (Operating Room Scheduling software) app and the vendor didn't even know how their app ran on a workstation, let alone under Terminal Services.