VMware View 3.0
VMware's VDI solution makes virtual desktops real, but not particularly easy to manage
- Building a VMware View infrastructure is relatively simple
- Management leaves much to be desired, user experience can be spotty, Web interface is fairly picky about which browser is used
All in all, VMware View is a functional VDI implementation with more than a few quirks and foibles.
Price$ 4,197.73 (AUD)
Buy now (Selling at 1 store)
Beyond the software clients, there are several companies producing thin client systems that have embedded VMware View clients. These units are designed to connect to a VMware View server and offer all of the options View supports.
Regardless of connection method, whenever a user authenticates to the VMware View server, they are presented with a virtual Windows desktop that works exactly the same as the physical Windows desktops they're used to. The one difference: In addition to logging out of the session, they can now disconnect. Disconnecting allows them to reconnect from anywhere and resume where they left off, while logging off will necessarily close all open applications and present them with a clean slate at the next log-in.
When running over 100Mbps Ethernet with the VMware View Client, the experience is roughly the same as with a local desktop. Of course, the overall experience is highly dependent on the specs of the desktop VM, such as RAM and CPU allowance, but when VMs are properly configured, most users are unlikely to notice much of a difference.
Users running from remote locations or via the Internet will see some sluggishness inherent with RDP (Remote Desktop Protocol), and high-latency connections will suffer somewhat too. This is a well-known factor present in all RDP connections, not simply VMware View. As with Citrix and Microsoft Terminal Services, it's best to know your users and what they need before deploying any form of virtual desktops. Users that require lots of CPU and RAM to run applications like Photoshop are not generally suitable for VDI, much as they aren't for other forms of remote desktop access.
Speaking of remote users, VMware View can be deployed to allow remote users to access their desktops from any browser anywhere. This comes in the form of another VMware View server built as a security server -- essentially, a Windows server that resides on the DMZ and acts as a proxy to the internal VMware View server. This removes the need for the internal View server to be Internet accessible and offers some measure of protection from external threats. The setup and configuration of this security server is extremely straightforward, requiring only a few open ports between the two systems, as well as to the security server from the Internet.
All in all, VMware View is a functional VDI implementation with more than a few quirks and foibles. If carefully administered, it's a suitable option for a VDI implementation, though there are several places where substantial improvements could be made, specifically in desktop pool administration and the entire Web-based management UI.
VMware's main competitor in the VDI space is Citrix's XenDesktop, which is quite a bit more advanced in terms of management and administration, but lacks the VMware VI3 back end when run with the native XenServer. No big surprise here: Citrix is better at desktop management and VMware is better at core virtualization fundamentals.Regardless of the VDI technology used, implementing VDI could be considered more of a political than a technical challenge. Users tend to bristle when the core of their work is disturbed and will be quick to point out flaws and problems, whether or not they exist. You'll want to make sure that the VDI build is as solid as possible before beginning a small-scale pilot.
Also problematic with any VDI initiative are the desktop options available. At the moment, eight-year-old Windows XP is the most popular candidate to form the VDI baseline. This is a problem from several perspectives and affects all VDI products. With Microsoft Vista apparently dead in the water and Windows 7 still in beta, it's unfortunately not an issue that is likely to be resolved soon.
Join the PC World newsletter!
Most Popular Reviews
- 1 Samsung's Galaxy Alpha review: A peek into the Galaxy S6
- 2 Lenovo Yoga 3 Pro hybrid Ultrabook
- 3 Bose SoundLink on-ear Bluetooth headphones
- 4 Apple iPhone 6 Plus: An in depth review
- 5 Medion Akoya P2214T (MD99430) hybrid laptop
Best Deals on GoodGearGuide
Latest News Articles
- Distracted? Slap this Hitachi gizmo on your forehead to focus
- Divoom Voombox-Travel rugged Bluetooth speaker
- Uber suspends Nevada operations, affecting nearly 1,000 jobs
- Sony confirms development of e-paper smartwatch
- My gripe with Apple’s iPhones
GGG Evaluation Team
First impression on unpacking the Q702 test unit was the solid feel and clean, minimalist styling.
For work use, Microsoft Word and Excel programs pre-installed on the device are adequate for preparing short documents.
The Fujitsu LifeBook UH574 allowed for great mobility without being obnoxiously heavy or clunky. Its twelve hours of battery life did not disappoint.
The screen was particularly good. It is bright and visible from most angles, however heat is an issue, particularly around the Windows button on the front, and on the back where the battery housing is located.
My first impression after unboxing the Q702 is that it is a nice looking unit. Styling is somewhat minimalist but very effective. The tablet part, once detached, has a nice weight, and no buttons or switches are located in awkward or intrusive positions.
- FTDigital Account ManagerNSW
- FTAccount ExecutiveNSW
- CCTech Support | IT Services Firm - Ad hoc Projects - Echuca AreaVIC
- FTSEO Content ExecutiveVIC
- FTPartnership Manager - MediaNSW
- FTProgram Manager - Integration & SolutionsNSW
- FTStudio Design ManagerVIC
- CCTech Support | IT Services Firm - Ad hoc Projects - Port Augusta / Whyalla AreaSA