With View Manager, you create pools of desktops that deliver View desktop access to clients. View Manager deploys pools from desktop sources, which can be virtual machines that are managed by vCenter Server, virtual machines that run on another virtualization platform, or physical computers, terminal servers, or blade PCs.

You can create several types of desktop pools. You can also provision an individual desktop by deploying a manual pool with a single desktop source.

To create an automated desktop pool, View Manager dynamically provisions desktops based on settings that you apply to the pool. View Manager uses a virtual machine template as the desktop source for the pool and creates a new virtual machine in vCenter Server for each desktop.

To create a linked-clone desktop pool, View Composer generates linked-clone virtual machines from a snapshot of a parent virtual machine. View Manager dynamically provisions the linked-clone desktops based on settings that you apply to the pool.

To create a manual desktop pool, View Manager provisions desktops from existing desktop sources. You select a separate desktop source for each desktop in the pool.

You can use Microsoft Terminal Servers to provide Terminal Services sessions as desktops to View clients. View Manager manages Terminal Services sessions in the same way that it manages other View desktops.

When you create a desktop pool, you select configuration options that determine how the pool is managed and how users interact with the desktops.

You can configure a power policy for the virtual machines in a desktop pool if the virtual machines are managed by vCenter Server.

You can configure desktop pools to enable ESXi hosts to cache virtual machine disk data. This feature, called View Storage Accelerator, uses the Content Based Read Cache (CBRC) feature in ESXi hosts. View Storage Accelerator can reduce IOPS and improve performance during boot storms, when many desktops start up or run anti-virus scans at once. The feature is also beneficial when administrators or users load applications or data frequently. To use this feature, you must make sure that View Storage Accelerator is enabled for individual desktop pools.

When many users require the same desktop image, you can create one large automated pool from a single template or parent virtual machine. By using a single base image and pool name, you can avoid dividing the desktops arbitrarily into smaller groups that must be managed separately. This strategy simplifies your View deployment and administration tasks.