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
Deploying Individual Applications Using an RDS Host
You might choose to provide end users with remote applications rather than remote desktops. Individual
remote applications might be easier to navigate on a small mobile device.
End users can access remote Windows-based applications by using the same Horizon Client that they
previously used for accessing remote desktops, and they use the same PCoIP display protocol.
To provide a remote application, you install the application on a Microsoft Remote Desktop Session (RDS)
host. One or more RDS hosts make up a farm, and from that farm administrators create application pools in
a similar manner to creating desktop pools. A farm can contain up to 200 RDS hosts. A View pod can
support up to 200 farms.
Using this strategy simplifies adding, removing, and updating applications; adding or removing user
entitlements to applications; and providing access from any device or network to centrally or distributed
application farms.
Deploying Applications and System Updates with View Composer
Because linked-clone desktop pools share a base image, you can quickly deploy updates and patches by
updating the parent virtual machine.
The recompose feature allows you to make changes to the parent virtual machine, take a snapshot of the
new state, and push the new version of the image to all, or a subset of, users and desktops. You can use this
feature for the following tasks:
n
Applying operating system and software patches and upgrades
n
Applying service packs
n
Adding applications
n
Adding virtual devices
n
Changing other virtual machine settings, such as available memory
NOTE Because you can also use View Composer to create farms of linked-clone Microsoft RDS hosts, the
recompose feature lets you update the guest operating system and applications on RDS hosts.
You can create a View Composer persistent disk that contains user settings and other user-generated data.
This persistent disk is not affected by a recompose operation. When a linked clone is deleted, you can
preserve the user data. When an employee leaves the company, another employee can access the departing
employee's user data. A user who has multiple desktops can consolidate the user data on a single desktop.
If you want to disallow users from adding or removing software or changing settings, you can use the
refresh feature to bring the desktop back to its default values. This feature also reduces the size of linked
clones, which tend to grow over time.
Managing VMware ThinApp Applications in View Administrator
VMware ThinApp™ lets you package an application into a single file that runs in a virtualized application
sandbox. This strategy results in flexible, conflict-free application provisioning.
VMware ThinApp provides application virtualization by decoupling an application from the underlying
operating system and its libraries and framework and bundling the application into a single executable file
called an application package. You can use View Administrator to distribute VMware ThinApp applications
to desktops and pools.
IMPORTANT If, instead of distributing ThinApps by assigning them to desktops and pools, you would rather
assign ThinApps to Active Directory users and groups, you can use VMware Workspace Portal.
Chapter 3 Managing Desktop and Application Pools from a Central Location
VMware, Inc. 39