EMA Webinar Transcript:

Virtualization 2010: A Resource Guide for Desktop

Virtualization

Webinar Date:

1/28/10

Featured Speakers:

Andi Mann

Calvin Hsu, Director of Product Marketing, Citrix

Abstract:

Desktop Virtualization is one of the most loaded terms in the IT industry – and perhaps

one of the most misunderstood. What is this technology? How is it really used? What are

the benefits customers are seeing today?

Find out when you join EMA VP of Research Andi Mann and Citrix Director of Product

Marketing Calvin Hsu as they explore how and why companies are successfully

deploying desktop virtualization, their real world experiences, lessons they have learned,

key drivers and barriers they have overcome to make desktop virtualization a reality in

their organizations.

In this one-hour Webinar, you will learn:

>>The technologies that make up desktop virtualization

>>The actual cost savings you should expect to see

>>How to kick start your desktop virtualization deployment

>>How to identify and overcome the top 5 barriers to success

>>How to choose the right solutions for all of your different user requirements

>>How to get started

With multiple case studies and best practice advice for managers on resourcing,

deployment, key use cases, expected outcomes, project execution, ongoing management,

handling departmental politics and more, this Webinar will provide a deep and lasting

resource for any organization that is considering, implementing, or struggling with

desktop or application virtualization.

Introduction:

Welcome and thank you for joining us today for Virtualization 2010, a resource guide for

desktop virtualization. My name is (inaudible 0.10.0) Gould and I will be your

moderator for today’s events. Our feature speakers are Andi Mann, VP of research at

Enterprise Management Associates, and Calvin Hsu, Director of Product Marketing at

Page 1 of 17

Citrix Systems. Andi Mann has over twenty years of experience across four continents

with large scale enterprise systems software on mainframe, midrange, server and desktop

systems. He has worked within the IT departments of various global corporations and

with several enterprise software vendors, leading diverse technical, sales and marketing

teams. At EMA, Andi focuses on the intelligent and automated management of IT,

specifically surrounding systems and application management, configuration

management, provisioning, and virtualization of systems applications. Calvin Hsu leads

the product marketing team for Citrix in desktops. Calvin has eighteen years experience

in (inaudible 1.09) technology marketing and management, ranging from federal

government information systems to enterprise virtualization infrastructure. Since joining

Citrix in 2004, Calvin has been part of the (inaudible 1.19) as in desktop products teams.

Calvin holds a degree from the Warden School of Business at the University of

Pennsylvania.

Now before I go ahead and turn things over to our featured speakers I did want to very

briefly mention some logistics for today’s event. We do encourage you to log your

questions at any time using the Q & A functionality located in the right hand column of

your screen. If you’re in full file view, simply look for the floating toolbar, you should

see a question mark icon, simply click on the icon and you can log your questions that

way. Andi and Calvin will be dedicating the last ten minutes or so to answer your

questions, so I do encourage you to take advantage of that opportunity. Also, today’s

event is going to be recorded and available on demand, as well as a pdf of the speaker

presentation, so I will be sending that out in email early next week.

And now I’m going to go ahead and turn things over to our first featured speaker, Calvin

Hsu. Calvin?

Great, thanks very much. So, to begin this webinar and the session, I know Andi’s got a

tremendous amount of data and market information around desktop virtualization. I

thought what I would do is, sort of set the stage a little bit, and you know talk about us as

vendor in this space, you know, what sorts of things we’re seeing from our customers,

what sorts of drivers that are coming around the corner. And chief among these things is

the Windows 7 upgrade motion, things that are on a lot of people’s minds that are

happening very rapidly here – 2010 by all accounts is going to be the year when

Windows 7 projects kick off, and in many cases complete. So what we’re seeing is that

there’s this interest in desktop virtualization along with the interest of the modernization

of the desktop itself. And combining those projects and those initiatives, and to

understand how they interplay with each other, and how they can help each other, what

kind of synergistic things we can create out of both motions. Interestingly what we see

happening, and you know, the research is indicating, is that Windows 7 adoption, due to a

number of factors, not the least of which among them are, you know, some of the

economic slowdown over the past year, where people blame some of their PC reflex

cycles, the sort of pent up demand that’s been created for a revision to Windows XP

which many enterprises have stuck with during that period of time. Windows 7 adoption

Page 2 of 17

is going to be, in order of magnitude, faster and more steeply adopted throughout the

