After a local desktop is checked out, it takes advantage of the memory and CPU capabilities of the local system, regardless of the memory and CPU settings specified for the virtual machine in vCenter Server. You can override this default behavior.

By default, the amount of RAM allocated to a View desktop that is checked out for use in local mode is automatically adjusted to be a certain amount of the RAM that is available on the client host.

The formula takes into consideration how much memory is available to split between the host and guest View desktop. A Windows XP operating system requires a minimum of 512MB RAM. A 32-bit Windows 8, Windows 7, or Windows Vista operating system requires a minimum of 1GB RAM. The amount of memory available to split is the total amount of RAM on the host minus the minimum RAM required for the host and guest operating systems.

Memory Allotted to Local View Desktops

Memory Allocation

Windows XP Guests

Windows 8, Windows 7, and Vista Guests

Minimum

512MB

1GB

Best effort

512MB + (Available/2)

1GB + (Available/2)

Maximum

2GB

4GB

For example, if a Windows 7 host has a total of 2GB of RAM, to run a Windows 7 View desktop locally would require 2GB of RAM, with 1GB of RAM allocated to the host and 1GB of RAM allocated to the local View desktop. If the host had 3GB of RAM, 1.5GB of RAM would be allocated to the host and 1.5GB of RAM would be allocated to the local View desktop.

Note

The automatic adjustment of memory allocation never sets the memory of the local desktop to a lower value than what is configured in vCenter Server.

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.

If you plan to set a specific number of CPUs that the local desktop can use, power off the local desktop.

Because in many cases you can specify the scope of the setting, determine the IDs you will need to specify.

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.

Server and 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=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.

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\disableOfflineDesktopMemoryScaleup

The value 1 indicates that disableOfflineDesktopMemoryScaleup is on, and the value 0 indicates that it is off.

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\offlineDesktopDefaultMemoryScaleupValue

Server and user specific

HKCU\Software\VMware, Inc.\VMware VDM\Client\broker_guid\remote_user_sid\offlineDesktopDefaultMemoryScaleupValue

Server, user, and desktop specific

HKCU\Software\VMware, Inc.\VMware VDM\Client\broker_guid\remote_user_sid\desktop_ID\offlineDesktopDefaultMemoryScaleupValue

If you set the value to a number that is too large, the local desktop does not power on, and an error message appears.

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\offlineDesktopReportedHostMemoryValue

Server and user specific

HKCU\Software\VMware, Inc.\VMware VDM\Client\broker_guid\remote_user_sid\offlineDesktopReportedHostMemoryValue

Server, user, and desktop specific

HKCU\Software\VMware, Inc.\VMware VDM\Client\broker_guid\remote_user_sid\desktop_ID\offlineDesktopReportedHostMemoryValue

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.

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\disableOfflineDesktopCPUScaleup

The value 1 indicates that disableOfflineDesktopCPUScaleup is on, and the value 0 indicates that it is off.

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\offlineDesktopDefaultCPUScaleupValue

Server, user, and desktop specific

HKCU\Software\VMware, Inc.\VMware VDM\Client\broker_guid\remote_user_sid\desktop_ID\offlineDesktopDefaultCPUScaleupValue

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.