Application Paths and RDP Connection

[Mark Stoker]

I have a registry setting

HKEY_LOCAL_MACHINE\Microsoft\Windows\CurrentVersion\App Paths\filename.exe

with a value that located the executables .dll files.

When the user logs on from a RDP session first onto the desktop then runs
the application all work fine. However if I configure the RDP client to run
the file upon connection (i.e by passing the desktop) the application fails
to locate the .dll files i.e the registry setting has not been read.

Why does TS do this and how can I get around the problem.

Mark

 

[Mark Mancini]

there are some apps that call variables and such and need the start-in
folder populated as well. Some require explorer.exe to be running.
Previous versions of AppLauncher addressed these for clients that use MAS90
and other difficult apps. The next version will deal with the apps that
require explorer to be running.

One way to test if I'm right is to download the 14 day eval and see if the
app runs, if so...then that's it. If not, it's the explorer thing.