Yesterday Pano Logic announced the release of its VDI platform Pano System 3.0.
The new product introduces the support for Windows 7 and the integration of VMware View 4 Manager into the Pano System console.
This last feature is specifically targeting large enterprises as Pano marketing literature is pretty clear about when View Manager makes sense in their VDI architecture:
For most Pano System deployments, the only VMware products needed are vSphere’s ESX or ESXi and vCenter Server.
Suggested uses for View Manager with the Pano System:
1. You need to manage a mixed or hybrid VDI client device population that includes both Pano Devices and thin clients or PCs running View Client.
2. Your initial deployment has over a 1,000 virtual desktops and is expected to grow.
3. You have 1,000 or more DVMs, storage space is a critical cost factor, and your IT group has the VMware expertise to implement View Composer’s linked clones.
Another interesting point in the company’s documentation is how it positions the proprietary Pano Direct Protocol against the new VMware/Teradici PCoIP:
PCoIP is an optional protocol for View 4 Clients and isn’t required for VDI. PCoIP was designed for edge cases rather than VDI – e.g. remote computing where a single user performing graphically intensive work, such as video editing or CAD/CAM design, is connected one-to-one to a dedicated workstation or blade server, often over low bandwidth wide area networks – and requires either proprietary chips or excessive processing power at both the server and the endpoint, driving up hardware and software costs.
The Pano Direct Protocol, built into all Pano Devices and Pano Manager, was purpose-built just for VDI and zero clients. It acts as a low-level highly efficient bus extension protocol that assumes there is no processing being done (or even possible) on the zero client device and delivers a VDI session over a local area network that typical users find equivalent to using a desktop PC. It doesn’t require any extensions or specialized compression processing on either the server or the endpoint, keeping costs and complexity down.