These users can check out a View desktop and run it locally on their laptop or desktop even without a network connection.

View Client with Local Mode provides benefits for both end users and IT administrators. For administrators, local mode allows View security policies to extend to laptops that have previously been unmanaged. Administrators can retain tight control over the applications that run on the View desktop and can centrally manage the desktop just as they do remote View desktops. With local mode, all the benefits of Horizon View can also extend to remote or branch offices that have slow or unreliable networks.

For end users, benefits include the flexibility of continuing to use their own computers online or offline. The View desktop is automatically encrypted and can easily be synchronized with an image in the datacenter for purposes of disaster recovery.

Local mode users might need to access their desktop applications and data from their laptop when no network connection is available. In addition, they might need this data to be regularly and automatically backed up to the datacenter in the event that the laptop is ever lost, damaged, or stolen. To provide these capabilities, you can use the following pool settings.

When creating a virtual machine to base the pool on, configure the minimum amount of RAM and virtual CPUs required by the guest operating system. Desktops that run in local mode adjust the amount of memory and processing power they use based on that available from the client computer.

Create an automated pool so that desktops can be created when the pool is created or can be generated on demand based on pool usage.

Use dedicated assignment because local mode users need to log in to the same desktop every time.

Create View Composer linked-clone desktops so that desktops share the same base image and use less storage space in the datacenter than full virtual machines.

If you want the provisioning process to generate a unique local computer SID and GUID for each linked clone in the pool, select a Sysprep customization specification when you create the pool. Sysprep creates new SIDs and GUIDs during the initial provisioning and after recompose operations. Because you are not likely to recompose local mode pools, the SIDs and GUIDs are not likely to change.

Include in the pool only desktops that are intended to be used in local mode. Local mode virtual machines can be placed on datastores with lower IOPS requirements than storage intended to support large numbers of remote View desktops.

You can reduce the number of ESX/ESXi hosts required for your local mode pool if you increase the number of virtual machines per ESX/ESXi host. An ESX/ESXi 4.1 host can accommodate up to 500 virtual machines if most are not powered on at the same time, as is frequently the case for local mode pools.

Use the following recommendations to reduce the amount of bandwidth and I/O operations required by each virtual machine and maximize the number of virtual machines on an ESX/ESXi host.

Set a View policy so that end users must use their View desktops in local mode only. With this setting, the virtual machines in the datacenter remain locked and powered off.

Set local mode policies so that end users cannot initiate desktop rollbacks, data backups, or check-ins to the datacenter.

Do not schedule automatic backups.

Do not turn on SSL for provisioning or downloading local mode desktops.

If the performance of View Connection Server is affected by the number of local desktops, set the heartbeat interval to be less frequent. The heartbeat lets View Connection Server know that the local desktop has a network connection. The default interval is five minutes.