RDP - Startup program access denied

I can log in with a remote desktop user (not administrator) to a terminal server and run a program, but when I put this in the "start the following program on connection" I'm getting an access denied error to the program.  The server is 2008.
Who is Participating?
rftaConnect With a Mentor Author Commented:
I found the problem.  I had installed TS RemoteApp which I was going to configure later.  It has a setting in it that restricts the programs a user can run on startup.  I had to change it to allow both listed and unlisted programs.
If you go into TS RemoteApp Manager and click on the "RDP Settings Change" link it will bring up a control panel.  Click on the Terminal Server tab and there at the bottom is an option box "Access to unlisted programs".  Tada.  Eventually I'm going to configure this app as a RemoteApp.
why not add it a startup shortcut inside your startup folder
rt click Start
click open
dbl click Programs
dbl click Startup
add a shortcut in there to launch programs
works great for me
I think what u are seeing is a permissions problem

rftaAuthor Commented:
What's nice about putting it in the start program in the RDP profile is that when they exit the program, it logs off their session.  I'm just not understanding why it's not a problem when I log in and double-click the shortcut vs. putting it in the start program in the RDP configuration file.
Doing it your way will give them access to the desktop which is what I'm trying to avoid, but it may come to that if I can't find the solution.
Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

Hello I tried this with RDP logging on to TS server 03 and I entered the program info into the RDP options  from the shortcut properties on the 2003 Terminal Server  and it worked fine.
I logged into the TS and brought up the properties of the short cut pasted them to Note pad and logged off and entered the settings from options before logging back in.
rftaAuthor Commented:
I have a 2003 server with this same program on it.  I'm thinking that it will work there.  I'm wondering if this is a 2008 terminal server bug.
its gotta be a permissions thing to get that error
trhanks soo much. Had the same issue and looked for it for hours.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.