From the initial install on VMware View, accessing View desktop using the PCoIP protocol would fail (the user was still being logged in). However, using the RDP protocol would connect properly to desktop-VM's.
After perusing of the event logs on all 3 devices (client, connection broker, Desktop-VM), the common theme was that something on the Desktop-VM was killing the session connection to the client, after login. I could see the session connection errors in the logs.
Changes were made to the network environment and the available video memory on the agent VM. Several testing scenarios were exercised, but it still seemed to be a Desktop-VM problem.
The issue turned out to be caused by the update of ESXi from 4.0 Update 1 to 4.0 Update 2. This updated VMware Tools for the platform, which created an incompatibility between it and the VMware View Agent, which caused the PCoIP protocol to no longer function.
The solution was to download the patched View agent software, uninstall the current agent and install the patched version. This forum post highlights the issue and the resolution (at least for us):
Upgrading VMware Tools in a virtual desktop causes PCoIP connections to fail
VM dt-xp001 was the first to be patched. There were some issues getting the broker to recognize the new agent (reboot of the broker) but once it was recognized, PCoIP was working properly. We are now able to connect over PCoIP from Vista (x32) and Windows Server 2003 VM (x32).
The other Desktop-VM's will be patched over the weekend.
No comments:
Post a Comment