5.2

Prerequisites
n
Because
in many cases you can specify the scope of the setting, determine the IDs you will need to specify.
Table 14-8. 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
u
To override the default behavior so that the local desktop uses bridged networking, 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\offlineDesktopUseBridgedNetworking
Server and user specific
HKCU\Software\VMware, Inc.\VMware
VDM\Client\
broker_guid \ remote_user_sid \offlineDesktopUseBri
dgedNetworking
Server, user, and desktop-specific
HKCU\Software\VMware, Inc.\VMware
VDM\Client\ broker_guid \ remote_user_sid \ desktop_ID \offlineDe
sktopUseBridgedNetworking
A value of 1 sets the desktop to use bridged networking. A value of 0 sets it to use NAT, which is the
default.
The setting takes effect when the end user powers on the local desktop.
Configuring an HTTP Cache to Provision Local Desktops Over a WAN
You can use an HTTP cache to facilitate the provisioning of linked-clone, local desktops. Configuring an HTTP
cache benefits remote offices and branch offices that are connected to the datacenter over a WAN. The HTTP
cache reduces the performance cost of transferring View Composer base images over a WAN.
If you configure linked-clone desktops to use local mode at remote offices, your WAN might not have the
bandwidth to efficiently download the View Composer base image directly to each local computer. For
example, repeatedly transferring a 6GB base image might be prohibitive.
If you set up an HTTP cache, the base image is stored in the proxy server's cache when the first user checks
out a desktop. When subsequent users check out desktops, the base image is transferred over the LAN within
the local office.
VMware Horizon View Administration
332 VMware, Inc.