VCP5-DT Objective 2.10–Configure the Environment for Local Mode

Objective 2.10 – Configure the Environment for Local Mode

For this objective I used the following resources:

  • VMware View Administration documentation
  • VMware View Installation documentation


Publish Linked Clone Replica to Transfer Server Repository

Refer to section “Configure/Identify Transfer Server Repository” in Objective 2.5 Configure View Transfer Servers

Configure Local Mode Policies

View/Modify Global Settings

Step 1 – Connect and login into the VMware View Administrator console:


Step 2 – Under “Policies” select “Global Policies”


Step 3 – On the far sided of the right side pane the defined global settings for “Local Mode” will be displayed. If changes are needed/required click the “Edit Policies” button:


Step 4 – Make the desired changes and click “OK” to save and exit:


View/Modify Pool Settings

Step 1 – Connect and login into the VMware View Administrator console:


Step 2 – Under “Inventory” select “Pools”. In the right hand pane double click the pool to view/modify its settings:


Step 3 – Click the “Policies” tab in the right side pane navigation window. Click “Edit Policies” under the “Local Mode Policies” section:


Step 4 – Make the desired changes and click “OK” to save and exit:


Ensure Client Device Meets Local Mode Requirements

Supported Operating Systems for Windows-based View Client with Local Mode

OS Version Edition(s) Service Pack
Window 7 32 and 64 bit Home, Enterprise, Professional, and Ultimate None and SP1
Windows XP 32 bit Home and Professional SP3
Windows Vista 32 bit Home, Business, Enterprise, and Ultimate SP1 and SP2

Hardware Requirements for Local Mode Desktops

Client Computer Requirement Description
PC Standard x86 or x86 64-bit compatible
Number of CPU’s Multiprocessor systems are supported
CPU Speed For a Windows XP local desktop, 1.3GHz or faster, 1.6 GHz recommended
For a Windows 7 desktop, 1.3GHz or faster, for Aero effects, 2.GHz or faster
Intel Processors Pentium 4, Pentium M, Core, Core2, Core i3, Core i5, and Core i7 processors
For Windows 7 Aero: Intel Dual Core
AMD Processors Athlon, Athlon XP, Athlon MP, Athlon 64, Athlon X2, Duron, Opteron, TurionX2, Turion 64, Sempron, Phenom, and Phenom II
For Windows 7 Aero: Athlon 4200+ and above
64-Bit Operating Systems Intel Pentium 4 and Core 2, and Core i7 processors with EM64T and Intel Virtualization Technology
Most AMD64 processors (except the earliest revision C Opteron processors)
GPU for Windows 7 Aero nVidia GeForce 8800GT and above
ATI Radeon HD 2600 and above


View Client with Local Mode Limitations and Restrictions

  • Must have a View license that includes the Local Mode component
  • Available only for virtual machines that are managed by vCenter Server
  • Checking out a View desktop that uses virtual hardware version 8 is not supported. If you use vSphere 5 to create virtual machines that will be sources for local mode desktops, be sure to create virtual machines that use virtual hardware version 7
  • You cannot use View Persona Management with desktops that run in local mode

Verify Transfer Server Configuration

Refer to Objective 1.3 – Install View Transfer Server for details.

Identify Local Mode Policies



Local Mode Determines whether users can check out desktops for local use. Also determines whether users can run local desktops while the desktops are checked out.
The default value is Allow
If you change this value to Deny while a desktop is checked out, the user cannot run the desktop in local mode, and the desktop cannot be used remotely because it is still checked out.
User-initiated rollback Determines whether users can discard a local desktop and revert to the remote version
When a user initiates the rollback process, the lock on the remote desktop is released and the local desktop is discarded. If necessary, the user can manually remove and delete the local folder that contains the local desktop data
The default value is Allow.
Max time without server contact Specifies the amount of time in days that a local desktop can run without making contact with View Connection Server for policy updates. If the specified time limit is exceeded, View Client displays a warning message to the user and suspends the desktop.
The default value is 7 days.
On the client side, this expiration policy is stored in a file that is encrypted by a key that is built into the application. This built-in key prevents users who have access to the password from circumventing the expiration policy.
Target replication frequency Specified the interval in days, hours, or minutes between the start of one replication and the start of the next replication. A replication copies any changes in local desktop files to the corresponding remote desktop or View Composer persistent disk in the datacenter
The default value is the No replication setting. If you select At a specified interval, the default replication interval is 12 hours.
You can prohibit scheduled replication by selecting No replication.
The No replication policy does not prohibit explicit replication requests. You can initiate replications in View Administrator, and users can request replications if the User initiated replication policy is set to Allow.
If a replication takes longer than the interval that is specified in the Target replication frequency policy, the next scheduled replication starts after the previous one is completed. The pending replication does not cancel the previous one
For example, the Target replication frequency policy might be set to one day. A replication might start at noon on Tuesday. If the client computer is disconnected from the network, the replication might take longer than 24 hours. At noon on Wednesday, View Client with Local Mode starts the next replication request. After the previous replication is completed, View Client with Local Mode takes a snapshot and starts the pending replication.
User deferred replication Determines whether users can pause active replications. If you enable this policy, a user can defer a replication that is underway. The replication does not resume, and no new replications start, until the deferment period is over.
The default value is Deny. When the value is set to Allow, the deferment period is two hours.
Disk replicated Determines which desktops disks are replicated. This policy affects View Composer linked-clone desktops only. For full virtual-machine desktops, all disks are replicated.
You have these disk-replication choices
Persistent disks
OS disks
OS and persistent disks
Changing this policy affects desktop replication after the next checkout occurs. A change does not affect desktops that are currently checked out.
The default value is Persistent disks
User-initiated check in Determines whether users are allowed to check in desktops that are running in local mode.
The default value is Allow
User-initiated replication Determines whether users are allowed to initiate replications from their desktops when they run in local mode.
The default value is Allow


%d bloggers like this: