As I was building the View Connection Server for our lab environment and editing the virtual machine so that it had the required 10GB of RAM, I had a thought but I’ll get to that in a second. The reason 10GB of RAM is required is due to sizing the Java Heap Size correctly. If you’re like me and I suspect many others, you will install the View Connection Server on a Windows Server 2008 R2 virtual machine which is 64-bit only. If you happen to miss this minor detail and perhaps install the View Connection Server software on a Windows Server 2008 R2 virtual machine with only 4GB of memory, you’ll be forced to re-install the View Connection Server software in order to properly size all components of the View Connection Server software, mainly the Java Heap Size. The Java Heap Size needs to be sized correctly in order to support the large number of concurrent desktop sessions. If you’re planning on setting up a View POC that ends up being a success, you don’t want to have to go through the process of re-installing View after knowing you already have a successful implementation. However, the 10GB requirement could tax your environment if you’re trying to use existing resources for the POC. The idea is the POC will succeed and you’ll receive approval to proceed with purchasing the correct hardware (compute & storage) for a proper View implementation. I had an idea for installing the View Connection Server software on a Windows Server 2008 R2 virtual machine with 10GB or RAM, checking to make sure the Java Heap Size is sized correctly then changing the RAM size of the virtual machine from 10GB to 4GB. This way the virtual machine fits better from a resource perspective in an environment that have enough resources to perform the POC, but not quite enough for a full implementation yet. The first thing I did was deploy a Windows Server 2008 R2 virtual machine from template and then set the RAM to 10GB. I then installed the View Connection Server software on the virtual machine and checked to confirm the Java Heap Size was set correctly. As you can see below, the Java Heap Size is set to the correct amount of 2GB. 
Next, I powered-off the virtual machine and modified the RAM of the virtual machine changing it from 10GB to 4GB. While I wait for the virtual machine to restart it would be nice to let you know where the above registry key is located. You can find it here:
HKLM\SOFTWARE\VMware, Inc.\VMware VDM\plugins\wsnm\TunnelService\params
The registry key you’re looking for is JvmOptions.
Okay, back to my test. After decreasing the RAM of the virtual machine, I browsed to the registry key and success, the Java Heap Size is still set at 2GB.
The idea here is to make your View POC a little easier on the environment from a resource perspective. Once your View POC has been considered a success, you can easily increase the size of the RAM on your View Connection Server back to 10GB. You’ll want to make sure you properly architect your View environment which should include multiple Connection Servers, Security Servers for external access and VDI specific storage.
I’ll be performing this same procedure in our lab where I wanted the ability to be able to test performance against our View Connection Server when properly sized (10GB) but don’t need the ability to support more than 50 concurrent users during normal operations (we have anywhere from 1-5 users accessing our lab at any one time).