enterprise than previous migration.

So in this talk we’re showing, in the blue and the green, the sort of expected path for, or

you know, the actual path for Windows XP adoption, and they’re comparing that to what

we really expect to happen in the next few years for Windows 7 and I can see that it’s a

much steeper, much faster penetration across the organization. So, you know, as that’s

happening, there are lots of concerns that cross people’s minds, all right? We hear all the

time, are there points of exposure during this transition that change the way I need to look

at security? Are there things that I wish I had done during the XP error and that now I

want to be able to address under Windows 7? Will we even be able to do it? I have

increasingly dispersed work forces, as well as both internal and external, people in the

work force – how do we manage all those things as well as the increasing diversity of

actual end point devices? And now some of those are not actually being owned by the

organization, the IT organization, perhaps being run by a contract or a third party.

Certainly at the C level, you know, what about the impact of productivity? That’s always

a concern and you know, how do we smoothly move to through a migration while

enabling people to quickly adapt to the new environment, have all their applications that

they need, and, you know, should I be considering alternatives to the traditional way that

maybe I did desktop refresh in the past, rather than just adopting the new desktop OS

whenever it has to change over the hardware, is there perhaps a smoother, more efficient

way that I can move myself over to the next platform and maintain productivity through

all that?

So if you think about it, you know, a lot of the things that were sort of emblematic of the

traditional desktop migration and upgrade, and you think about sort of four main factors:

there’s the simplicity, the flexibility, the security and changes in the security, and the

overall total cost of ownership of the upgrade period as well as going forward once

you’ve made that migration. We see sort of the traditional ways of doing things, perhaps,

you know, laptops go around, there’s certain that we’re lacking and certain things that

we’d like to do better or do better, so instead of installing applications per PC is there

something else that we can that would make it easier for us to manage the application

migration as the underlying desktop moves through, and help simplify the management

and the general cost that it takes to manage that process. You know, we’ve talked the PC

refresh, now that we’re looking at really a different era of PC’s. I mean the last time

perhaps a lot of organizations went through this with XP, you know, there was definitely

a lot of complexities, all the way through fro procurement to retirement of those

difficulties in the hardware, as well as the ongoing refresh rate costs that are required

operationally. And so a lot of room left to be desired there in some of the people’s minds

as they are planning their next steps. People are increasingly using more and more types

of end points as well as moving from one end point to another; work from home

initiatives, in some cases hotelling, you know, having generic work stations in some

organizations, you know, moving from one office or device to another. All these things

have an impact on how you do Windows migration and of how uniformly you can do it,

you know, do you want them to have the same experience when they are moving across

Page 3 of 17

these different environments and not be confused about what environment that they’re

working in when they switch from one machine to the other.

And then certainly a concern about the date, not just through the transition, but you know,

overall the whole model of having data out in end points, particularly in certain industries

that are regulated. You know this has always been a concern and people looking for new

desktop models may need help with this down the road.

So, in this context Andi is going to talk through a number of the desktop virtualization

technologies, and there’s certainly a lot of benefits that desktop virtualization can bring to

this migration process in all these areas – help centralize applications, help simplify the

way that they’re managed, be able to perhaps leverage and extend the life of some of the

existing PC’s. Then you can make that desktop migration without having to make the PC

refresh coincident at the same time. Provide a lot more device flexibility, location

flexibility, and it will also have a more effective way of bringing in that data into the data

centre and securing it and locking it down. So in this way the challenges that we see with

the Windows 7 migration and the considerations that are being evaluated, makes this

whole thing occur a lot easier, so as you’re looking through, and you know, considering

all the information that Andi has to share with you, think about how this can help with

this intending project, and certainly this is a way of reaching a lot of the PC’s in it and

fast improving a lot of the processes that you may have around those and simplifying

them for you.

And lastly, just to mention our product line from Citrix and Desktop 4 is really designed

to encompass a lot of these desktop virtualization technologies for you, so that as you’re

building our you’re plans and you’re considering the different ways that you can

virtualize the desktop, you know that you have the solution that addresses all these

different types of virtualization and provides that type of flexibility that you’re looking

for through this Window 7 upgrade period.

So with that introduction, I would like to hand it over to Andi Mann.

Thanks very much Calvin, and yeah good intro, and some really important stuff there.

I’m going to dive right in because I have a huge amount of content, so hopefully we’ll get

through it all and have some time for some Q & A at the end as well. So just what I’m

