You can use an HTTP cache to facilitate the provisioning of linked-clone, local desktops. Configuring an HTTP cache benefits remote offices and branch offices that are connected to the datacenter over a WAN. The HTTP cache reduces the performance cost of transferring View Composer base images over a WAN.

If you configure linked-clone desktops to use local mode at remote offices, your WAN might not have the bandwidth to efficiently download the View Composer base image directly to each local computer. For example, repeatedly transferring a 6GB base image might be prohibitive.

If you set up an HTTP cache, the base image is stored in the proxy server's cache when the first user checks out a desktop. When subsequent users check out desktops, the base image is transferred over the LAN within the local office.

To complete a check-out operation, View Transfer Server still must transfer each user's linked-clone OS disk and persistent disk from the datacenter over the WAN, but these disks are a fraction of the size of the base image.


To allow a caching proxy server to pass on View Composer base images and other data between local desktops and the datacenter, you must configure certain settings in View Connection Server.


A View Composer base-image package can contain files that are larger than a gigabyte, too large for many proxy servers to cache. You can configure View Transfer Server to split base-image packages into files that are no larger than the capacity of the proxy-server cache.


To support HTTP caching, you must configure the client computers that host local desktops to transfer the desktop data through a caching proxy server. You also must configure the client computers to use the proxy server's HTTP address for internet connections.


When you set up a proxy server to support HTTP caching for local desktops, you must configure the capacity of the cache and the HTTP connection method.