Microsoft Desktop and Session Virtualization
Technologies
To offer a virtual desktop solution, whether session virtualization or VDI, various
components are required to complete the solution and enable connectivity from end
users:
Machine virtualization to host the virtual machines (for example, Hyper-V)
Virtualization management to enable the creation of virtual machines and
stopping/ starting them as needed in addition to passing information back to the
VDI components
Client platform to run inside the virtual machines, meaning Windows 10
Access protocol to communicate with the virtual desktop OS, which is Remote
Desktop Protocol for native Windows
Connection Broker to decide which virtual desktop a user should be connected to,
which could be via session virtualization or VDI, and to remember which desktop a
disconnected user was last using for reconnections
Gateway capability for users connecting from outside of the corporate network and
avoiding the need for VPN connections or technologies like DirectAccess
LicensingIn this section, I walk you through the typical process of connecting to a hosted
desktop in a Microsoft VDI implementation and demonstrate the Microsoft role
services used and how they interact. Figure 11.3 depicts the major steps required for
VDI functionality, from the initial user contact all the way to a usable VDI session
with an empty Windows 10 operating system. If using session virtualization, the flow
is similar, except that the endpoint for the virtual desktop is a session host instead of a
virtual machine; in addition, step 6 in the flow is not performed.