Greetings, folks...
I am using MacrosScheduler to execute a RemoteApp. I can successfully open the RemoteApp by using the following commands:
Change Directory>C:\Users\aaa\Desktop
ExecuteFile>"C:\Users\aaa\Desktop\bbb.rdp"
Once my RemoteApp is open, I cannot seem to get the WaitWindowOpen command to work.
SetFocus>ccc (Remote) has been applied and is working fine. Within ccc (Remote), WaitWindowOpen>ddd is being applied but is not working. ddd resides inside ccc (Remote).
Is it even possible for MacroScheduler to recognize windows within a RemoteApp? If so, how do I get MacroScheduler to acknowledge those windows?
Thank you.
WaitWindowOpen inside Remote Connection
Moderators: JRL, Dorian (MJT support)
- Marcus Tettmar
- Site Admin
- Posts: 7395
- Joined: Thu Sep 19, 2002 3:00 pm
- Location: Dorset, UK
- Contact:
Re: WaitWindowOpen inside Remote Connection
That's not possible.
Remote Desktop works by sending screen images in one direction and mouse/key events in the other. The technology (e.g. the windows etc and whatever makes those windows) are unknown to the client.
You can for example remote to a windows 12 machine from a linux machine and vice versa. They don't share technology.
Something running on the client has no knowledge of the internal workings of the things on the server. All you have are visuals - screen images. The server sends back screen images, refreshing whenever the screen changes, and the client sends mouse and keyboard events. That's it.
For Macro Scheduler to "see" a window title within the server environment Macro Scheduler (or the macro) would have to itself be running on the server.
But if you need to automate a remote application across the remote desktop window then you are limited to sending keystrokes/mouse events and using image recognition.
Remote Desktop works by sending screen images in one direction and mouse/key events in the other. The technology (e.g. the windows etc and whatever makes those windows) are unknown to the client.
You can for example remote to a windows 12 machine from a linux machine and vice versa. They don't share technology.
Something running on the client has no knowledge of the internal workings of the things on the server. All you have are visuals - screen images. The server sends back screen images, refreshing whenever the screen changes, and the client sends mouse and keyboard events. That's it.
For Macro Scheduler to "see" a window title within the server environment Macro Scheduler (or the macro) would have to itself be running on the server.
But if you need to automate a remote application across the remote desktop window then you are limited to sending keystrokes/mouse events and using image recognition.
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?
Re: WaitWindowOpen inside Remote Connection
Are you saying that... if I were to continue running MacroScheduler on a PC and moved the macros themselves to the Server, that this would all work?
- Marcus Tettmar
- Site Admin
- Posts: 7395
- Joined: Thu Sep 19, 2002 3:00 pm
- Location: Dorset, UK
- Contact:
Re: WaitWindowOpen inside Remote Connection
For the macros to run on the server they would either need to be compiled, or Macro Scheduler would also need to be installed on the server. But yes, you would then have those macros running locally to the server and therefore they would have lower level access to the applications and windows and objects etc.
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?