

To take advantage of RD Connection Broker and the intelligence it brings to managing the VDI, users must connect to virtual desktops via the RD Web Access service ( Figure 1). Once a user has selected their personal virtual desktop or a virtual desktop pool, the request is passed to the Remote Desktop Gateway, which establishes a secure connection to RD Session Host. Users cannot connect to virtual desktops negotiated on their behalf by the RD Connection Broker without using RD Web Access. Remote Desktop Web Access provides a web interface with which users connect to remote virtual desktops.

When you install Remote Desktop Virtualization Host on a server, Hyper-V will be installed if not already present. Remote Desktop Virtualization Host is new to R2 and installs on the Hyper-V box, monitoring and preparing VMs as directed by the RD Connection Broker. Remote Desktop Connection Broker provides the brains of the VDI solution, sending requests to the Remote Desktop Virtualization Host to resume VMs and manage user sessions in virtual desktop pools.

When RD Session Host is configured to provide remote access to virtual desktops (redirection mode), it cannot be used to connect users to standard terminal server desktop sessions.

Remote Desktop Session Host works with Remote Desktop Connection Broker to provide Remote Desktop clients with an IP address for a virtual desktop. New role service names for Remote Desktop Services in Windows Server 2008 R2 Windows Server 2008 All the other related role services have been renamed as follows: The Terminal Server role service in R2 is now called Remote Desktop Session Host.
