Hi team,
We have installed MS into a customer's remote machine and are driving everything over RDP. Keyboard and mouse commands into MS work, as do commands into Windows File Explore and browsers.
Image recognition and OCR work.
When we try to drive Active Directory Users and Computers the SetFocus works, but keyboard and mouse commands do not.
Press Tab
LClick
Press Enter
etc.
On the face of it, we feel we have found an application which isn't listening to the MS commands even though MS is installed into the host machine itself. Your thoughts would be appreciated. Thanks.
RDP KeyBoard/Mouse Control
Moderators: Dorian (MJT support), JRL
-
Marcus Tettmar
- Site Admin
- Posts: 7380
- Joined: Thu Sep 19, 2002 3:00 pm
- Location: Dorset, UK
- Contact:
Re: RDP KeyBoard/Mouse Control
Let's rule out the obvious first. Are these apps running as admin? Please see:
https://help.mjtnet.com/article/11-cont ... n-as-admin
https://help.mjtnet.com/article/11-cont ... n-as-admin
Marcus Tettmar
http://mjtnet.com/blog/ | http://twitter.com/marcustettmar
Did you know we are now offering affordable monthly subscriptions for Macro Scheduler Standard?
http://mjtnet.com/blog/ | http://twitter.com/marcustettmar
Did you know we are now offering affordable monthly subscriptions for Macro Scheduler Standard?
-
colin.rogers
- Newbie
- Posts: 11
- Joined: Sat Oct 28, 2017 11:49 am
Re: RDP KeyBoard/Mouse Control
Different access levels is indeed the root cause. The AD Users and Computers application is elevated. We are allowed to run MS as Administrator and when the levels match the application listens to the MS commands and shares its objects as well.
Once again, great and fast support from Marcus and the team, for which we are always grateful. Thank you.
Once again, great and fast support from Marcus and the team, for which we are always grateful. Thank you.
