It seems since late 2007 and early 2008 some virtualization players are still trying to hop on the VDI bandwagon started by VMware back in 2005. Since 2007, Citrix has been feeling the squeeze from the top by Microsoft with 2008 Server and Remote App around the corner, and squeezed at the bottom by VMware and the momentum of VMware VDI. Citrix had to do an about face on the Application Delivery strategy and messaging by getting in the VDI game with the purchase of Xen Source; an attempt catch up by trying to deliver desktops.
It also appears based on the recent release of a White Paper titled Virtual Desktop Infrastructure, SWsoft would like to ride the VMware VDI tailwinds. After reading this short overview on VDI, I wanted to offer some additional things to consider for readers that come across this paper.
“There are five components that comprise the VDI solution.”
A properly designed VDI solution is going to include more than five components. At a minimum, a proper VDI solution will encompass the following:
- Client Access – Fat Clients, Thin Clients, Repurposed PCs and or Mobile / Remote
users. - Virtual Desktop Management Services – Connection Brokering, Session Management and desktop provisioning such as what’s provided with VDM 2
- Virtualization Services – Such as what’s provided by VMware Virtual Infrastructure 3 including tools such a HA, DRS and VMotion that simplify the operations of a Virtual Desktop Infrastructure.
- Virtual Desktop Instances – Such as Windows XP and Vista
- Infrastructure Services – Such as Active Directory, File and Print, Email, employee portals etc.
- Application Virtualization Services – The legacy tools such as Citrix and Terminal Server used for delivering applications as well as next generation Application Virtualization tools such as Softgrid, SVS and ThinStall.
- Management Services – Such a VirtualCenter and other existing desktop management tools for patch management and software distribution such as Altiris, and SMS.
- Storage Services – The storage infrastructure for storing and managing the desktop images and data being centralized.
- Integration Services – The services and support provided to successfuly design, implement and integrate all
these components, such as those provided by VMware.
“The simple purpose of the connection broker is to manage the end user connection with the virtualized desktops.”
The purpose of a broker is not simple. The role of a broker is very important in enabling VDI. At a minimum, a broker's offering should include:
- Virtual Desktop Management
- Session Management
- Desktop Life-Cycle Management
- Desktop Provisioning
- Desktop Pooling
- User management and entitlement to virtual desktop resources
- Providing secure encrypted connections across un-trusted networks
All these thing and many more will be provided by VMware VDM 2. Customer looking for other alternatives can also leverage solutions from our VDI Alliance
partners that closely integrate with VMware VI3.
“VDI is a new technology that gives IT departments some choice and control over how to manage their exploding desktop infrastructure.”
VDI is not new technology. VMware customers have been deploying VMware VDI based solutions since 2005. I would say most the IT organizations I meet with do a really good job managing desktop systems. Although, they are looking for a better way to deliver desktop services, gain more control over their desktop architectures and inprove deployment and management efficency. Distributed desktop architectures are difficult and costly to manage, but I do not expect any explosions.
One area glossed over in this paper were Virtual Desktop Instances. One of many key driving factors increasing the adoption in VMware VDI, is the ability to virtualize and deliver Windows XP and Vista desktops. Doing so allows IT organizations to overcome the shortcomings of typical server based computing solutions such as Citrix Presentation Server and Microsoft Terminal Services, where application conflicts and the loss of the personal computing experience often inhibit mass adoption as the desktop environment.
According to the following requirements http://kb.swsoft.com/en/1446, SWsoft does not support or deliver Windows XP or Vista desktops. Providing each user a Windows 2003 Server is a costly proposition. If the proposition is to virtualize each server instance and then use Terminal Services, most people have come to agree that is not VDI, but rather consolidating Terminal Servers which are typically underutilized. Although Terminal Servers can be of value and Remote App is showing a lot of promise in extending the value of a VDI architectue; alone they do not offer all the benefits of a true VDI solution, to organizations with complex applicaition environments.
I know of no company that has done the jump to full VDI with full-featured thin clients, desktop broker, HA/DRS on a blade system and a finally good storage concept. Our company has been doing 1:1 "VDI" since the days of GSX server but in my view this is not VDI because the 'I' in VDI is all bone no flesh.
I have to agree with your comments...
I have heard at VMworld 2007 that they wanted to be in the VDI market and I had the same wonder you had .... how can they do that if they don't support XP? In fact what they want you to do is to use a WIndows Server dedicated (i.e. not TS shared) VE (Virtual Environment) for every user. The only advantage I see here is that they might have less overhead running a VE than you might have running a VM but the limitations are clear. Two above all in my opinion:
I have never been a fan of OS virtualization ..... obviously I can't be a fan of it for VDI .... at least the way it is right now. But hey ... VDI appears to be the next cash cow for the vendors (VMware included) so no matter what .... they want to get onto THAT wagon .....
My 2 cents.
Massimo.