going to talk about, you can see here I’ve got a lot of stuff; end point virtualization,

desktop virtualization, we’re going to talk about what that is and some of the perceptions

that people have about very specific technologies. Then we’re going to look at some of

the fundamental differences between server virtualization and end point virtualization.

This is very much regarding desk practices in terms of ownership and project

management. We’re going to bust some of the myths around ROI; there are a lot of ROI

questions and answers out there. And looking at choosing and end point virtualization, a

solution and some of the case studies that we’ve seen – how people have been able to do

end point virtualization and desktop virtualization in various ways, and give you some

ideas around starting points for you, and even try and overcome some of the barriers to

success.

Page 4 of 17

Starting out, I’d just like to point out that end point virtualization is more than just

desktops. So you’ve got laptops and thin clients, and you’ve got end point virtualization

on mobile devices like pda’s and Iphones, kiosks in various places, on tablets indeed,

potentially even the new Ipad tablet. So, I mean EMA uses the term quite regularly – end

point virtualization – to describe all of these different points at the end of the

communication chain there, but it’s also variously known as desktop virtualization and

application virtualization. So I’m going to use a mix of terminology today, probably

mostly taking about desktop virtualization, but I’ll give you an idea of a bunch of

different technologies that end point or desktop virtualization is. Because fundamentally

it’s important to understand that end point virtualization and desktop virtualization, it’s

more than just a virtual desktop infrastructure. The virtual desktop infrastructure – the

VDI as it’s commonly known. Now that is a very common and popular methodology for

desktop virtualization and we talk about remote or server hosted desktop virtualization.

A lot of organizations will talk about server based computing, or you know, hosted

virtual desktops. There’s a lot of names for this, but it is only one form, I mean this is

where the operating system is hosted on a remote system. Normally our server and the

data system, normally our virtual machine in fact in the data centre, and accessed by the

end user across a network. Now, the client there I’ve shown, you know, a standard kind

of desktop, although it doesn’t seem to have a keyboard unfortunately. But that could be

a laptop that could be a thin client, it could be a hybrid, one of the new smart clients for

example, and so you know, that’s one method of desktop virtualization no doubt.

But there’s more – for example, you can run a dedicated system not using VM’s at all, by

putting machines on a blade typically in the data centre and dedicating an entire physical

piece of hardware in the data centre for each user, who has their own unique

environment; it’s a bit of a high powered environment as well. This tends to be a more

expensive way of doing it, but also gives you more resources, a personalized

environment, and very high availability and so forth, so there’s a lot of goodness out of

that, but again just another way of doing virtual desktops. And also the shared system,

which is the plastic VDI model, multiple desktops on the server, and using virtual

machines to deliver those desktops. Great for knowledge workers, who need a

personalized environment but they don’t need dedicated hardware for example. Then we

have the common desktop model, this is often referred to as a terminal services model.

We have multiple desktops on a server in a common environment for all users. Now this

can have issues around its capability, it can having issues around being able to present

different types of environments to each user, and it can have some issues around

compatibility, but it enables you to pack a lot more punch onto each server. And it

certainly suits very well to the process workers in a call center for example.

Then we have streaming. Now we know streaming from things like YouTube for

example, you stream a video as soon as you start to watch it. As soon as you start to play

it you can watch it immediately, you don’t have to wait for the whole thing to download.

And the same is true of the operating systems and applications. Now this is where the OS

or the applications live it on demand across the network and you actually start to use it

pretty much as soon as you start to download it, you don’t have to wait for the entire

operating system or the entire application to download to your PC before you can start

Page 5 of 17

using it. Now, because you are actually eventually downloading everything, or

everything you need, then you can even use this offline. You can cache the application or

operating system on your local system and take it away with you, which is very, very

different from the VDI model which requires that network connection back to the data

centre.

And then you’ve client hosted desktop virtualization, and then again fundamentally

different from the server hosted desktop virtualization that is typically known as desktop

virtualization or VDI. So this is where a complete operating system is running in the

client on the desktop or the laptop, and its running on top of an existing operating system,

you can see here I’ve got the logos for Windows XP and Lynnix running on top of a

Windows 7 or Windows Vista environment. You know and this suits very well with

anyone who needs those independent environments, you know, programmers,

contractors, channel sales agents who may need a dedicated environment for different

companies that they work with – insurance agents are a typical use case for this where

they work with multiple insurance companies and have a different desktop for each of

