Comments by AsmoconX (Top 8 by date)

Sergey,

Thank you for all the time put into your reply. I have been reading a lot of the links and looking into the Windows Hooks methods.

On a side note, I realized a lot of the confusion from my original post was due to wording. I changed the original post to use the correct Host/Client terms, so that if anyone else reads it, it will make more sense for what I was doing. Thank you for pointing that out!

I do not know if I will actually get this resolved anytime soon, but again, I appreciate your time.

This is a test environment and information is not meant to be added or modified on the remote systems (for validation and testing requirements). The test-process requires us to login to the system using a Remote Desktop Connection and perform a set of tests within that Remote Desktop Environment (Again, the remote system does not have other connection methods such as USB, PS2, VGA, etc..Just a console network line plug). The remote PCs already have the operating system installed, configured, and have specialized test-programs pre-loaded onto them that must be ran for validation purposes.

After we login to the remote system, we perform multiple days worth of tests using the software already on the remote system.

The end-goal was simply to find a way to let individuals know when a test has completed or had an error. The program would be able to detect that completion/error window within the remote desktop window and turn on a light, send an email to the operator, and various other things.

There can be 20 different systems testing like this and each Test-PC must be monitored to see when it is time for a new action. So, the final objective is to reduce the time lost because a person is unable to go turn on each monitor, check the remote display, act if needed or turn display back off and continue check the other displays. If the event could be relayed, like I was saying through a program that was monitoring the remote window, they would not be occupied checking systems that may not even require attention yet.

I honestly do not know how else to explain it. :(

So, your comment of there is no way to interact or relay this information without having a specialized program is essentially the answer. :( Since the Remote system can not be modified, I do not have a way to communicate the window information back to the Test-PC.

This part was unknown and all other code was finished (logic for alerts, sending notifications, etc, etc). Feels crazy that there is no way to interpret events within the RDC window. :(

Test PC -- Uses Remote Desktop Connection to Connect to Remote PC. The Remote PC has specialized files already on it, that must be ran to validate configurations and components.

The person on the Test-PC is controlling all of the tests to run via the Remote Desktop Connection (using mouse clicks and keyboard commands, etc). The hope, is that the person could start a program on the Test-PC that will monitor the actions happening inside that Remote Desktop Window, so that if a test is finished [during test completion a Event Window is displayed], the program will detect that Event Window inside the Remote desktop Window and cause an event notification back on the TestPC.

{TestPC}-----------(remote login)----------{Remote PC}
Program Runs --------------------------- Event Happens
Programs Detects Event ----------------- (no changes)
Program Sends Event Notification ----- (no changes)
User Interacts ---------------------------- Event is manually cleared by User