Understanding the Virtual Desktop Lifecycle - Part 1
By MrDGrobler on Feb 11, 2008
Why is desktop virtualization such a big topic in the industry today? Because it has a lot of potential. Potential in terms of better security, more mobility, better hardware utilization and improved manageability. Specifically the last item is of course interesting for the administrator. And, improved manageability in itself has a lot of different aspects. Starting today I will start a serious of small articles that will focus on the improvements and simplifications that can be achieved through desktop virtualization. So I will concentrate on finding some answers to questions like: How do I deploy a virtual desktop on a VDI platform? Where is it different compared to a traditional PC deployment? Does it need to be different?
So let's start with the last question first. Is a deployment of a virtual desktop necessarily different than a real desktop? - Note with desktop a Windows XP or Windows Vista desktop is meant. The fundamental answer is 'No. Absolutely not.' Only the location is different. This is now the data center instead of the PC in the office. But the rest can remain the same in terms of how you create the desktop, how you upgrade and secure your desktop, how it is connected into your infrastructure. An essence you create a virtual PC that you handout to a user. And each user can 'own' his desktop. A scenario that is probably most common for todays Windows XP deployments. This deployment is also often referred to as a static deployment.
The static deployment of virtual desktops already provides a lot of advantages compared to a traditional deployment as the user can connect from different locations to his 'static' virtual desktop through a remote connection like RDP. And of course the user's data resides in the data center. Besides, the complexity with different types of PCs goes away, specifically dealing with the differences in hardware and the required drivers, as there is basically only one type of virtual HW presented to the Windows guest OS.
Deploying virtual desktops statically is a good start into the world of VDI and does not require to change a whole lot in your Windows infrastructure. But there is more potential for automation of desktop deployments in VDI. Wouldn't it be great if a desktop just gets created instantaneously when a user first logs in? Wouldn't it be great if a desktop automatically expires and is deleted after a defined period time? This would help so much better to adjust to changing workload and improve the hardware utilization. It also might change your whole patch model. So is there still a requirement to update a running instance of Windows XP and the embedded applications? Not necessarily. It could also be an option to delete existing instances and create new ones based on an updated golden image, also called template in the world of virtualization. And this is the core idea of an automated desktop lifecyle also referred to as dynamic desktop deployment.
In upcoming blog entries I will discuss the concept of an automated desktop lifecycle, I'll dive down to techniques and parameters to control the process based on the Sun Virtual Desktop Connector 1.0 and finally will provide a couple of use cases, that might help you to identify when dynamic deployment is actually useful in your remote desktop world.
So stay tuned!