them. And they can put them all on top of one physical piece of hardware, instead of

having to carry around as I’ve seen literally two or three laptops.

Then you have a relatively new technology called client side hypervisor, this is like sort

of virtualization but running on the desktop. A lot of other complexities involved there,

but fundamentally we’re talking about putting a hypervisor onto the bare metal hardware

of that desktop or that laptop, and then running multiple completely independent

operating systems on top of it, that essentially don’t interact at all. So there you’ve got

Lynnix and Windows 7 for example on one system. Now that could just as easily be

Windows XP and Windows 7 side by side, and so you know, we’re talking about

migration to Windows 7 having side by side compatibility. You know that sort of thing

is going to dramatically reduce the problems then users could have with that new

operating system because they can always go back to the old one. I mean there are a lot

of other use cases here, but again client side, nothing to do with the server - nothing to do

with the data centre at all really, so you’ve got a fundamental difference there as well.

Then you’ve got a bunch of technologies and I’ll just give you a couple of ideas about

them, that don’t really deal with the operating system that much at all. So you’ve got

remote application virtualization and this is where just the application is served to the end

user across a network. It’s still running in the data centre, so you get a lot of the security

and other advantages of having a data centre based execution, but the end user gets access

to that application no matter what desktop they’re actually physically using, because

they’re accessing it simply across a network. And then you get local application

virtualization, this is very various different technologies and implementations and it’s

known as isolation or layering or containerization, and then what happens here is the

application actually is installed and runs locally, but it doesn’t use the standard tools and

methods for maintaining its own configuration and data, so it doesn’t use the standard

system registry for example. In a lot of cases it doesn’t actually use the standard file

system, it actually has a separate, it establishes a separate file system, and a separate

registry. And so you’ve got a lot of isolation benefits, so you know, you don’t get the

DLL conflicts for example if you’re running multiple versions of the same application.

Page 6 of 17

You can run multiple java runtime on the same box without any conflicts, so there are a

lot of opportunities here to get around some very significant problems, but again we’re

not talking about anything that connects back to the server. So when I say VDI is not the

only answer this is why I say it. We’ve got a significant population here, and this is a

survey that EMA did just in late 2009, and you can see there the remote desktop

virtualization is very popular, you know, its equal first in terms of the popularity of these

different technologies, but you can also see that there’s ten or eleven different

technologies of varying popularity. And the one thing here is you’ll notice they’re the

two that add up to much more than 100%, and that’s because organizations are deploying

multiple technologies together. Now in fact when you look deeply at this data as I did, I

actually found that enterprises tend to deploy between four and five different

virtualization technologies together just for desktop virtualization and end point

virtualization. Almost a quarter of organizations that are doing this are deploying more

than six different technologies simultaneously. The key here is that we believe many end

point virtualizational desktop and associated technologies are going to be needed to solve

real world requirements. It’s a case of different types of users actually need more than

one solution on many different occasions. You will find some user groups and

departments will be satisfied with a single solution, such as, maybe it’s a VDI, maybe it’s

a desktop virtualization, maybe it’s an ab streaming, but in most situations users will need

multiple technologies to address all of their issues. And this is just one of the ways in

which desktop virtualization is fundamentally different from server virtualization.

I’d like to dive into that a little bit. Now firstly as I mentioned desktop virtualizations not

only serve a base, yes there are multiple server based technologies involved in desktop

virtualization, but there’s also a lot of client based technologies that really have almost

nothing to do with the server. But I’ve mentioned the four different virtualization

technologies, and many of those are client based, you know local OS virtualization, the

client hypervisor application virtualization for example. Not it’s also important here

when you start to talk about who’s going to run and own this environment. Now, when

you talk about local OS virtualization, client hypervisor or application isolation, I mean

these specifically are probably quite alien terms to the server team, the server

virtualization people. And yet the desktop support teams probably already know some of

these terms, but more important they probably know quite deeply the architectures and

intricacies of the end point systems, of the desktops, of the multiple different types of

desktops, different types of laptops in the environment. As well as potentially the clients,

the point of sale, the front office terminals. The server admins are much less likely to

have that level of understanding and knowledge, and when you think about the biggest

barriers to success, among them are skills and knowledge, then we have to start thinking

about which team is most appropriate to understand the challenges involved and this is

one element that leaves me to believe that the desktop management team definitely

already has a significant proportion of the knowledge they need to understand desktop

