Hi Michael,
The response from the Dev's seems like an easy (lazy) answer, but I couldn't say what the "Full Control" connection is actually using, assuming it's NOT just RDP.
The
Full Control mode is Remote Utilities's own connection mode that allows you to view the remote screen, manipulate the mouse cursor and send keystrokes.
RDP is Microsoft's technology and the acompanying software (Remote Desktop Services) that does the same.
The
RDP mode that you can see in Remote Utilities Viewer simply runs the Microsoft's RDP client, nothing more. This has been added long ago for convenience - many admins prefer using RDP in many situations even if they have an RU license.
It should be noted that sometimes people use the word 'rdp' (as a verb) even if they don't actually use RDP (the technology). They may say that they 'rdp to a remote computer' meaning that they are actually using whatever remote control software they have at that moment, including Remote Utilities' Full Control mode. That may produce some confusion.
I found this post as I now have 3 Pro licenses and was researching why 1 out of 10 times it won't let me connect to the session when I connect in "Full Control" mode.
We should examine the Host logs to tell why this might be happeing. This can be as well a network/connectivity issue which has nothing to do with terminal sessions.
Thanks.