|
|
|
18 Jun 2010
Comments:1
Desktop virtualisation or Virtualised Desktop Infrastructure (VDI) is a technology which I think everyone is talking about. Operating systems and applications are not directly installed on user desktops but on servers, so IT managers have an easier time managing individual desktops.
Nothing changes for the user but the fact he or she is actually accessing an image, or virtual representation of the system, linked to the datacentre where the system is hosted.
A company with 1,000 traditional PCs running Vista can use VDI and do the migration in a few server-based clicks. The ultimate solution of course is to deploy thin clients, which are cheaper and need less energy.
All this sounds great but there are a few things holding back wider adoption.
At first glance, VDI looks suspiciously similar to old-school server based computing, application virtualisation or application publishing. Server based computing has applications working on remote servers and relaying the virtual image to the user’s desktop, but the applications are virtualised rather than the whole operating system.
Server based computing is used to manage application lifecycles, especially for installing the latest software updates, whereas VDI generally keeps the applications anchored within the operating system.
Many of our customers have told us that they were impressed by the potential of VDI but have given up after an initial test, because they struggled to maintain applications or to reach the same level of service that they enjoyed with the ‘old’ server based computing.
Another disadvantage is the cost of VDI deployment when migrating to a new OS. Storage costs are quite high for VDI but nonexistent for server based computing. An office with 200-300 seats needs at least 10GB, and 1GB of RAM for each user.
Server based computing only requires 200MB of RAM, and no storage space for the desktop.
I think that VDI makes most sense combined with server based computing. You get the ability for complete desktop personalisation by user need, and total OS compatibility.
This means adapting your approach to virtualisation according to your customer’s needs. You can start by centralising and virtualising applications, then do desktop virtualisation for individual cases where server based computing does not suit.
Even when using desktop virtualisation, you can use server based computing to maintain application lifecycles inside the virtualised desktop. And user needs are becoming ever more diverse.
Virtualise your applications as soon as possible, then introduce desktop virtualisation gradually in response to specific needs.
Christophe Corne is founder and chief executive officer of Systancia
In this video find out about the fast-growing Chinese vendor's plans for market domination and how the channel is its route of choice
Find out what gifts Acer has in store for partners for 2012 in this exclusive roundup of its recent conference
CRN's premier networking event is back on 17 May at the Ricoh Arena
Date: Thu 17 May 2012
Channel fighters preparing to square up once more on 24 May
Date: Thu 24 May 2012
The proliferation of endpoint devices within the enterprise has highlighted the shortcomings of one of the traditional approaches to data security
This Forrester report compares the costs and benefits of legacy email and productivity software with Google Apps
Dave discovers that rozzers are seemingly living in the technology dark ages
Mark Needham, founder of distributor Widget, argues that John Browett leaves for Apple with Dixons in better shape than when he arrived
|
|
|
Do you agree?
VDI is a niche
VDI (i.e., centeralised virtualised desktops) is a niche deployment method that suits a very small number of cases, i.e, disposable desktops (e.g., training labs) and off-shore developers (banks mostly).
The major barriers are the high TCO and the user experience. The truth of the matter is most of the benefits can be more easily obtained using less radical deployment approaches.
A better approach is to implement a dynamic desktop, where the users resoruces are dymamically assembled when the user logs in. This requires data redirection, roaming profiles, AD GPO and app virtualisation. Most orgs have done the first 3 and just need to implement app virtualistion.
When done this way the users desktops can be dynamically assembed when they log-in to a desktop/laptop, a termainl services session or a VDI session. These deployment methods can all use the same dynamic desktop approach
http://ibrs.com.au/index.php?option=com_mtree&task=viewlink&link_id=1680&Itemid=10&cat_id=144
Posted by Kevin McIsaac | 18 Jun 2010
Have your say