Hero Banner

Feedback & Support Discussions

Reply
Level 2 Contributor

Enable Remote Desktop - Fails with Group Policy

On a Windows 10 workstation, the "Allow users to connect remotely by using Remote Desktop Services" Group Policy used to enable RDP fails to change the below value:

 

Remote Desktop New School Managed.jpg

As you can see, it shows as being managed, but the value is off. The below image, from the same machine with the GPO applied, it shows as RDP being enabled. But with the above value still being off, you cannot RDP.

 

Remote Desktop Old School Managed.jpg

 

This has been tested on Windows 10 versions 1803, 1809 and 1903. What we've observed is that without Group Policy set, in the "Settings" app, if we set "Enable Remote Desktop" to on, it changes the 'old school' System Properties and vice-versa. 

 

It appears to be a bug in Group Policy. As a workaround, do you know what registry keys we could use to turn "Enable Remote Desktop" on for all users on a device?

 

Thanks,

 

Matt

1 ACCEPTED SOLUTION

Accepted Solutions
Level 2 Contributor

Re: Enable Remote Desktop - Fails with Group Policy

Turns on the Windows 10 "Settings" value for Enable Remote Desktop looks at whether the firewall port is open for Remote Desktop Services or not. Once this value is set in Group Policy, it turns on and it works. So it was a firewall issue, not a setting issue.

To be honest, feels silly that we missed this one in troubleshooting. However, I feel like we would have found the lack of open firewall port for this if the value had of turned on and RDP then just failed. Would have been the first thing to look into when the setting shows as on and the action failed.

1 REPLY 1
Level 2 Contributor

Re: Enable Remote Desktop - Fails with Group Policy

Turns on the Windows 10 "Settings" value for Enable Remote Desktop looks at whether the firewall port is open for Remote Desktop Services or not. Once this value is set in Group Policy, it turns on and it works. So it was a firewall issue, not a setting issue.

To be honest, feels silly that we missed this one in troubleshooting. However, I feel like we would have found the lack of open firewall port for this if the value had of turned on and RDP then just failed. Would have been the first thing to look into when the setting shows as on and the action failed.