The changes in Windows Server 2008 to Terminal Services as a platform were the most significant changes in Terminal Services since its integration into the Windows (Server) products. Windows Server 2008 R2 marks a similar start of the inclusion another functionality into the base Windows Server OS: VDI. In this article we will be looking at exactly how the “VDI functionality” in Window Server 2008 R2 works and what it exactly offers you (and what it doesn’t).

With Windows Server 2008 R2, Microsoft has taken their first steps into the VDI space. These first steps look and feel like solid and confident steps. We should however be honest and objective, though, and establish that these steps are but small steps. This should absolutely not be a surprise, since Microsoft has specifically mentioned that the VDI functionality in Windows Server 2008 R2 is aimed at small and non-complex environments. I am sure that this functionality will be enhanced in future releases. This is similar to what Microsoft has been doing in the Terminal Server/ RDS space for many years now.

To do VDI on any other scale beyond the scope of “small and non-complex environments” you would definitely need additional third party “VDI products” (like –in no particular order- Quest vWorkspace, Citrix XenDesktop or any other Hyper-V compliant VDI solution) and other Microsoft products (like SCVMM R2).

Source: http://www.brianmadden.com/blogs/michelroth/archive/2009/08/26/taking-a-closer-look-at-the-vdi-functionality-in-windows-server-2008-r2.aspx