Architecture Planning
Table Of Contents
- View Architecture Planning
- Contents
- View Architecture Planning
- Introduction to View
- Planning a Rich User Experience
- Feature Support Matrix for View Agent
- Choosing a Display Protocol
- Using Hosted Applications
- Using View Persona Management to Retain User Data and Settings
- Using USB Devices with Remote Desktops and Applications
- Using the Real-Time Audio-Video Feature for Webcams and Microphones
- Using 3D Graphics Applications
- Streaming Multimedia to a Remote Desktop
- Printing from a Remote Desktop
- Using Single Sign-On for Logging In to a Remote Desktop
- Using Multiple Monitors
- Managing Desktop and Application Pools from a Central Location
- Architecture Design Elements and Planning Guidelines for Remote Desktop Deployments
- Virtual Machine Requirements for Remote Desktops
- View ESXi Node
- Desktop Pools for Specific Types of Workers
- Desktop Virtual Machine Configuration
- RDS Host Virtual Machine Configuration
- vCenter Server and View Composer Virtual Machine Configuration
- View Connection Server Maximums and Virtual Machine Configuration
- vSphere Clusters
- Storage and Bandwidth Requirements
- View Building Blocks
- View Pods
- Advantages of Using Multiple vCenter Servers in a Pod
- Planning for Security Features
- Understanding Client Connections
- Choosing a User Authentication Method
- Restricting Remote Desktop Access
- Using Group Policy Settings to Secure Remote Desktops and Applications
- Implementing Best Practices to Secure Client Systems
- Assigning Administrator Roles
- Preparing to Use a Security Server
- Understanding View Communications Protocols
- Overview of Steps to Setting Up a View Environment
- Index
n
Use multiple monitors. With PCoIP multiple-monitor support, you can adjust the display resolution
and rotation separately for each monitor.
n
Access USB devices and other peripherals that are connected to the local device that displays your
virtual desktop.
You can specify which types of USB devices end users are allowed to connect to. For composite devices
that contain multiple types of devices, such as a video input device and a storage device, you can split
the device so that one device (for example, the video input device) is allowed but the other device (for
example, the storage device) is not.
n
Use View Persona Management to retain user settings and data between sessions even after the desktop
has been refreshed or recomposed. View Persona Management has the ability to replicate user profiles
to a remote profile store (CIFS share) at configurable intervals.
You can also use a standalone version of View Persona Management on physical computers and virtual
machines that are not managed by View.
View offers the following security features, among others:
n
Use two-factor authentication, such as RSA SecurID or RADIUS (Remote Authentication Dial-In User
Service), or smart cards to log in.
n
Use pre-created Active Directory accounts when provisioning remote desktops and applications in
environments that have read-only access policies for Active Directory.
n
Use SSL tunneling to ensure that all connections are completely encrypted.
n
Use VMware High Availability to ensure automatic failover.
Scalability features depend on the VMware virtualization platform to manage both desktops and servers:
n
Integrate with VMware vSphere to achieve cost-effective densities, high levels of availability, and
advanced resource allocation control for your remote desktops and applications.
n
Use the View storage accelerator feature to support end-user logins at larger scales with the same
storage resources. This storage accelerator uses features in the vSphere 5 platform to create a host
memory cache of common block reads.
n
Configure View Connection Server to broker connections between end users and the remote desktops
and applications that they are authorized to access.
n
Use View Composer to quickly create desktop images that share virtual disks with a master image.
Using linked clones in this way conserves disk space and simplifies the management of patches and
updates to the operating system.
The following features provide centralized administration and management:
n
Use Microsoft Active Directory to manage access to remote desktops and applications and to manage
policies.
n
Use View Persona Management to simplify and streamline migration from physical to virtual desktops.
n
Use the Web-based administrative console to manage remote desktops and applications from any
location.
n
Use View Administrator to distribute and manage applications packaged with VMware ThinApp™.
n
Use a template, or master image, to quickly create and provision pools of desktops.
n
Send updates and patches to virtual desktops without affecting user settings, data, or preferences.
n
Integrate with Workspace Portal so that end users can access remote desktops through the user portal
on the Web, as well as use Workspace Portal from a browser inside a remote desktop.
View Architecture Planning
10 VMware, Inc.