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)
Everyone in the pool
Once the core components of View are installed and running, at least one desktop pool needs to be built to support the users. The primary source of the desktop pool is a single VM that's built like any other Windows VM. The base OS is installed, then patches and service packs, followed by applications, and so forth until the VM is completely prepped and ready for a user. This source VM is then joined to the domain, and the VMware Agent is installed. The Agent is a small piece of code that runs on every View desktop and permits interaction with the View server.
Additionally, all the Microsoft Sysprep code must be installed on the vCenter Server to facilitate the automatic building of new desktops from the single image. This is the code that permits Windows machines to be cloned and run on the same network as unique entities, with various unique parameters such as the SID (security identifier) modified during the cloning process.
Once all those pieces are in place, the source VM is shut down, and a snapshot is taken of the system. This snapshot forms the basis of all subsequent desktop VMs.
Back in the VMware View Web interface, a desktop pool can now be created. Desktop pools can be built in several ways. The most common is likely to be linked clones. This method is used by View to allow for a large number of desktops without requiring that each desktop have a separate base disk image. Even a small desktop VM might require a 10GB disk, and creating a pool with 100 desktops would then require 1TB in storage. However, using linked clones, the total storage requirements of 100 users will only require a fraction of that space. View manages this trick by using the snapshot of the source VM as a baseline and creating links to that baseline for each VM. Thus, each desktop runs as an extension to the primary, with any and all changes made to the VM during normal use stored as a delta to the original. Also, View offers the option of creating a user disk with a fixed limit for users to store files separately from the linked clone.
In production, you'll want to use Microsoft Active Directory Group Policy to limit or prevent users from storing anything locally to the VM or to the user disk by redirecting My Documents and other directories to file shares served elsewhere. This is very similar to a normal Microsoft Terminal Services or Citrix installation.
The pool of desktop VMs can also be created with support for persistent or non-persistent desktop sessions. The difference here is whether or not a user is tied to a specific desktop instance, or if they simply log in to the next available desktop. In a call-center scenario, non-persistent desktops are probably the best idea, since users likely won't be using more than one or two applications, nor will they need a place to park their personal files.
Otherwise, persistent desktops are likely to be the best bet. This assigns a specific desktop to a specific user during their initial log-in, and they will always be connected to that desktop for each subsequent log-in, much like they would with a physical desktop beneath their desk.
Join the PC World newsletter!
Most Popular Reviews
- 1 Hisense Series 7 ULED 4K UHD TV review
- 2 Samsung Galaxy Note 7 review
- 3 Portable power: Venom Blackbook 13 Zero review
- 4 Alcatel Idol 4S review: King of the mid-range?
- 5 Samsung Galaxy S7 Edge Review
Latest News Articles
- Samsung's 960 Pro and 960 Evo SSDs marry crazy-fast speeds with roomy capacity
- Apple commits to run off 100% renewable energy
- IBM targets x86 server territory with new Power servers
- FBI faces lawsuit because it's stayed mum on iPhone 5c hack
- Bank of England wants next payment system to be blockchain-ready
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.
- CCJava / J2ee ProgrammersACT
- CCService Desk analystSA
- CCData Analyst | Data Feeds | Catalogue and MapNSW
- CCTest Manager (HP Quality Centre / Kronos)NSW
- CCBusiness Analyst - Telecom ProjectNSW
- FTJava DeveloperNSW
- CCIT Security ArchitectACT
- CCContract Web Developer (160915/WD/vmp)Asia
- FTOutbound TelesalesVIC
- FTScrum Master | High Profile FintechNSW
- FTTest SpecialistSA
- CCProgram Manager - Data InsightVIC
- FTCustomer Solutions Engineer | Voice | Data | TelcoNSW
- CCSolutions ArchitectACT
- CCVideo Conference Support Officer- VoIP, LAN, WAN, RemedyNSW
- FTTest Manager (HP Quality Centre / ARIBA)NSW
- CCSoftware TesterACT
- CCNetwork and Security EngineerNSW
- CCFull Stack Application Developer - IoT projectsVIC
- CCSenior .NET DeveloperVIC
- CCBusiness ArchitectNSW
- FTOutbound TelesalesVIC
- FTTechnical Business Analyst | Marketing ServicesNSW
- FTOutbound TelesalesVIC
- FTPositive Vetted ICT positions - Defence intelligence and information securityACT