Lose control after Remote Desktop Connection
Joseph Renzi
Connection to connect to the slave machine, I can not longer access
the slave machine using Input Director.
It seems that Input Director is disabled on the slave and I need to
use the slaves keyboard and mouse to turn Input Director back on (turn
slave mode on).
Is there a setting that fixes this, or is it a bug?
Example:
Master = Windows 7
Slave = Windows XP
1. Master can operate slave using Input Director
2. Master does a Remote Desktop Connection to slave
3. Master closes Remote Desktop Connection to slave
4. Master can no longer connect to slave using Input Director
Any help would be very much appreciated.
Shane
> I can use Input Director fine, but after I use Remote Desktop
> Connection to connect to the slave machine, I can not longer access
> the slave machine using Input Director.
>
> It seems that Input Director is disabled on the slave and I need to
> use the slaves keyboard and mouse to turn Input Director back on (turn
> slave mode on).
>
> Is there a setting that fixes this, or is it a bug?
Hi Joseph,
I'll look into this and see what's going on.
When you close the Remote Desktop Connection - are you logging out or
just closing the remote desktop window?
Regs,
Shane.
Joseph Renzi
firstly, thanks for a great product ...
On Feb 19, 10:21 am, Shane <sh...@inputdirector.com> wrote:
> I'll look into this and see what's going on.
> When you close the Remote Desktop Connection - are you logging out or
> just closing the remote desktop window?
In answer to your question, I am simply closing the remote desktop
window (not logging out).
I look forward to your response and to recommending your product to
many people.
Regs,
Joe
Shane
I ran a quick testing following the steps and it worked for me.
A couple of questions -
1. When you started the terminal session on the slave, did the slave's
monitor switch to the Windows login screen?
2. When you quit the terminal session, did the slave's monitor remain
on the login screen and you then had to use the slave's physically
attached mouse/keybd to resume your original session?
3. Are you logging onto the slave, via RDP, as a different user to the
one already logged on?
Can you send me something to help -
1. Master can operate slave using Input Director
2. Master does a Remote Desktop Connection to slave
3. Startup a copy of notepad on the slave (via RDP)
4. Open the task manager on the slave.
5. On the task manager, select View / Select Columns and then check
"Session ID" and "User name"
6. Expand the task manager window so that all processes are in view
and then take a screenshot of the window and email it to me.
Also, if you haven't tried already, try logging out of the RDP session
rather than just closing it and see if that helps.
Regs,
Shane.
Joseph Renzi
I have solved the problem.
In summary, when I started the Remote Desktop Connection to the slave,
I noticed that Input Director chnaged to disabled mode (which is
fine), but when I closed the Remote Desktop Connection unfortunately
Input Director was still disabled (so therefore it would not respond).
I played with the settings in Input Director solved the problem by
changing a setting in "Global Preferences" - I changed "On Start =
Input Director is disabled" to "On Start = Input Director is enabled
as Slave"
(note: I also have "Run Input Director on Starup" turned on, and the
"Background slave active for all users at logon" turned on)
This means that whenever I close the Remote Desktop Connection to the
slave, Input Director activates itself again as a Slave, and
everything works perfectly!
Thank you very much for your help.
You have developed a great product, and it is so great that you offer
it for free ... I will definately recommend this to many people.
Joe