I have to admit the idea behind virtualizing software is really cool. So cool I can't really grasp exactly how it works. I mean you have applications that run in their own memory pool and access the necessary resources that are also bundled within the pool without messing with the other system memory but still allowing the user to have input? The way they "stream" down to the desktop only the pieces of the software that is necessary at the time? It's like figuring out time travel. And all of the buzz around "virtualizing" everything, as if our entire work environment wasn't completely virtual anyhow right! Now we need to be virtually virtual, completely not real at all. So I am still stuck with the question of why? What great purpose does it serve so that companies would want to invest another $25-$50 per node or user along with infrastructure and training cost?
There are 2 main players in the Software Virtualization market right now. Altiris with Wise Software Virtualization Service, and Microsoft with their aquired SoftGrid from Softricity. On just a strange note I think it is weird that MS kept the Softricity name with SoftGrid. Instead of just calling it MS SoftGrid it looks like MS Softricity SoftGrid, maybe I am missing something. Anyhow, every virtualization solution seems to tout the same benefits:
Software Virtualization Benefits:
- No application or OS conflict - Virtual Apps run in their own memory bubble. Essentially this means that everything necessary for the application to run should be contained in the virtual package that you create. If you have an app that uses Java 1.3 and another that uses Java 1.5 the application package should have the necessary Java Components inside it so that regardless of the version of Java on the desktop it will work.
- Software is available On-Demand - When the software is needed clicking on the icon will "Inflate" (Altiris SVS) or "Stream" (SoftGrid) to the users PC. When no longer need the resource is stored in cache until needed again.
- Reduced testing time - Once the package is finished it should work on any OS that the clients support. Regardless of spam or improperly installed components on the target systems, the software should work flawlessly. This also greatly reduces the number of support calls after rollout since the application won't be affected by spam, or improperly installed pre-requisite components.
So it all sounds good right? And certainly the Virtualization services seem to work as advertised so what could be problem? Well there are a few caveats as well they all seem to share:
Software Virtualization Limitations:
- No core OS configuration support - This means that software or services that reside and interact with the actual desktop OS or physical hardware can not be deployed virtually. This means no patches for the OS or Anti-virus as well as no plug-in or configuration support for Internet Explorer. Any off the wall items that need to be updated in the registry or file system will need to be "deployed" instead of virtualized.
- All applications must be sequenced or packaged - Gone would be the days of simply deploying a well written manufacturers MSI or EXE installation package, which are becoming more common. For virtualization to work you have to repackage every application you want to use, and even worse you have to use them just as you would in a real world scenario. This is necessary so that the virtual version can emmulate the calls made by the app in a memory pool. It also allows the sequencing software to see what other dll's and registry keys etc are being used so they can be included with the final package.
The question then is if you still have to deploy patches, AntiVirus definitions and updates, drivers, and other updates via different means are we really saving that much time? Also, if every application has to be re-packaged how much time does that add to the typical deployment scenario? How many conflicting applications does the typical corporation have? Wouldn't it be better to update the app or go back to the developers with grievances versus investing in an expensive work around? How do apps that access specific information on the desktops work? Like for product activation or getting the current timezone, registry value or environment setting etc?
I have a feeling that we won't know until down the road a bit. I know this, when I first saw a virtual PC I thought of a hundred uses for it, but for virtual software I simply don't see it.
For those embarking on this journey here are a few links:
Altiris SVS
Microsoft SoftGrid
SoftGridGuru.com - A lot of useful info here for those using the MS virtualization solution.