5.2

Table Of Contents
By default, the system can create a maximum of approximately 16,000 ephemeral ports that run
concurrently on Windows Server 2008. 16,000 ephemeral ports can support more than 2,000 concurrent
client connections, the maximum supported number for a View Connection Server instance.
On Windows Server 2008 computers, you do not need to increase the maximum size of the TCB hash table.
Windows Server 2008 fully tunes this value by default.
For hardware and memory requirements for View Connection Server, see “Hardware Requirements for
View Connection Server,” on page 8.
For hardware and memory recommendations for using View Connection Server in a large View
deployment, see "View Connection Server Maximums and Virtual Machine Configuration" in VMware
Horizon View Architecture Planning.
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.
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.
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.
Configure the System Page-File Settings
You can optimize the virtual memory on the Windows Server computers on which your View Connection
Server instances are installed by changing the system page-file settings.
When Windows Server is installed, Windows calculates an initial and maximum page-file size based on the
physical memory installed on the computer. These default settings remain fixed even after you restart the
computer.
If the Windows Server computer is a virtual machine, you can change the memory size through vCenter
Server. However, if Windows uses the default setting, the system page-file size does not adjust to the new
memory size.
Chapter 8 Configuring View for the First Time
VMware, Inc. 113