View Transfer Server is required to support desktops that run View Client with Local Mode (formerly called Offline Desktop). This server requires less memory than View Connection Server.

You must install View Transfer Server on a virtual rather than a physical machine and the virtual machine must be managed by the same vCenter Server instance as the local desktops that it will manage. View Transfer Server Virtual Machine Example lists the virtual machine specifications for a View Transfer Server instance.

View Transfer Server Virtual Machine Example

Item

Example

Operating system

64-bit Windows Server 2008 R2

RAM

4GB

Virtual CPU

2

System disk capacity

20GB

Virtual SCSI adapter type

LSI Logic Parallel or SAS

Virtual network adapter

E1000 (the default)

1 NIC

1 Gigabit

Several operations use View Transfer Server to send data between the View desktop in vCenter Server and the corresponding local desktop on the client system. When a user checks in or checks out a desktop, View Transfer Server transfers the files between the datacenter and the local desktop. View Transfer Server also synchronizes local desktops with the corresponding desktops in the datacenter by replicating user-generated changes to the datacenter.

If you use View Composer linked-clones for local desktops, the disk drive on which you configure the Transfer Server repository must have enough space to store your static image files. Image files are View Composer base images. The faster your network storage disks are, the better performance will be. For information about determining the size of base image files, see the VMware Horizon View Administration document.

Each Transfer Server instance can theoretically accommodate 60 concurrent disk operations, although network bandwidth will likely be saturated at a lower number. VMware tested 20 concurrent disk operations, such as 20 clients downloading a local desktop at the same time, over a 1GB per second network connection.