5.2

Similarly, the local View desktop can use up to two CPUs available on the client host if the View desktop is
running a Windows Vista or later operating system.
You
can change the defaults and specify the scope of the setting. The setting can apply to all local desktops on
the client or, depending on the setting, it can apply to a specific desktop or to all desktops from a specific View
Connection Server instance that a specific user is entitled to use on the client.
To change these defaults, you must configure Windows registry settings. You can then use standard Windows
tools such as Group Policy Objects (GPOs) to deploy these registry settings.
Prerequisites
n
If you plan to set a specific number of CPUs that the local desktop can use, power off the local desktop.
n
Because in many cases you can specify the scope of the setting, determine the IDs you will need to specify.
Table 14-6. Identifiers Used in Registry Settings for Local Mode Resource Usage
Scope
Variable
Name Description
Server specific broker_guid Globally unique identifier for the View Connection Server instance or group. Use
the vdmadmin -C command to determine the GUID.
See “Setting the Name of a View Connection Server Group Using the -C
Option,” on page 414.
Server and user
specific
remote_user_si
d
The security ID of the end user. Use the ADSI Edit utility on a View Connection
Server host and find the value of the pae-SIDString field of
CN=machine_CN,OU=Servers,DC=vdi,DC=vmware,DC=int.
Server, user, and
desktop specific
desktop_ID The ID of the View desktop. Use the ADSI Edit utility on a View Connection
Server.
The ID is listed in OU=Applications of DC=vdi,DC=vmware,DC=int. The
desktop ID is the distinguished name that uses the display name of the desktop
pool: CN=pool_display_name,OU=Applications,DC=vdi,DC=vmware,DC=int.
You can also find the broker GUID in the mvdi.lst file on the client computer. On Windows XP, the file
is located in the C:\Documents and Settings\
user_name \Local Settings\Application Data\VMware\VDM
folder. Open the file and search for brokerGUID. The remote user security ID is also listed in this file. Open
the file and search for user-sid.
Procedure
n
To override the default behavior so that the local desktop uses only the amount of memory configured in
vCenter Server, create and deploy a GPO to add one of the following registry keys and set the key to 1.
Scope of Setting Path
Client-wide
HKCU\Software\VMware, Inc.\VMware
VDM\Client\disableOfflineDesktopMemoryScaleup
Server and user specific
HKCU\Software\VMware, Inc.\VMware
VDM\Client\
broker_guid \ remote_user_sid \disableOfflineDeskto
pMemoryScaleup
The value 1 indicates that disableOfflineDesktopMemoryScaleup is on, and the value 0 indicates that it is
off.
Chapter 14 Managing Local Desktops
VMware, Inc. 329