Hacker News Reader

This post doesn't mention it but I noticed that RDPing to a remote Windows Server from Windows 10 now requires the server to be using a certificate.

View on HN

I'm pretty sure it doesn't need one - it just warns you if the remote server doesn't have one. Kind of like how browsers will warn you if a remote site's SSL cert is bad, but they'll let you through if you insist.

That's not my experience, it insists and refuses to connect.

Edit: I'm not sure who downvoted me, what do you want me to post a screencast to prove it? Do you think I'm making this up or what?

what do you want me to post a screencast to prove it?

Given that multiple people are replying to you saying that they do not experience the same thing... yes, probably.

On your Server, check the Computer Properties for Remote Access. One property discusses allowing Remote Desktop, another discusses mandating certificates, versus warning.

It doesn't require one, unless your group policy (or local server policy) has been set as such.

That's not what I've seen. No policy has been changed on my Windows Server, Windows 7 and prior RDP clients connect fine, Windows 10 clients refuse because of lack of certificate.

I just tested on a fresh windows 10 install. Works fine.

Windows 10 to Windows 2008 R2, no cert. I just click past the warning. Everything works just as it did with Win7.

Reply on news.ycombinator.com