5.2

n
To
set a specific amount of memory 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 in megabytes, up to 32GB.
Scope of Setting Path
Client-wide
HKCU\Software\VMware, Inc.\VMware
VDM\Client\offlineDesktopDefaultMemoryScaleupValue
Server specific
HKCU\Software\VMware, Inc.\VMware
VDM\Client\
broker_guid \offlineDesktopDefaultMemoryScaleupVa
lue
Server and user specific
HKCU\Software\VMware, Inc.\VMware
VDM\Client\ broker_guid \ remote_user_sid \offlineDesktopDefaul
tMemoryScaleupValue
Server, user, and desktop specific
HKCU\Software\VMware, Inc.\VMware
VDM\Client\ broker_guid \ remote_user_sid \ desktop_ID \offlineDe
sktopDefaultMemoryScaleupValue
If
you set the value to a number that is too large, the local desktop does not power on, and an error message
appears.
n
To check out a desktop that was configured to require more memory than is available on the client host,
create and deploy a GPO to add the following registry key that specifies the number of megabytes that
you want the local client to report that it has available.
HKCU\Software\VMware, Inc.\VMware VDM\Client\offlineDesktopReportedHostMemoryValue
Setting this value to one that is greater than or equal to the memory required by the View desktop allows
you to check out and run the View desktop if the client has enough spare memory to run the virtual
machine.
Scope of Setting Path
Client-wide
HKCU\Software\VMware, Inc.\VMware
VDM\Client\offlineDesktopReportedHostMemoryValue
Server specific
HKCU\Software\VMware, Inc.\VMware
VDM\Client\ broker_guid \offlineDesktopReportedHostMemoryValu
e
Server and user specific
HKCU\Software\VMware, Inc.\VMware
VDM\Client\ broker_guid \ remote_user_sid \offlineDesktopReport
edHostMemoryValue
Server, user, and desktop specific
HKCU\Software\VMware, Inc.\VMware
VDM\Client\ broker_guid \ remote_user_sid \ desktop_ID \offlineDe
sktopReportedHostMemoryValue
If the client does not have enough spare memory, you can use the
offlineDesktopDefaultMemoryScaleupValue setting in conjunction with the
offlineDesktopReportedHostMemoryValue setting.
For
example, if your client system has 2GB of memory and the View desktop is configured to require 2GB
of memory, you will not be able to check out the View desktop because some memory is also required for
client hosted virtualization. You can, however, use the registry setting
offlineDesktopReportedHostMemoryValue = 2048, so that you can check out the desktop, and use the
registry setting offlineDesktopDefaultMemoryScaleupValue = 1024 so that the View desktop uses only
1GB of memory when it runs locally.
VMware Horizon View Administration
330 VMware, Inc.