Architecture Planning

n
Integration with Workspace Portal means that IT managers can use the Web-based Workspace Portal
administration interface to monitor user and group entitlements to remote desktops.
n
With View Persona Management, physical and virtual desktops can be centrally managed, including
user profiles, application entitlement, policies, performance, and other settings. Deploy View Persona
Management to physical desktop users prior to converting to virtual desktops.
n
Storage management is simplified. Using VMware vSphere, you can virtualize volumes and file
systems to avoid managing separate storage devices.
n
With vSphere 6.0 or a later release, you can use Virtual Volumes (VVols). This feature maps virtual
disks and their derivatives, clones, snapshots, and replicas, directly to objects, called virtual volumes,
on a storage system. This mapping allows vSphere to offload intensive storage operations such as
snapshoting, cloning, and replication to the storage system. The result, for example, is that a cloning
operation that previously took an hour might now take just a few minutes using Virtual Volumes.
n
With vSphere 5.5 Update 1 or a later release, you can use Virtual SAN, which virtualizes the local
physical solid-state disks and hard disk drives available on ESXi™ hosts into a single datastore shared
by all hosts in a cluster. You specify only one datastore when creating a desktop pool, and the various
components, such as virtual machine files, replicas, user data, and operating system files, are placed on
either SSD disks or hard drive disks, as appropriate.
You manage virtual machine storage requirements, such as capacity, performance, and availability, in
the form of default storage policy profiles, which get created automatically when you create a desktop
pool.
n
With the View storage accelerator, the IOPS storage load is dramatically reduced, supporting end-user
logins at larger scales without requiring any special storage array technology.
n
If remote desktops use the space-efficient disk format available with vSphere 5.1 and later, stale or
deleted data within a guest operating system is automatically reclaimed with a wipe and shrink
process.
Hardware Independence
Remote desktops and applications are hardware-independent. For example, because a remote desktop runs
on a server in the datacenter and is only accessed from a client device, a remote desktop can use an
operating system that might not be compatible with the hardware of the client device.
For example, although Windows 8 can run only on Windows 8-enabled devices, you can install Windows 8
in a virtual machine and use that virtual machine on a PC that is not Windows 8-enabled.
Remote desktops run on PCs, Macs, thin clients, PCs that have been repurposed as thin clients, tablets, and
phones. Remote applications run on a subset of these devices. New device support is added quarterly.
If you use the HTML Access feature, end users can open a remote desktop inside a browser, without having
to install any client application on the client system or device.
View Features
Features included in View support usability, security, centralized control, and scalability.
The following features provide a familiar experience for the end user:
n
On Microsoft Windows client devices, print from a virtual desktop to any local or networked printer
that is defined on the Windows client device. This virtual printer feature solves compatibility issues and
does not require you to install additional print drivers in a virtual machine.
n
On most client devices, use the location-based printing feature to map to printers that are physically
near the client system. Location-based printing does require that you install print drivers in the virtual
machine.
Chapter 1 Introduction to View
VMware, Inc. 9