If one of our employees wants to work from outside we give them access through ScreenConnect to their PC in the company. With WOL they are able to turn the PC on at any time they want.
A better way would be if ScreenConnect could initiate a new RDP session on a given terminal server where the user can logon with his credentials so that there is no need to use of an extra PC.
+1
We need to keep using RDP for server access for both the ability to have two simultaneous active/connected tech sessions as well as the ability to leave virtually unlimited number of disconnected tech sessions with processes running.
While we still need to be able to reconnect to our old disconnected RDP/console sessions through Control without getting hit with the consent requirement (which we only need for end-user computers), this gets us part of the way there.
If we could exclude the consent requirement from applying to disconnected RDP sessions as well as console sessions that are at the logon screen, we would be literally jumping up and down with excitement over here
Many times, we connect to server console sessions that are locked or in use. We would like the option to create a new session, by default, on specific servers or groups of servers, instead of connecting to the console.