virtualization, which the virtual server team probably don’t.

Moreover the scale here is exponentially larger than in the server room. So, the average

data centre for instance in EMA’s data has around about eleven staff for around about

three hundred servers – this is an average, you know, obviously it varies quite

Page 7 of 17

significantly. But we find they’re looking at the same data, the same averages, that same

organization is likely to have over 5,000 desktops, so you‘re talking about a quantum

shift in scale here. Most organizations already face a shortage of skilled server

virtualization staff by the way, so giving them an extra 5,000 systems to deal with, you

know, a 1500% increase in systems under management is simply impractical. You can

see the ratios there, the server to admin ratio and the desktop to admin ratio, it’s a

multiple. So, but what we have already today is desktop support already handling those

volumes. It’s already handling that level of interaction within users with desktops every

single day, so we’ve got an entirely different type of skill set and an entirely different

type of scale, again suggesting to me that the desktop team is going to be primary here.

The other thing I think is important is that physical deployments will remain dominant

and you can see here that most organizations are not going to deploy end point

virtualization – this is a typo – it says application virtualization, it should say end point

virtualization for their entire environment. We’re predicting that physical deployments

will remain not only regular but dominant in the enterprise, at least through 2012, and

probably through 2015. So we’ve got a situation where whoever owns the desktop is

going to have to deal with physical and virtual. Anyone required to deliver, administer or

manage desktop virtualization is going to have to deal with those physical end points as

well. Once again this is an area where the desktop team already has the skills and the

ability to do that. If you don’t do that, then you’re going to (inaudible 25.13.6) support

and you’re going to get into a frustrating situation for end users where someone will think

it’s the physical desktop and they don’t have the skills to fix it, whereas the physical

desktop team may think it’s the virtual desktop and they won’t have the skills to fix it

either. So you’ve got all these problems with support, that impacts productivity, it also

impacts costs and then you end up with multiple people involved as well which is a

staffing and resourcing issue.

The other thing which really grabs me here is that there’s actually quite a variety of

desktop virtualization users, I mean that’s an interesting chart in itself because you can

see to start with that end point virtualization, desktop virtualization, it’s pretty broadly

deployed now. Again, this is research done in late 2009 so it’s pretty recent and it shows

that it’s not just these past workers using data entry tools on a thin client, and it’s not IT

developers and so forth doing programming and doing testing and multiple

environments. It’s actually pretty much across the board, across the entire enterprise,

more than 50% of each different type of user are having production deployments of end

point virtualization. But what this also means is that anyone who is dealing the desktop

virtualization environment, trying to manage it and maintain it, is dealing with a user base

that’s much less sophisticated than the users, and the primary contact points for server

virtualization.

So over half of all organizations are delivering desktop virtualization to people like

process workers, and that can be anyone from a call centre operator down to a factory

floor staff, as well as mobile staff, you know, sales on the road, knowledge workers and

management as well. Now end point virtualization staff, whoever owns that strategy and

that project team has got to be equipped to ensure a personal level of satisfaction for these

least technological advanced staff, which is actually something the desktop teams already

Page 8 of 17

do every day. Satisfaction in end user experience is actually a prime issue in terms of

being able to guarantee success to your end point and desktop virtualization deployment,

so it’s very important that you’re able to deal with individual users and understand what

they’re doing and why they’re doing. Overall it really becomes clear to me that end point

and desktop virtualization is probably situated within the desktop administration team

rather than the server administration team. Really the only significant link between

server virtualization and end point virtualization is the worker virtualization to start with

and the fact that some servers might be used. Really the rest of it is all about desktop

management.

So just looking at whether you should or should not be dong desktop virtualization? I

think it’s fairly broad, as you can in the previous chart it goes across multiple different

use types and user groups. But there’s some interesting things here, let’s go to the top of

the session about busting the myths of ROI. Now this is the big myth of desktop

virtualization I think, is that desktop virtualization doesn’t deliver return on investment.

Now this research, and again this is recent research and it’s also research asking users

who are actually using desktop virtualization today. This is not a ‘would this save you

money’ – this is a ‘has it already saved you money’, and as you can see there for 71% of

respondents, they said yes, end point virtualization does result in real measurable cost

savings. And that’s really interesting because a lot of people look at the cost of

potentially an additional service, although as I said, desktop virtualization does not

necessarily involve servers. And you know, the cost of network and maybe storage and

