Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

AllowDirectRDP Group Policy settings are supported on Windows 10 1909 and later (76593)

Last Updated: 4/20/2022Categories: TroubleshootingTotal Views: 6145Language:
Chinese (Simplified)JapaneseEnglish

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

AllowDirectRDP group policy setting is disabled.

You are using an earlier version of Windows 10 1909 virtual desktop.

Even though the AllowDirectRDP is disabled, you can reconnect to existing session between Horizon Client and virtual desktop by using Microsoft Remote Desktop connection (mstsc.exe).

Cause

There are some major design change which has been made on below mentioned Windows 10 versions.

As part of the design change, some Windows APIs which were specifically used in Horizon's reconnect sequence changed their behavior.

Due to that, Horizon Agent cannot block re-connection from mstsc.exe anymore even though the AllowDirectRDP is disabled.

Currently these Windows versions are confirmed as affected:

Windows 10 1709

Windows 10 1803

Windows 10 1809

Windows 10 1903

Resolution

AllowDirectRDP determines if non-Horizon clients can connect directly to Horizon managed Desktops using RDP. When disabled, the agent will only permit Horizon-managed connections via Horizon Client or Horizon HTML Portal. This policy setting is enabled by default.

This Group Policy setting is supported on Windows 10 1909 and later.
If you are running an earlier versions of Windows 10 1909, follow the steps in the Workaround Section.

Workaround

As a workaround, if you need to block RDP, you must block all incoming RDP connection, including those coming from the Horizon Client.

To block incoming RDP on individual virtual desktops:

On the virtual desktop, launch systempropertiesremote.exe

Select Don't allow remote connection to this computer and click OK

To block incoming RDP by using group policy setting:

On Active Directory host, open Group Policy Management Editor

Go to Computer Configuration > Policies > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Connections

Disable the policy Allow users to connect remotely by using Remote Desktop Services

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
vCloud Director 设备安装最佳实践 (76559)

KB
•
vCloud Director Appliance のインストールのベスト プラクティス (76559)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Horizon

Related Versions:

Take Our Survey

Support Assistant