We've been investigating VMware View 4 as a VDI connection broker for some time now.  We've gone through an extensive pilot testing phase, and sadly have decided it's not ready for general deployment at this time.  There are a number of deal-breaker missing and broken features that we think should be brought to light.

1. Documentation for View is essentially nonexistent.  There is the View Administration Guide, but it's little more than an overview and doesn't go into any significant technical detail.  If you need to do something more sophisticated, you're on your own.
2. The PCoIP protocol will not work though a View Secure Gateway or fire wall.  If you planned on putting a View server in your DMZ as a security precaution, you will be limited to using the RDP protocol.  If you want to use PCoIP, you will require a VPN connection.  PCoIP requires a direct connection to the virtual workstation.
3. Web access to a View desktop requires a pared-down version of the thick client be installed.  This requires administrative access to the machine.  It only supports Internet Explorer.  The version installed by the web access doesn't support local printer or USB redirection, and you must completely uninstall the View client and reinstall the full version to use those features.  This makes the web access feature essentially useless for road warriors that don't carry their laptops with them.
4. Printer redirection using the full View client is unreliable.  Local printers will not map properly on 50% of installations, with no rhyme, reason, or logging information to troubleshoot the issue.
5. PCoIP does not presently support printer redirection.  If your users need to print to local printers, they will need to use the RDP protocol.
6. PCoIP graphical performance over a WAN link is unacceptable, and due to the lack of documentation there seems to be no way to improve it.  Users experienced slow screen refresh rates & graphical distortions doing things as simple as scrolling through a web page.   PCoIP clients bandwidth spiked to 1.5 Mbit (on a 20 Mbit circuit) and despite our best efforts we could not get the clients to use more than that.  RDP clients would spike up to 6.0 Mbit, and performance perception was excellent.  Idle, PCoIP clients used under 20 kbps, less than half of RDP clients.
7. Teradici Thin-Clients (marketed and sold through Wyse, eVGA, and others) require a direct connection to the workstation, regardless of your protocol choice.  Thin clients will not work through a firewall or VCS, if you want to use them at a remote site they require a site-to-site VPN connection.
8. Teradici thin-clients suffer from a number of glitchy graphical issues.  For example, some grey shades are rendered as a light green.
9. With the Teradici thin-clients performance rendering some kinds of list boxes in windows (such as your Outlook Inbox) are achingly slow.  30 seconds slow.  For users that get more than a message every few minutes, Outlook is effectively rendered unusable.  Overall graphical performance rendering all objects with thin-clients is sub-par.

Given VMware's marketing blitz surrounding View, I hope this helps shed some light on this potentially exciting product.  Overcoming these limitations has yielded some interesting solutions for SymbioSystems, including a thick-client we put together that will be detailed in a forthcoming post.