Why Windows does not create handle window the minimized RDP?

Good day!
Use the tools based on AutoIT and WinAPI directly for automated Windows application through its GUI. Faced with the problem, let's connect via RDP to a remote machine, launching it to the script and it starts working with the application (click buttons, open Windows, etc.), all the work is based on the fact that we know the handle of the window and I worked with him by sending messages through WinAPI window (for example the SendMessage function), but if I minimize the RDP connection on remote machine Windows stops to give the handle of the window you are working with the robot. A similar situation occurs when the RDP window is open and everything works correctly, but after 15 minutes of idle time the parent OS (which is open RDP connection) turns off the display and locks uchetku (this security policy we have).

Question in what, is there any way to configure Windows so that it always gave the handle of the window, even if the monitor is turned off, and the parent OS in sleep mode (the remote machine it works).
June 5th 19 at 21:28
3 answers
June 5th 19 at 21:30
Solution
IP KVM, VNC, Teamviewer or any similar
Or to put the hypervisor
Have checked the following diagram of My machine <-RDP-> Machine on the hypervisor (WinServ2012) <-RDP-> Client machine (Win7)
In this configuration, even if the RDP connection between my machine and a machine on the hypervisor is closed, or even my PC is off, then the Client machine with Win7 thinks the monitor is there and displays all Windows (the main thing that session on the machine with the hypervisor was active, i.e. do not Log Off, and not to break the RDP connection with client machine). Similar to the hypervisor or server OS has some feature. - Elnor commented on June 5th 19 at 21:33
June 5th 19 at 21:32
Why Windows does not create handle window the minimized RDP
Because there is no window.
And there is no window, no handle.
Connect locally or via Teamwiewer and won't be a problem.

Windows is a graphical interface for the user. They are only created when the user works in the system.
If you are logged in locally - you'll be in the system until you click the button to log out or shut down the system.
If you are logged in via RDP you will be in the system until an active RDP session, once it becomes inactive, for example you closed it, or just turned the system ceases to serve a graphical user interface for the user.
Although the running processes continue to work.
June 5th 19 at 21:34
The problem is deeply buried:
rsdn.org/forum/asm/3361089.all
I should add - might help the RDP connection to the console: mstsc /admin - Elnor commented on June 5th 19 at 21:37
Well, thank you! Today will be dripping in this direction can really help) - Lucio commented on June 5th 19 at 21:40

Find more questions by tags WindowsAutoIt