To create and deploy View desktops in local mode, you must have the required license, set up a View Transfer Server, use a desktop source managed by vCenter Server, and apply settings and policies specific to local mode.

When you create desktops that can be checked out for use on end users' local systems, in addition to the usual setup tasks, you must complete several tasks for local mode.


Verify that you have a license for the VMware View with Local Mode component.

In View Administrator, go to View Configuration > Product licensing and usage.


Verify that the user account used to access vCenter Server from View Connection Server has the required administrator privileges.

To see which user account is being used, in View Administrator, go to View Configuration > Servers, select the vCenter Server, and click Edit.

The list of privileges required for vCenter Server operations is provided in the VMware View Installation document, in the section about configuring user accounts for vCenter Server.


Install View Transfer Server in a virtual machine and add this server to a View Connection Server configuration.

In View Administrator, go to View Configuration > Servers.


If you plan to use View Composer linked-clone desktops, configure a Transfer Server repository.

In View Administrator, go to View Configuration > Transfer Server Repository.


If you plan to create a manual pool, verify that the desktop source is a virtual machine managed by vCenter Server.


Create a virtual machine in vCenter Server to use as the desktop source.

If you create a virtual machine that has more virtual memory and processors than are available on a local client system, the local version of the desktop will not power on, and an error message will appear.


If you plan to use linked-clone desktops, publish the desktops' View Composer base image as a package in the Transfer Server repository.

You can publish the base image when you create a pool or after the pool is created.


Verify that the Local Mode policy is set to Allow for the desktop pool.

In View Administrator, go to the Policies tab for that pool.


If you want desktops to run only in local mode so that users must always check out the desktop, set the Remote Mode policy to Deny.

In View Administrator, go to the Policies tab for that pool.


Direct end users to install View Client with Local Mode on their local systems.


In addition, take the following considerations into account when planning to deploy local desktops:

When creating automated pools, use dedicated assignment and create the pool only for desktops that are intended to be used in local mode. Virtual machines that are intended for use in local mode can be placed on datastores with lower IOPS than storage intended to support large numbers of remote View desktops. Also, because assigning ThinApp packages to local desktops is not supported, a best practice is to assign ThinApp packages to pools that do not contain any local desktops.

As a standard best practice for desktops, make sure that a unique password is created for the local Administrator account on each View desktop that you plan to use in local mode.

If you configure the desktop to use RSA authentication, end users are prompted for the RSA token when they have a network connection to View Connection Server, but are not prompted when they do not have a network connection.