so forth, different technologies, maintenance training and yet we see that all the people

who have measured their costs in some way upwards of 90%, believe that it delivers and

has delivered for them real measurable cost savings. Well it has, it’s sort of busting the

myth.

But let’s look at a little bit more at detail. These are again, it’s a different question but

asking what result you actually achieved and three different costs results were among the

options available, and they actually ended up being the top three options responded, so

you can see their 55-60% are reporting of these different cost savings. But in actual fact

84% reported specific cost benefits, most organizations obviously you can see there’s a

hardware cost reduction, things like being able to use thin clients instead of full PC’s,

being able to load up multiple end users onto a single device, so a server for example

being able to load up ten or fifteen different or more end points or desktops that are

virtually delivered to the end user. So again, you can see the savings you can get through

there. Being able to share storage as well, being able to share a single larger storage

device in the data centre, amongst multiple users rather than all the local running hard

drives. So, I mean, that’s very interesting. It’s interesting also that over half of the

organizations, around about 50-60% actually, achieved cost reduction in two or more of

these areas simultaneously. In almost a third, just on 30%, actually reported saving costs

in all three of these areas. Now it’s also important to note just by the way that they also

reported a lot of other outcomes which potentially can drive those cost savings, and in

fact drive revenue up as well. For things like better security, you know, preventing data

loss, more flexibility, greater mobility, higher availability which is going to drive up

Page 9 of 17

productivity and revenues, you know, there are a lot of areas here which can actually

drive significant and very specific cost savings.

I may just do an example for example, or a couple of examples, we’ve got more case

studies that I’ll cover later on, but there’s one organization I know, they had a very long

running transaction based application which went over to multiple systems, it’s actually a

pharmacological organization doing prescriptions and so forth. And they have a very

long running transaction whenever they fill a prescription that goes across three or four

different systems. What they were doing was actually putting two physical desktops on

the pharmacist’s desk, whenever they would write a prescription they would get it started

on one of those systems and then they’d turn around to the other one, so they continue to

work and do more business. What they’ve done now instead now is put a local client and

a local OS virtualization on top of one desktop on the pharmacist’s desk, and because it’s

running two separate operating system environments, they can actually run it as two

separate PC’s, and they’re effectively doubling their productivity and halving their end

point hardware costs. That’s pretty impressive in itself. Just one of the many different

examples, and like I said I’ll give you a few more case studies towards the end of the

session today.

Just think about software costs though – if you’re able to maintain an asset register for

example of software licenses, where they’re deployed, who’s using them – if you can get

accuracy on that you can do two very important things around cost saving. You can

firstly reduce the overall number of licenses you are using. You can tell whether people

are using them or not, you can actually harvest those licenses from people who aren’t

using them and apply them to people who need them, rather than just going out and

buying more licenses. The other thing you can do to reduce software costs is actually go

to your software vendor and show them definitively how much software you are using,

and often times they will let you reduce your software licenses overall and negotiate

down to a lower costs. So there are a few things here, the admin costs, having centralized

desktops, having centralized desktops, being able to manage those desktops centrally

without having to remote in or even worse travel to a remote site to sit down in front of a

desktop to fix any problems. Being able to apply or attach for example, once to a base

image and have that propagate to ten thousand desktops that are based on that base

image. Again you can see there are significant opportunities to reduce admin costs here.

So, the top three outcomes: actually cost, cost, and cost reduction again. So that’s pretty

strong in terms of busting that myth about ROI. In terms of quantifying that ROI though,

it’s really interesting, you can see here that there are certain clusters, you may, you know

maybe you’re not going to save huge amounts but between 0-10% is, you know, upwards

of 30% of the population here have saved that. But you’ve also got a little spike there,

around 20-25%, and some are even towards the higher end, you know a handful of

organizations even reported overall a desktop and application cost reduction of 50% or

more. On average, if you average out all these numbers, the average saving in desktop

virtualization deployment is around about 17% of the total desktop and application

management and deployment c

IT & DATA MANAGEMENT RESEARCH,
INDUSTRY ANALYSIS & CONSULTING

View Webinar & Listen On-Demand

Back To Library

IT & DATA MANAGEMENT RESEARCH,INDUSTRY ANALYSIS & CONSULTING

View Webinar & Listen On-Demand

Back To Library

IT & DATA MANAGEMENT RESEARCH,
INDUSTRY ANALYSIS & CONSULTING