4.5

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 13-6. Identifiers Used in Registry Settings for Local Mode Resource Usage
Scope
Variable Name Description
Broker 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 293.
User specific remote_user_sid 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=v
di,DC=vmware,DC=int.
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=Applic
ations,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.
Chapter 13 Managing Local Desktops
VMware, Inc. 237