VMware released VMware View 5.1.1 yesterday (8/16/2012). The update addresses a few different issues, and applies only to VMware View Connection Servers, not View Security Servers, View Transfer Servers, View Composer, or View Clients.
I’ve had several customers ask me for help with the VMware View environment recently, as their users were complaining about performance issues when dragging a window between monitors in a multi-monitor VMware View setup. Performance was otherwise acceptable on the View desktops. I recommended several troubleshooting and remediation steps to get windows to stop “catching” on the border between their two screens, including:
In a lab environment, you have competing priorities. On one hand, individual users want endless amounts of compute, network, and storage resources. They also want consumption of those resources, whether that means delivering individual applications, operating systems, or the entire stack, to be quick and easy. On the other hand, you have a limited amount of compute, network, and storage resources available, and since it's your lab, you don't want to spend tons of time manually delivering solutions to your end users. You also want to have the ability to segregate these users from one another so their individual deployments don't step all over each other.
The sheer number of virtual desktop solutions on the market can be overwhelming for even the most seasoned IT staff, if you combine that with the unknown costs and virtual desktops becomes a non-starter before it even gets on the whiteboard. In an effort to make VDI evaluation and the subsequent roll-out a manageable reality, I have created a 12-step journey into VDI.