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.
After 5 years and several "started" and "under review" tag changes I would like to hear, if anything is on the way!?!
Yes, there is one approach: the bridge extension. But it isn't really usable for our case. In this thread there are really good ideas for integrating RDP that would give much more opportunities for using connectwise control!
I had a similar idea. Other members of my small team (6 I.T. staff total, supporting 350ish personnel) have a habit of using ScreenConnect to remote in to servers or other devices where there is no user to support, where an RDP session would be much more secure and also not consume a license. When I suggest that they stop this, the response tends to be that the list of machines within ScreenConnect is just much more convenient than manually typing in the computer name into MSTSC.
I'd like to see a join option (for Access sessions) which triggers an RDP session directly between the host and the guest. (If there is no direct network connectivity between the two, then perhaps fail over to a standard ScreenConnection session? Or just let the host know that it failed and they can do a SC connection manually.)
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.