#VDI Tip 67: Run the PCoIP Managment Console on vSphere Without Converting

Teradici offers a great little appliance to manage all of your PCoIP devices. It doesn’t matter if your Zero Clients are from Wyse, Samsung or some company you never heard of before. If the device is a Zero Client, the Teradici Management Console has you covered.

You should be running your Teradici Management Console(MC) in your management cluster. When you download the MC from Teradici it’s meant to be ran on VMware Player or Workstation so the instructions tell you to use VMware Converter but this is a waste of time.

1. Open the VMX file with NotePad
2. Delete the first line of code “.encoding = “windows-1252”
3. Save the file
4. Copy the VMX and VMDK to the proper datastore
5. Right click on the VMX file and add to the inventory
6. Upgrade the VM to version 8
7. Remove the Network Card
8. Add a New Network Card, I used the Flexible adapter
9. Power on the VM
10. It will tell you to reboot again
11. Done

If you’re going to have less than 2,000 Zero clients in your environment use a DNS service record to configure your devices. If you’re going to have more than 2,000 Zero clients you can configure your devices via DHCP. The DHCP option was available when the 3.5 Zero client firmware was launched.

Note: Teradici is only supporting 2,000 devices per MC.


#VDI Tip 64: Follow the Network Checklist

Funny thing about Virtual Desktop Infrastructure, it usually relies heavily on the network. Most of my last two days has been spent troubling shooting dropped PCoIP packets, so I feel it’s timely to make sure you have your basis covered.

So here is the big tip of the day, Read and follow this check list – PCoIP Virtual Desktop Network Design Checklist

Networking isn’t my strongest skill but luckily I work with some really smart people. I think the biggest take away from the checklist is WRED.(Weighted Random Early Detection). It provides preferential traffic handling for packets with higher priority. It can selectively discard lower priority traffic when the interface begins to get congested. Try to get your PCoIP traffic prioritized just under VoIP traffic. The above document notes ” Do not configure WRED on the physical interface as it will override all other QoS policies”. Most traffic monitoring tools are not granularity enough to catch the spikes in traffic. In the land PCoIP, 1 minute intervals does not pass the test.

If you have access to your Cisco Router, you can check for drop packets by using the CEF (Cisco Express Forwarding) commands.
show cef drop
show ip cef switching statistics

You can also check for high CPU utilization. Sometimes high CPU utilization will cause buffering. Buffering = BAD

Run something different than Cisco? Please comment and leave commands for other vendors.