I guess I should have posted more.
Resources issues can be a reasons for disconnect for sure with either network or vDesktop hardware resources both physical and virtual. If you think you might be having PCoIP or network problems, there are tools out there that can be very help in determining the status, stats, and health of your View sessions. You can get them at http://mindfluxinc.net/?cat=19 . Look for a tool called PCoIPConfig.exe. there are a few other tools at that website as well. It might be able to help you rule out dropped packets or network latency at least. You can take measurements on latency and compare with VMware recommended thresholds.
My personal disconnect issue persisted after setting the the resolution down even though it seemed to improve. My issue ended up being solved by two things after talking with Teradici who actually created PCoIP:
1. Resetting the power policy on the parent VM and turning all items to be always on/never falling asleep
2.
- Uninstalling VMware Tools, Shutting down the parent VM (not just rebooting)
- Uninstalling View Agent, Shutting down the parent VM (not just rebooting)
- Installing VMware Tools, Shutting down the parent VM (not just rebooting)
- Installing View Agent, Shutting down the parent VM (not just rebooting)
I had some trouble removing the VMware Composer service n some of my parent VMs after the agent removal, but I disabled the service, removed it from the registry, and deleted all the associated files. I was then able to reinstall the agent cleanly.
My environment for View Desktop with linked clones
VM: Windows 7 32bit
Processor: 2vCPU with dual cores (appears as 4)
RAM: 4GB
Hard disk: 60 GB
vSphere 5.1
Server: Dell R715 with 2 CPU with 12 Cores @ 2.4Ghz and 128 GB of RAM.
Good luck
