5.0
Table Of Contents
- VMware View Architecture Planning
- Contents
- VMware View Architecture Planning
- Introduction to VMware View
- Planning a Rich User Experience
- Feature Support Matrix
- Choosing a Display Protocol
- Using View Persona Management to Retain User Data and Settings
- Benefits of Using View Desktops in Local Mode
- Accessing USB Devices Connected to a Local Computer
- Printing from a View Desktop
- Streaming Multimedia to a View Desktop
- Using Single Sign-On for Logging In to a View Desktop
- Using Multiple Monitors with a View Desktop
- Managing Desktop Pools from a Central Location
- Architecture Design Elements and Planning Guidelines
- Virtual Machine Requirements
- VMware View ESX/ESXi Node
- Desktop Pools for Specific Types of Workers
- Desktop Virtual Machine Configuration
- vCenter and View Composer Virtual Machine Configuration and Desktop Pool Maximums
- View Connection Server Maximums and Virtual Machine Configuration
- View Transfer Server Virtual Machine Configuration and Storage
- vSphere Clusters
- VMware View Building Blocks
- VMware View Pod
- Planning for Security Features
- Understanding Client Connections
- Choosing a User Authentication Method
- Restricting View Desktop Access
- Using Group Policy Settings to Secure View Desktops
- Implementing Best Practices to Secure Client Systems
- Assigning Administrator Roles
- Preparing to Use a Security Server
- Understanding VMware View Communications Protocols
- Overview of Steps to Setting Up a VMware View Environment
- Index
View LDAP
View LDAP is an embedded LDAP directory in View Connection Server and is the configuration repository
for all VMware View configuration data.
View LDAP contains entries that represent each View desktop, each accessible View desktop, multiple View
desktops that are managed together, and View component configuration settings.
View LDAP also includes a set of View plug-in DLLs to provide automation and notification services for other
VMware View components.
View Messaging
The View Messaging component provides the messaging router for communication between View Connection
Server components and between View Agent and View Connection Server.
This component supports the Java Message Service (JMS) API, which is used for messaging in VMware View.
By default, RSA keys that are used for intercomponent message validation are 512 bits. The RSA key size can
be increased to 1024 bits if you prefer stronger encryption.
If you want all keys to be 1024 bits, the RSA key size must be changed immediately after the first View
Connection Server instance is installed and before additional servers and desktops are created. See VMware
Knowledge Base (KB) article 1024431 for more information.
Firewall Rules for View Connection Server
Certain ports must be opened on the firewall for View Connection Server instances and security servers.
When you install View Connection Server on Windows Server 2008, the installation program can optionally
configure the required Windows firewall rules for you. When you install View Connection Server on Windows
Server 2003 R2, you must configure the required Windows firewall rules manually.
Table 5-4. Ports Opened During View Connection Server Installation
Protocol Ports View Connection Server Instance Type
JMS TCP 4001 in Standard and replica
JMSIR TCP 4100 in Standard and replica
AJP13 TCP 8009 in Standard and replica
HTTP TCP 80 in Standard, replica, and security server
HTTPS TCP 443 in Standard, replica, and security server
PCoIP TCP 4172 in;
UDP 4172 both
directions
Standard, replica, and security server
Firewall Rules for View Agent
The View Agent installation program opens certain TCP ports on the firewall. Ports are incoming unless
otherwise noted.
Table 5-5. TCP Ports Opened During View Agent Installation
Protocol Ports
RDP 3389
USB redirection 32111
Chapter 5 Planning for Security Features
VMware, Inc. 67