5.2

n
To override the default behavior so that the local desktop uses only the number of CPUs 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\disableOfflineDesktopCPUScaleup
Server and user specific
HKCU\Software\VMware, Inc.\VMware
VDM\Client\ broker_guid \ remote_user_sid \disableOfflineDeskto
pCPUScaleup
The
value 1 indicates that disableOfflineDesktopCPUScaleup is on, and the value 0 indicates that it is off.
n
To set a specific number of CPUs that the View desktop can use when running locally, create and deploy
a GPO to add one of the following registry keys that specify the number of CPUs, up to 2.
Scope of Setting Path
Client-wide
HKCU\Software\VMware, Inc.\VMware
VDM\Client\offlineDesktopDefaultCPUScaleupValue
Server specific
HKCU\Software\VMware, Inc.\VMware
VDM\Client\ broker_guid \offlineDesktopDefaultCPUScaleupValue
Server and user specific
HKCU\Software\VMware, Inc.\VMware
VDM\Client\ broker_guid \ remote_user_sid \offlineDesktopDefaul
tCPUScaleupValue
Server, user, and desktop specific
HKCU\Software\VMware, Inc.\VMware
VDM\Client\ broker_guid \ remote_user_sid \ desktop_ID \offlineDe
sktopDefaultCPUScaleupValue
If
you specify an invalid value, the value is ignored and the default is used. If you specify more CPUs than
are available on the host, the local desktop does not power on, and an error message appears. If you set
the value to a number higher than 2, the value 2 is used.
The settings go into effect when the local desktop is powered on, except in the case of the setting that allows
the reported required memory to be less than that set on vCenter Server. That setting is read only when the
desktop is checked out.
Change the Network Type from NAT to Bridged
By default, the virtual network type of a View desktop changes to NAT (network address translation) when
the desktop is checked out for use on a local system. You can override this behavior to use bridged networking
so that the View desktop has its own identity on the network.
With bridged networking, the virtual network adapter in the View desktop connects to the physical network
adapter in the host computer. Bridged networking makes the View desktop visible to other computers on the
network and requires the desktop to have its own IP address.
NAT configures a virtual machine to share the IP and MAC addresses of the host. The View desktop and the
client host share a single network identity on the network.
To change these defaults for all local desktops or for specific local desktops on a client host, you must configure
Windows registry settings. You can then use standard Windows tools such as Group Policy Objects (GPOs) to
deploy these registry settings.
Chapter 14 Managing Local Desktops
VMware, Inc. 331