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.

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


Variable Name


Broker specific


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.

User specific


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.

Desktop specific


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 bridged networking, create and deploy a GPO to add one of the following registry keys and set the key to 1.

Scope of Setting



HKCU\Software\VMware, Inc.\VMware VDM\Client\offlineDesktopUseBridgedNetworking

Connection Server and user specific

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


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

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.