0
I have an application that wouldn't start via Remote Desktop (it checks whether it was started via Windows Terminal Services). One simple way to circumvent this would be using a different remote desktop application, such as DameWare. This works, but I was wondering if I could keep using windows Remote Desktop, starting the application remotely by other means. So far I haven't been able to do so:
- PsExec / BeyondExec / Windows Scheduled Tasks - The application detects these as well (I assume they use Terminal services too)
- Telnet - The telnet session does not appear to be interactive, I can't see any of the applications I start there in my remote desktop session
I suppose I could always roll my own simple "remote process runner" (with say .NET/WCF), just wondering if there is something ready-made.
EDIT Rolling my own didn't work either, since I had to run the server application I built from Remote Desktop, and any process it spawned was still under that context
Optimus Prime
Posted 2012-02-12T15:54:09.023
Reputation: 1
I was wondering if you tried a
run asto change the user to a local one. Also, if the roll your own was a service running on the remote box. That way it would also use a local user account. PerhapsREMOTE.EXEwould help. Also, I don't know if VNC be acceptable. If I knew more on how the target app protected itself from remote execution, maybe I could give better suggestions. – Scott McClenning – 2012-02-13T02:42:50.053Strictly speaking, all interactive sessions, even local ones, now run via Terminal Services on XP and above. – user1686 – 2012-02-13T08:39:31.923
@Scott: What I rolled was a process running on the remote box, but I ran it from the remote desktop session. As per your suggestion I also tried
run aswith a local user, still woudln't start. Perhaps it simply recognizes that the current session is a remote desktop session ? – Optimus Prime – 2012-02-13T10:18:34.333