VMware View 4.5, the latest version of the VMware desktop virtualization product, is designed to simplify the management,...
By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
monitoring and security of enterprise workstations.
Like other virtual desktop infrastructure (VDI) products, VMware View 4.5 hosts virtual desktops on a central server, wich users can then access through traditional PCs, thin clients and other endpoints. View 4.5 uses PC over IP (PCoIP) to exchange data between the endpoint and the vSphere host where the virtual desktop resides.
Desktop virtualization gives IT staff greater control over a desktop infrastructure. Because virtual desktops are centrally managed, IT administrators can target specific applications to user pools. Additionally, they can spend less time servicing endpoint machines, because it's the servers that perform most of the data crunching.
Before its official release in September, VMware View 4.5 traveled a bumpy road. In June, SearchVirtualDesktop.com reported that View 4.5 would ship late -- and without profile management. That news caused disappointment among customers, who need third-party products to get the customized desktop experience.
Despite the lack of profile management, View 4.5 is a significant update to the VMware desktop virtualization portfolio. This guide covers the additions to VMware View 4.5, as well as specific strategies and problems to watch consider.
VMWARE VIEW 4.5 FEATURES
VMware View 4.5 offers improved wide area network (WAN) performance, tighter integration with VMware ThinApp and a new Apple Mac View Client. These resources take an in-depth look at the new VMware desktop virtualization features.
What's new in VMware View 4.5?
Robust VDI installations require a strong network backbone, and VMware View 4.5's PCoIP delivery system improves network performance. To help users, VMware also published suggested WAN bandwidth and latency figures for View. A reconfigured local mode and a new transfer-server role are also new in View 4.5.
Linked clones and the future of VMware View 4.5
VMware View 4.5 is a major upgrade compared with its previous iteration, but how does it stack up against Citrix Systems' XenDesktop? (According to Gartner Inc., XenDesktop 4.0 is the first enterprise-ready VDI product.) Expert Mike Laverick weighs in on the future of View 4.5 and how VMware desktop virtualization compares to the competition.
Launching ThinApps in VMware View 4.5
VMware View 4.5 and ThinApp 4.6 are better integrated to take advantage of the natural overlaps between virtualized applications and desktops. Users can now launch VMware ThinApp and designate which desktop pools receive virtualized applications.
HOW TO INSTALL VMWARE VIEW 4.5
VMware View 4.5 is built on vSphere, so many installation and management principles apply to both products. But there are nuances when it comes to VMware desktop virtualization deployments and administration. These resources cover how to install VMware View 4.5 and offer management strategies.
How to install VMware View 4.5: Three easy tips
Installing VMware View 4.5 is an elaborate endeavor. To eliminate costly mistakes, careful planning is critical. Before rolling out this VMware desktop virtualization product, consider licensing, virtual desktop clusters and Active Directory subnets to ensure a smooth installation.
Four irritating VMware View 4.5 management obstacles
VMware View management and administration is a fluid process with numerous variables. And a poorly managed VMware desktop virtualization infrastructure can create performance problems for users. To maintain high performance, monitor resource usage, storage utilization and provisioning errors.
Migrating VMware View 4.5 virtual desktops: Data store considerations
As modified virtual machines, VMware View virtual desktops have storage migration capabilities. Offloading VMware View 4.5 virtual desktops to a different storage array is helpful during hardware or firmware updates, for example. But as with any migration, you must consider the data store ramifications.