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
Sizing the Java Virtual Machine
The View Connection Server installer sizes the Java Virtual Machine (JVM) heap memory on View Connection
Server computers to support a large number of concurrent View desktop sessions. However, when View
Connection Server runs on a 32-bit Windows Server computer, the View Secure Gateway Server component
is configured with a limited JVM heap size. To size your deployment adequately, you can increase the JVM
heap size on 32-bit computers.
On a 64-bit Windows Server computer with at least 10GB of memory, the installer configures a JVM heap size
of 2GB for the View Secure Gateway Server component. This configuration supports approximately 2,000
concurrent tunnel sessions, the maximum number that View Connection Server can support. There is no benefit
in increasing the JVM heap size on a 64-bit computer with 10GB of memory.
NOTE On a 64-bit View Connection Server computer, 10GB of memory is recommended for deployments of
50 or more View desktops. Configure less than 10GB of memory for small, proof-of-concept deployments only.
If a 64-bit computer has less than 10GB of memory, the installer configures a JVM heap size of 512MB for the
View Secure Gateway Server component. If the computer has the required minimum of 4GB of memory, this
configuration supports approximately 500 concurrent tunnel sessions. This configuration is more than
adequate to support small, proof-of-concept deployments.
If you increase a 64-bit computer's memory to 10GB to support a larger deployment, View Connection Server
does not increase the JVM heap size. To adust the JVM heap size to the recommended value, reinstall View
Connection Server.
On a 32-bit Windows Server computer, the default JVM heap size is 512MB for the View Secure Gateway Server
component. This JVM heap size can support approximately 750 concurrent tunnel sessions. To support more
than 750 sessions, the computer must have at least 3GB of memory and the JVM heap size should be increased
to 1GB. A JVM heap size of 1GB supports 1,500 concurrent tunnel sessions, the maximum number that View
Connection Server can support on a 32-bit computer.
Increase the JVM Heap Size on 32-Bit Windows Server Computers
You can edit the Windows registry to increase the JVM heap size on a 32-bit Windows Server computer on
which View Connection Server is installed.
IMPORTANT Do not change the JVM heap size on 64-bit Windows Server computers. Changing this value might
make View Connection Server behavior unstable. On 64-bit computers, the View Connection Server installer
sets the JVM heap size to accord with the physical memory. If you change the physical memory on a 64-bit
View Connection Server computer, reinstall View Connection Server to reset the JVM heap size.
On a 32-bit computer, if you increase the JVM heap size and reinstall or upgrade the View Connection Server
software, you must increase the JVM heap size again. This value is reset each time the View Connection Server
software is reinstalled or upgraded.
Procedure
1 On the Windows Server computer, start the Windows Registry Editor.
a Select Start > Command Prompt.
b At the command prompt, type regedit.
2 In the registry, locate the subkey and click JvmOptions.
HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc.\VMware VDM\Plugins\wsnm\tunnelService\Params
VMware View Installation
64 VMware, Inc.