RDP Windows 2008 Logs Off Instantly When Launching With A Program
Hello. We are trying to create an RDP Session in Windows 2008, with the <Start the following program on connection> function. Our problem is...when we do this, the RDP client will, indeed, connect to the Terminal Server, but then AUTOMATICALLY LOGS OFF...and *never* launches our application!
As a side note...IF we test this WITHOUT that box checked...using the exact same user credentials...it authenticates, and logs in, directly to a Desktop. We do NOT want to present/provide a Desktop to such users; the whole purpose, is to lock the user into our application, and have their Terminal Session ended upon Exiting of our application (this is for a Point of Sale application on a WAN).
We've done this many, many times, on Win2003 (Terminal Server), but this is failing on Win2008. We're obviously missing something...and I'm hoping it's something quite simple. Any clues? Please help...we need to get this system up & running pretty quickly for the Remote Users...Thanks!...Mark
As a side note...IF we test this WITHOUT that box checked...using the exact same user credentials...it authenticates, and logs in, directly to a Desktop. We do NOT want to present/provide a Desktop to such users; the whole purpose, is to lock the user into our application, and have their Terminal Session ended upon Exiting of our application (this is for a Point of Sale application on a WAN).
We've done this many, many times, on Win2003 (Terminal Server), but this is failing on Win2008. We're obviously missing something...and I'm hoping it's something quite simple. Any clues? Please help...we need to get this system up & running pretty quickly for the Remote Users...Thanks!...Mark
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
We resolved this on our own. This answer was...and we didn't know this in Win-2008...we had to PUBLISH the application out on the RDP Apps Manager! That clued us in, and we've tweaked it since...to get the behavior precisely the way we needed.
Again, thanks to all of you!