C
cfman
Hi all,
I have several softwares here that they don't work along well with MS RDP.
One software, in particular, does not even launch itself when it detects the
presence of a 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.
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).
It failed. It didn't start.
-----------------------------------
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.
-----------------------------------
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!
I have several softwares here that they don't work along well with MS RDP.
One software, in particular, does not even launch itself when it detects the
presence of a 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.
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).
It failed. It didn't start.
-----------------------------------
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.
-----------------------------------
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!