MicrosoftThis is an excellent article! Well written and I agree with the logic of "make it work" instead of registry hacks and "don't bother me" checkboxes.
We are experiencing problems recently with Windows 10 ver 20H2 domain PCs on our network. We have a local CA with relevant certificates being issued. No problems with RDP to servers (2012R2, 2016, 2019) or domain PCs Windows 10 ver 1909 or 2004. With the "Allow connections only from computers running Remote Desktop with Network Level Authentication" checked on the 20H2 PCs, we receive this error.
Domain DNS and DHCP is configured properly and name resolution is working fine. If we uncheck, the "Allow connections..." box, we no longer have that error, but the self-signed cert is being used by RDP, not the one issued by our inhouse CA. I prefer not to use the registry hack to force the RDP service to use the thumbprint of the proper certificate as that will get messy quickly with 100 workstations.
Has anyone else seen this behavior with Windows 20H2 clients?
Once again, we do not have this problem with any earlier versions of Windows 10 nor our servers. Just the 20H2 workstations. Any assistance or recommendations are most welcome.
Regards,
Todd
