Commentary

Charles Babcock
InformationWeek  

A First Step Toward End User Virtualization

The savings that flow from server virtualization are well known and accepted. The potential savings on the client side, I believe, are even greater. But that premise is much less widely accepted, and even less frequently implemented. Perhaps virtualizing end users one application at a time is the way to go.

The savings that flow from server virtualization are well known and accepted. The potential savings on the client side, I believe, are even greater. But that premise is much less widely accepted, and even less frequently implemented. Perhaps virtualizing end users one application at a time is the way to go.When it comes to virtualizing clients, IT managers take a step back and hunker down. Even if they can find the right connection broker and identity and authentication servers, there's still the issue of providing a satisfactory end-user experience. And those pesky end users sure let you know about it when the experience isn't satisfactory. If there's no clear solution, who needs to volunteer for that headache?

So client-side virtualization thus far has been a nonstarter. There are still just too many issues to resolve. If you try to store everyone's individual desktop as a virtualized file on a central server, then you will have increased storage costs and maybe, or then again maybe not, decreased client costs. Who wishes to be first in demonstrating how planned savings evaporate? Several vendors claim a complete solution to this problem but lack a list of high-powered customers who've adopted it.


More Storage Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Then there's the issue of not all end users are alike, so you'll need a variety of virtualized desktops, and make sure you always know how each one evolved, so you can re-create it. There are partial solutions -- some would claim whole solutions -- to these problems, but the world isn't flocking to them either. But there may be a partial solution that yields some savings while giving both implementers and end users needed experience in client virtualization.

End user applications can be virtualized one by one on central servers and made available, without virtualizing the whole desktop. A lesser-used application, such as Microsoft Project, might offer a test case of what can be accomplished and where the cost savings can actually be captured.

Or a set of applications could be aimed at a particular end-user group whose needs were more basic and more assured of being met than others. A test of the capacity of the corporate network to deliver virtualized end-user services in a manner that mimics the performance of the desktop would yield valuable information.

In a declining economy, these small initiatives may pale against the CFO's next demand for real IT savings. But the sooner IT takes some stab at desktop virtualization, the better armed it will be at confronting the task when there's no longer a choice on whether it's going to happen.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links