Some important notes:
When running GUI tests via Remote Desktop, do not do the following:
One way we got around this was using VNC to remote into our test lab machines and kick off the tests. The VNC services would keep the remote UI active for us while we were disconnected. We did find it to be a little slower to interact with the desktop, but it didn't seem to slow the tests down.
There is one more thing I have noticed,
1) The execution is running seamlessly when the local machine is Windows 7, but if the local machine is Windows 10 and if we lock it, all our test cases are getting failed after the timeout delay
Note: Remote machine was Windows 10 in both the above cases
A workaround that works sometimes is to open remote session (B) within another remote session (A) running on your local machine. Quite often session B is not getting locked when the local machine is locked.