In an emergency situation where a tenant is down or unreachable but the network is still working, you can globally instruct all DaaS Agents to allow temporary RDP native access so end users can connect without the broker being functional.

To enable this temporary functionality, add the registry keys described below to the desktop VMs, either directly or via GPO policy. Add the keys in one of the following locations, depending on whether the DaaS Agent is installed on a 32-bit or 64-bit Windows system:

  • HKEY_LOCAL_MACHINE\SOFTWARE\VMware, Inc.\VMware DaaS Agent (32bit)

  • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\VMware, Inc.\VMware DaaS Agent (64bit)






0 = do not allow direct connections

1 = allow direct connections.



Date and time until which direct connections are allowed if direct connections access is enabled (AllowDirectConnections = 1).

Date and Time Format: YYYY-MM-DD HH:MM:SS

This functionality requires the following:

  • DaaS Agent 17.2 is in use.

  • RDP access is not being blocked via View or any other GPOs.

  • The user is in a group associated with a desktop assignment. The DaaS Agent configures the same users/groups for RDP access in the desktop (local RDP group).


The default Group Policy refresh interval is 90 minutes. You have to perform additional steps to force a refresh sooner than that. See the relevant Microsoft documentation for more information.