A Generic Server-Based Desktop Architecture

All server-based desktops require similar infrastructure. This illustration shows the client and data center components of infrastructure that provide users with server-based desktops (top), which could be running in server virtual machines (VMs) or in server sessions.

Client software (1) on the user’s device (left), such as Microsoft’s Remote Desktop client, finds and connects to the user’s server-based desktop in the data center (right).

A protocol (2), such as Microsoft’s Remote Desktop Protocol or RemoteFX, sends keyboard and mouse actions to the server-based desktop and sends images or the display of the executing application from the server-based desktop to the local device’s display.

A menu of server-based desktops (3) is provided by gateway software such as Microsoft’s Remote Desktop Gateway. The server-based desktops available to the user are determined by the authentication and authorization component (4), which is typically Microsoft’s Active Directory.

A broker (5), such as Microsoft’s Remote Desktop Connection Broker, prepares the user’s server-based desktop and finishes the connection between her client device and the desired server-based desktop based on her selection from the menu.