VirtualVCP IT Virtualization

I am happy to report that I have managed to get the VMware View PCoIP Client to work on openSUSE Linux 12 with the GNOME 3 desktop environment. The first client I tried was the VMware View Open Client, which is an open source project. However the View Open Client does not support PCoIP and only connects to the View desktops using RDP. As I am not a fan of RDP, I was keen on getting PCoIP to work.

Some background as to why I needed the PCoIP View Client to work on Linux:

Generally for remote access to my lab, I use the VMware View PCoIP Client for Windows, Android and iOS (on the iPad). VMware has made the PCoIP client available on all of these platforms, but no Linux PCoIP client has been released. This article should get you up and running, but bear in mind that it is not supported by VMware.

When working on a Linux VM via the VMware Remote Console over a WAN or slow link, the keystrokes sent to the console might end up reppeating. In order to avoind this, perform the following steps:

1. Power down the VM

2. Add the following line to the VMX file (can also be done by editing the Advanced VM settings using the vSphere Client):

keyboard.typematicMinDelay = "2000000"

3. Save the VMX file

4. Power on the VM.

I decided to post this as I keep on forgetting what the fix is. Now I'll know where to find it in the future without having to go to Google ;-)

Following the changes made by VMware to the vSphere 5 vRAM allocation sizes, I've released version 0.6 of my vSphere License Calculator to reflect the new vRAM allocations.

Please download version 0.6 and let me know if you discover any further problems with the calculator.

*The vRAM Entitlement for vSphere Enterprise has now been corrected to 64GB*

The new version of tha calculator can be found here

Following some feedback from the community, I'm happy to release version 0.5 of my vSphere License Calculator.

The main issue that has been fixed in this release is a flaw in the formula that calculates the vSphere 4 License count based on the CPU core count.

The problem was discovered when a user tried to calculate licenses based on 7 core CPUs. This had highlighted a major flaw in the original formula for calculating vSphere licenses. The formula for calculating vSphere 4 Licenses has therefore been rewritten from scratch.

Please download version 0.5 and let me know if you discover any further problems with the calculator.

The new version of tha calculator can be found here