1. There is a tab in RDP "Programs", that allow you to specify to "start the following program on connection"
2. Save your connection as an .rdp file, and use the DOS RUN to start the connection.

>>Perhaps this might help
>>
>>http://support.microsoft.com/kb/281262
>Thanks, but I don't think this is the complete story.
>
>I guess I wasn't clear... What I did was, log on via rdp. Then ran my application from the desktop that appeared (via dblclick of icon on desktop).
>
>What I was hoping to automate, is not just the log on process, which is what that kb seems to be about, but also launching my application from inside the terminal services screen.
>
>So I envision a custom loader program, like the one I already have to run the application locally (with the data on the local network server drive).
>I was hoping to change my loader program, if the choice is a remote computer to automatically run terminal services. Once terminal services has logged on, I would like to automatically run my app on the remote machine.
>
>That's why the reference to tasc, as it sounds like it might work.
>
>Does this help clarify matters?
>Thanks,
>Mike
>
>>
>>>I am able to run my application on terminal services if I do it by hand. i.e. I login in remotely via rdp, and then when the desktop appears, I run my app.
>>>
>>>This is too messy for my users...
>>>
>>>Is there a way to automate this?
>>>
>>>i.e.
>>>The user picks the location, and based on this selection, I connect to the remote location via terminal services and run my application.
>>>
>>>I found something here, or was it on WIKI, not sure, called tasc... but I can't seem to get it to work. It requires some ole control to be registered. (msrdp.ocx) I tried placing the control in the default directory of my app and then running regsvr32 msrdp.ocx. There were no complaints, but the form still didn't work.
>>>
>>>Thanks in advance,
>>>Mike
>>>
>>>There is no error returned but the control does not seem to work.