7.0
Table Of Contents
- View Architecture Planning
- Contents
- View Architecture Planning
- Introduction to View
- Planning a Rich User Experience
- Feature Support Matrix for Horizon 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
- Monitors and Screen Resolution
- Managing Desktop and Application Pools from a Central Location
- Advantages of Desktop Pools
- Advantages of Application Pools
- Reducing and Managing Storage Requirements
- Application Provisioning
- Deploying Individual Applications Using an RDS Host
- Deploying Applications and System Updates with View Composer
- Deploying Applications and System Updates with Instant Clones
- Managing VMware ThinApp Applications in View Administrator
- Deploying and Managing Applications Using App Volumes
- Using Existing Processes or VMware Mirage for Application Provisioning
- Using Active Directory GPOs to Manage Users and Desktops
- 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
- Using Smart Policies
- 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
Using VMware vSphere to host virtual desktops and RDS host servers provides the following benefits:
n
Administration tasks and management chores are reduced. Administrators can patch and upgrade
applications and operating systems without touching a user's physical PC.
n
Integration with VMware Identity Manager means that IT managers can use the Web-based
VMware Identity Manager administration interface to monitor user and group entitlements to remote
desktops.
n
Integration with VMware App Volumes, a real-time application delivery system, enables enterprises to
deliver and manage applications at scale. Use App Volumes to attach applications to users, groups, or
target computers, even when users are logged into their desktop. Applications can also be provisioned,
delivered, updated and retired in real time.
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
With VMware User Environment Manager, end users get a personalized Windows desktop that is
adapted to the user's situation, meaning that access to the required IT resources is based on aspects
such as role, device, and location.
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 data center 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.
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 or application inside a browser,
without having to install any client application on the client system or device.
Chapter 1 Introduction to View
VMware, Inc. 9