Full encryption where required, using 56- or 128-bit keys, enabling FIPS
compliance where needed and Network Level Authentication (NLA) to ensure
authenticity of both the server and the client
Clipboard, drive, port, device, and smartcard redirection. Certain types of devices
can be redirected to a remote session in an abstracted fashion, which avoids a
driver having to be installed for the specific hardware on the remote server.
Devices with in-boxes such as cameras are great examples.
Port-level USB redirection with RemoteFX, enabling any USB device to be
redirected to a remote session. However, because the redirection is at a port level,
the driver for the USB device must be present on the remote server, and the device
is available only to one remote session at a time and is no longer available to the
local client.
RDP 8 added automatic network detect, removing the need to select the type of
network manually in the Remote Desktop Client.
RDP 8 added UDP and TCP support to provide the best possible experience over
different types of networks.
RDP 8 added multitouch support with up to 256 touch points (and of course
RemoteFX Multi-Touch offers a richer experience where available).
RDP 8 adds the ability to have nested RDP sessions.
RDP 8.1 provides dynamic monitor and resolution changes, which supports
automatic changing of the display in the remote session as the display of the local
client changes; for example, rotating a table or adding a second display.
RDP 8.1 improved transparent windows and moves/resizes of RemoteApps on the
local device.
RDP 10 adds support for AutoSize zoom. When connecting to older operating
systems from a HiDPI client, the remote session would look very small; the Zoom
option is available through the RDP icon of your connection.
RDP 10 adds pen remoting, which enables native pen functionality in the remote
session instead of the pen being projected to the remote session as mouse actions.
RDP 10 adds the aforementioned 4:4:4 codec support.
RDP 10 adds Remote Credential Guard (often called Remote Guard), which as the
name suggests helps protect credentials from attack on a remote system. It does
this by keeping the credential locally on your box and not sending it to the remote
system. If you try to access another system from the remote session, your local box
will request the required tickets for access.To summarize, as you look at RDP, it is not a basic protocol anymore. It has a huge
array of features, it works well over WAN connections, and, even better, Microsoft
now provides RDP clients not just for Windows (including the nice-to-use modern