One of the things we keep hearing from prospects about desktop virtualization is cost. In fact, in a meeting with our CIO Council this spring, the CIO of a major Wall Street bank said this firm’s investments in a virtual desktop infrastructure (VDI) solution had so ballooned out of proportion and the experience had been so painful that it’s left permanent bad taste in everyone’s mouth. There’s no way, he contends, that he could ever sell “desktop virtualization” to his firm again – management and end users alike.
That point really inspired us to work on a TCO model – so companies know what the costs entail before they commit to a desktop management path. Fundamentally, desktop virtualization is about easier desktop management and cost savings the icing on the cake.
In our TCO calculations, we show how MokaFive can dramatically
cut desktop TCO by at least 45% by delivering savings in three areas:
1. Operational costs;
2. Helpdesk costs; and
3. Capital costs.
Operational Savings. MokaFive’s management model -- central management and distributed execution – is unique in the market, and critical to lowering overall TCO. The IT administrator creates one golden image, called the LivePC, which is sent down to thousands of users. To patch or update OS or applications, IT updates the single golden image in a central location, and automatically the changes are distributed to users’ machines. Contrast that to traditional software distribution, which requires every endpoint to be individually patched which can result in errors, complications and costs. (It’s no wonder companies are dreading the Windows 7 migration – and I am not at all surprised by the
costs.)
Helpdesk Savings. MokaFive also delivers savings in helpdesk costs. Typically the most expensive calls occur when a user corrupts their machine with a virus. With MokaFive’s rejuvenate capability, a corrupted desktop can be “rejuvenated” back to its pristine state with all personal data intact – all with just a click of a button. The user doesn’t have to even make a helpdesk call or be online. The CIO of one of our earliest customers – a major law firm in Silicon Valley – recently raved to me about the unexpected savings in their helpdesk costs. They hadn’t even calculated it into their models (nor we, for that matter), but we now expect them to have paid for their initial investment in the next year.
If not for MokaFive, this customer’s helpdesk would be fielding level two and level three calls when a user corrupts their machine with a virus. This specific case calls for a desktop re-image, which can be a very cumbersome process taking hours, if not days to complete. When you re-image the machine, IT needs to supply a new OS, restore all the applications, and then re-apply all the user data.
We estimate steady state this is going to be true whether it’s a VDI instance or with software distribution because even in a VDI scenario the user has to make a helpdesk call and the administrator has engage and to revoke the VM and put the data back on.
Capital Savings. With MokaFive, enterprises have the option to implement BYOC (bring your own computer) programs for employees and contractors.
Cisco and Dell made headlines last year when they initiated BYOC programs giving their employees a stipend to purchase their own computer. Both used virtualization to deliver company approved applications, but their approaches had significant limitations. In Dell's case, the only real choices was, well, Dell machines. Cisco at least allowed more latitude, so employees could purchase Macs, but "they are pretty much on their own for tech support." With these traditional desktop management models, and even with VDI, BYOC hits a snag due to online-offline access issues.
With MokaFive, IT deploys and manages the virtualized corporate environment on employee-chosen machines (Mac or a PC, online or offline) using MokaFive and benefit from the central management and distributed model I discussed above.
Going Green. There is one final area of savings I'd like to highlight -- though it may not necessarily be considered by CIOs when making a decision on desktop virtualization: the environmental impact. With MokaFive's approach, companies can use existing equipment; existing personal devices and existing corporate devices. In the case of contractors, companies are no longer buying assets, nor are they provisioning servers to the datacenter. All these add up to a reduction in new power-hungry equipment. MokaFive’s approach give you almost status-quo type of energy in the case of most work from home and contractor scenarios – and is even more effective than what we have today. I go into a lot more detail on this in an
earlier post.
For our customers, the savings in all these areas have been very real. But the fact remains that desktop virtualization has over-promised and under-delivered for many years -- to the detriment of all of us. Just because two (with a third making very fast progress) very large vendors dominate virtualization, it doesn't mean innovation has ceased. It's still happening, and MokaFive is proof of it, 20+ patents and still coming.
We've really put a lot of thought into all the costs associated with managing desktops. Our customers have weighed in and helped us create a TCO model that factors in these four areas. We
invite you to sign up for a personalized TCO for your environment.
Purnima Padmanabhan, VP of Products and Marketing
I presented a session on BYOC and Security at RSA Conference 2011 today. Judging from the turnout (the room was packed), there is a lot of interest in this topic right now as companies are struggling with how to deal with employee-owned devices. When I asked how many people worked at companies that have official BYO programs, only a few people raised their hands. But when I asked how many people use a personal device for work, almost everyone's hand shot up. Too many IT departments either try to restrict access from personal devices, in which case employees work around the restrictions so they can get their work done, or the IT departments put their blinders on and pretend the problem doesn't exist. They would be much better off to actually embrace BYO and make it easy for users to "do the right thing".
.png)
