Microsoft Virtualization Secrets

Architecting a Microsoft VDI Solution

This chapter focuses on the Windows Server 2008 R2 VDI implementation, which was a new feature in Windows Server 2008 R2 and is part of the Remote Desktop Services role. Remote Desktop Services (RDS) was previously known as Terminal Services prior to Windows Server 2008 R2, which focused on session-based virtualization. Terminal Services was renamed to show the shift in focus from pure session-based virtualization to session-based and VDI scenarios.

Reviewing the Components of a Successful VDI Implementation

Figure 11-1 shows users whose devices are directly connected to a virtual machine. Although this is a basic form of VDI, it is completely impractical and likely wouldn’t work in the real world. For a successful VDI implementation, a number of components are needed:

• Machine virtualization to host the virtual machines
• Virtualization management to enable the creation of virtual machines, to stop/start them as needed, and to pass information back to the VDI components
• Client platform to run inside the virtual machines, such as Windows 7 or Windows 8
• Access protocol to communicate with the virtual desktop OS, which is Remote Desktop Protocol
• Session Broker to decide which virtual desktop a user should be connected to and to remember which desktop a disconnected user was last using
• Gateway capability for users connecting from outside of the corporate network, avoiding the need for virtual private network (VPN) connections
• Licensing (Yes, you ...