5 . The user needs an initial RDP connection point, since their VDI client VM
destination will not be known yet unless the user has a personal desktop
configured. The RD Connection Broker acts as the connection point for the user’s
RDP connection and then redirects the client to the true endpoint, the VDI session.
The RD Connection Broker knows what the RDP target should be for the
requesting client.
6 . The RD Connection Broker communicates with the Remote Desktop Virtualization
Host role service that is enabled on the Hyper-V boxes to check the state of the
VMs, start the VM if required, and gather any needed information such as IP
address of the client VM OS. This information is then passed back to the RD
Connection Broker, to the RD Session Host in redirection mode, and then back to
the client.
7 . The client now makes an RDP connection to the destination client VM via the RD
Gateway (if connecting from outside the corporate network), and the connection is
complete. The logon process for the user would now be complete.One part I haven’t mentioned is the role of System Center Virtual Machine Manager,
which while not a requirement, definitely helps in the management of the virtual
machines and helps automate the bulk creation and updating of virtual machines.
Next you’ll spend a little time looking at each component in a bit more detail. It
should go without saying, but all of the roles can be virtualized on Hyper-V, and it is
common practice to do so.
RD Web Access
The RD Web Access role provides the initial entry point for users; it provides a web-
based interface to select the desired VDI or published desktop/application target.
While not absolutely required, this helps give a simple-to-use portal that supports
form-based authentication, provides single sign-on, and differentiates between public
and private computers for credential caching. The Web Access portal utilizes HTTPS to
protect the credentials that are passed and could be made available to the Internet
through publishing enabled by gateway services such as Microsoft User Access
Gateway.
Although not directly part of RD Web Access, Windows 7 introduced RemoteApp and
Desktop Connections, which allows a feed from RD Web Access to populate the same
content shown in the website directly into the Start menu, avoiding the need to use
the website. The standard URL is https://<RD Web Access
server>/RDWeb/Feed/webfeed.aspx.
This was continued in Windows 8 and beyond as a Control Panel applet and extended
with the new Remote Desktop windows application available from the Windows Store.
The Remote Desktop application enables easy access to the feeds provided by RD Web
Access. The Manage RemoteApp and Desktop Connections setting in the application
enable a new connection to be added, as shown in Figure 11.4. Previously, either a web