5.0
Table Of Contents
- VMware View Installation
- Contents
- VMware View Installation
- System Requirements for Server Components
- System Requirements for Client Components
- Supported Operating Systems for View Agent
- Supported Operating Systems for Windows-Based View Client and View Client with Local Mode
- Hardware Requirements for Local Mode Desktops
- Client Browser Requirements for View Portal
- Remote Display Protocol and Software Support
- Adobe Flash Requirements
- Smart Card Authentication Requirements
- Preparing Active Directory
- Configuring Domains and Trust Relationships
- Creating an OU for View Desktops
- Creating OUs and Groups for Kiosk Mode Client Accounts
- Creating Groups for View Users
- Creating a User Account for vCenter Server
- Create a User Account for View Composer
- Configure the Restricted Groups Policy
- Using View Group Policy Administrative Template Files
- Prepare Active Directory for Smart Card Authentication
- Installing View Composer
- Installing View Connection Server
- Installing the View Connection Server Software
- Installation Prerequisites for View Connection Server
- Install View Connection Server with a New Configuration
- Install a Replicated Instance of View Connection Server
- Configure a Security Server Pairing Password
- Install a Security Server
- Microsoft Windows Installer Command-Line Options
- Uninstalling View Products Silently by Using MSI Command-Line Options
- Configuring User Accounts for vCenter Server and View Composer
- Where to Use the vCenter Server User and Domain User for View Composer
- Configure a vCenter Server User for View Manager, View Composer, and Local Mode
- View Manager Privileges Required for the vCenter Server User
- View Composer Privileges Required for the vCenter Server User
- Local Mode Privileges Required for the vCenter Server User
- Configuring View Connection Server for the First Time
- Configuring View Client Connections
- Sizing Windows Server Settings to Support Your Deployment
- Installing the View Connection Server Software
- Installing View Transfer Server
- Configuring SSL Certificates for View Servers
- Configuring SSL Certificates for View Connection Server and Security Server
- Configuring SSL Certificates for View Transfer Server
- Prepare an Existing Certificate in PKCS#12 Format for Use with View Transfer Server
- Obtain a Signed Certificate from a CA for Use with a View Transfer Server Instance
- Generate a Self-Signed Certificate for View Transfer Server
- Configure a View Transfer Server Instance to Use a Certificate
- Configure SSL for View Transfer Server Communications
- Configuring Certificate Checking in View Client for Windows
- Appendix: Additional SSL Configuration Tasks
- Creating an Event Database
- Installing and Starting View Client
- Index
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-2. 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
Install a Replicated Instance of View Connection Server
To provide high availability and load balancing, you can install one or more additional instances of View
Connection Server that replicate an existing View Connection Server instance. After a replica installation, the
existing and newly installed instances of View Connection Server are identical.
When you install a replicated instance, View Manager copies the View LDAP configuration data from the
existing View Connection Server instance.
After the installation, the View Manager software maintains identical View LDAP configuration data on all
View Connection Server instances in the replicated group. When a change is made on one instance, the updated
information is copied to the other instances.
If a replicated instance fails, the other instances in the group continue to operate. When the failed instance
resumes activity, its configuration is updated with the changes that took place during the outage.
NOTE Replication functionality is provided by View LDAP, which uses the same replication technology as
Active Directory.
Prerequisites
n
Verify that at least one View Connection Server instance is installed and configured on the network.
n
Verify that you can log in as a domain user with administrator privileges on the Windows Server computer
on which you plan to install the replicated instance.
n
If the existing View Connection Server instance is in a different domain than the replicated instance, the
domain user must also have View Administrator privileges on the Windows Server computer where the
existing instance is installed.
n
Verify that your installation satisfies the requirements described in “View Connection Server
Requirements,” on page 7.
n
Verify that the computers on which you install replicated View Connection Server instances are connected
over a high-performance LAN. See “Network Requirements for Replicated View Connection Server
Instances,” on page 9.
Chapter 5 Installing View Connection Server
VMware, Inc. 39