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
3 Type the Secure Tunnel external URL in the External URL text box.
The URL must contain the protocol, client-resolvable security server host name or IP address, and port
number.
For example: https://view.example.com:443
4 Type the PCoIP Secure Gateway external URL in the PCoIP External URL text box.
Specify the PCoIP external URL as an IP address with the port number 4172. Do not include a protocol
name.
For example: 100.200.300.400:4172
The URL must contain the IP address and port number that a client system can use to reach this security
server. You can type into the text box only if a PCoIP Secure Gateway is installed on the security server.
5 Click OK to save your changes.
View Administrator sends the updated external URLs to the security server. You do not need to restart the
security server service for the changes to take effect.
Sizing Windows Server Settings to Support Your Deployment
To support a large deployment of View Manager desktops, you can configure the Windows Server computers
on which you install View Connection Server. On each computer, you can size the ephemeral ports, TCB hash
table, Java Virtual Machine settings, and Windows page-file. These adjustments ensure that the computers
have adequate resources to run correctly with the expected user load.
For hardware and memory requirements for View Connection Server, see “Hardware Requirements for View
Connection Server,” on page 7.
For hardware and memory recommendations for using View Connection Server in a large View deployment,
see "Connection Server Virtual Machine Configuration and Maximums" in the VMware View Architecture
Planning document.
Ephemeral Ports
View Manager uses ephemeral ports to establish TCP connections between View Connection Server and the
View desktops that it administers. To support a large View desktop deployment, you can increase the number
of available ephemeral ports.
An ephemeral port is a short-lived endpoint that is created by the operating system when a program requests
any available user port. The operating system selects the port number from a predefined range, typically
between 1024 and 65535, and releases the port after the related TCP connection terminates.
By default, the system can create a maximum of approximately 4,000 ephemeral ports that run concurrently
on Windows Server 2003 and approximately 16,000 on Windows Server 2008.
On 32-bit Windows Server 2003 computers, you should increase the number of available ephemeral ports if a
View Connection Server instance is likely to use more than 800 concurrent client connections.
Calculate the Number of Ephemeral Ports
You can calculate the number of ephemeral ports that are needed on each View Connection Server instance to
support a large number of concurrent client connections.
Procedure
u
Use the following formula.
Number of ephemeral ports = ( (5 x clients) / servers ) + 10
Chapter 5 Installing View Connection Server
VMware, Inc. 59