how to simulate a human-being logon onto a PC and take control back from a RDP session?

[cfman]

Hi all,

I have a weird software, does not launch itself when it detects the presence
of a MS Remote Desktop (RDP) connection.

Call the remote PC at my office the SERVER, and the local PC at my home the
CLIENT.

Situation 1:

I want to remotely luanch that wierd software on my SERVER via a RDP
connection.

The wierd software detects the ongoing RDP connection, it refused to luanch.

Result: I have to drive a long way to my office to run it.

Situation 2:

Okay! Now let's fool around the wierd software a little bit.

I set a timer on the SERVER, and set it to launch the wierd software after
60 seconds.

Then I close the RDP connection, and have a cup of coffee, and after
sufficiently long time,

I re-connect to my remote SERVER, expecting that the wierd software should
be fooled and it should launch, because at the moment of its initilization,
there is really no RDP connection at all.

(Please note that if I first physically go to my office and launch the wierd
software, and leave it open, and then I come back home to use it, that's
perfectly okay. It works. The only problem lies in if I want to start it
remotely from my home).

Result: It failed. It didn't start. I still have to go to office and run it
manually.

Situation 3:

After I used RDP, I drove to office, and logged in, and launch the weird
software manually.

Result: It runs.

-----------------------------------

In conclusion:

The wierd software SUCCEEDS to luanch if: there is a human-being physically
sitting in front of the computer, logged-in, and click on it and run it
physically.

The wierd software FAILS to launch if: the person used a RDP to connect to
this PC, and he closed the RDP, but this PC is still logged out due to RDP
connection, thus it detects this situation and refuses to launch(even if the
RDP was already disconnected.)

-----------------------------------

So how can I set a timer using RDP, and then disconnect the RDP, and the
timer software does the following:

simulate a person physically takes control from RDP and login into the
system, and launch the software manually,

how can I do this?

Thanks a lot!

[Vera Noest [MVP]]

I assume that both PCs are running XP, correct?
Is there anything in the EventLog which explains why the
application doesn't run when started in a remote session?
Do you get an error message?

I'm not sure what exactly you mean with "set a timer".
Do you mean running a Scheduled Task? If so, under which user
account does it run? By default, the Scheduler service runs under
the System account, maybe you need to run this application under
your own account?
And if you have used the Task Scheduler, what is the exit code when
it fails? And what does the Scheduler logs tells you about the
failure?

Note that you can disconnect from a connection to an XP client
*without* leaving the host in a state where no user is logged on:

From http://ts.veranoest.net/ts_faq.htm

Q. I need to have an application running on the console. How can I
monitor it?

A. If the application is running on a Windows 2003 Server or XP Pro
desktop, you can connect to the console (=session 0), by starting
the rdp client from a command prompt:
mstsc /console

After you have done with your work remotely start a command prompt
within the remote session and type:
tscon 0 /dest:console

This will disconnect your remote session and 'push' it back to the
console.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

"cfman" <comte...@gmail.com> wrote on 16 jul 2006 in
microsoft.public.windows.terminal_services:

[Erik Funkenbusch]

On Sun, 16 Jul 2006 11:02:07 -0700, cfman wrote:

> The wierd software detects the ongoing RDP connection, it refused to luanch.

My guess is that there is a reason the software does this. Why would they
go to all the trouble of making it detect a remote desktop and fail if
there wasn't an important reason to do so?

Maybe you should contact the customer support of the company that makes the
software and ask them why it won't run under terminal services?

[cfman]

"Erik Funkenbusch" <er...@despam-funkenbusch.com> wrote in message
news:10t87nclro7ai$.dlg@funkenbusch.com...

They intentionally made it. They also sell the network version of the same
software. You see the point?

However, I am a VILID single user of the PC and the software. I am not
sharing with anybody else my PC.

This stupid software, by making the terminal service access disallowed, it
also blocked a VALID single user(such as me) the possiblities of accessing
office PC from home PC to use that software.

I have to drive a long way back and forth between home and office just to
launch the software on such a beautiful weekends.

It doesn't make any sense!!! It sucks.

(If the software didn't crash, then I can open it once on Friday and enjoy
using it remotely on weekends; but it crashed from time to time... thus
relaunch it becomes a problem...)