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
Figure 5‑2. Load-Balanced Security Servers in a DMZ
vCenter
Management Server
Microsoft
Active Directory
View
Connection
Servers
load balancing
View
Security
Servers
DMZ
client device
ESX hosts running
Virtual Desktop
virtual machines
external
network
When users outside the corporate network connect to a security server, they must successfully authenticate
before they can access remote desktops and applications. With appropriate firewall rules on both sides of
the DMZ, this topology is suitable for accessing remote desktops and applications from client devices
located on the Internet.
You can connect multiple security servers to each instance of View Connection Server. You can also combine
a DMZ deployment with a standard deployment to offer access for internal users and external users.
The topology illustrated in Figure 5-3 shows an environment where four instances of View Connection
Server act as one group. The instances in the internal network are dedicated to users of the internal network,
and the instances in the external network are dedicated to users of the external network. If the View
Connection Server instances paired with the security servers are enabled for RSA SecurID authentication, all
external network users are required to authenticate by using RSA SecurID tokens.
View Architecture Planning
82 VMware, Inc.