The biggest news was the company's announcement of VMware View, an update to its desktop virtualization product. The release contained a couple of interesting aspects. First, VMware's product now includes desktop cloning from a master image. This means that instead of having a full image copy for each virtualized desktop, the system contains one "golden" image, from which new virtual instances are created as needed. When a user makes some changes (saves some data, etc.) to a specific virtual desktop, those changes are captured and stored in a difference file.

Cloning offers two important benefits. The first benefit of cloning is that storage is vastly decreased; instead of, say, 2 GB per desktop, it's 2GB for the master, plus the collection of difference information for the universe of virtual desktops. Clearly, once you get into significant numbers of desktops, the storage savings can be huge. The second benefit is, perhaps, even more important. After all, the cost of storage is plummeting, so maybe the storage savings don't impress you. But another benefit of the master/dynamic desktop creation is that the arduous task of keeping desktops up-to-date by applying patches, keeping virus definitions current, and so on becomes much simpler when only one image must be kept current. Given the well-known challenge of desktop management, ease of system administration may be the greatest benefit of dynamic desktop assembly.

A second interesting element of the new VMware View is that it includes an experimental capability to allow desktop checkin/checkout. This allows a desktop to be sourced from a centralized server (a la cloning, described just now) but rather than the desktop executing on a server, it is sent down to a desktop device, where it is used just like a traditional locally-based desktop. This is functionality that is discussed extensively in the virtualization world, cited as important for workers that are mobile. The scenario often presented is an employee needs to work at home or on the road, where connectivity is not good enough to allow interaction with a remote server. I have to say that, while this sounds convincing, I'm not sure I believe in it. After all, if the connectivity isn't that good, wwill it be sufficient to transfer an entire desktop? Moreover, it seems like keeping the difference files straight in this scenario could be challenging. This seems like a "last mile" issue, hinging on the bandwidth available in the Internet. I won't say this is a non-starter, but it remains to be seen how it will be applied in the real world.