Re:Remote Desktop Protocol Improvements in Windows 10
by jrcii on Tuesday January 12, 2016 @10:12AM
(#10887810)
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.
[ Parent
| on HN ]
Re:Remote Desktop Protocol Improvements in Windows 10
by smithkl42 on Tuesday January 12, 2016 @10:38AM
(#10887993)
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.
Re:Remote Desktop Protocol Improvements in Windows 10
by jrcii on Tuesday January 12, 2016 @11:09AM
(#10888170)
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?
Re:Remote Desktop Protocol Improvements in Windows 10
by untog on Tuesday January 12, 2016 @12:22PM
(#10888739)
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.
Re:Remote Desktop Protocol Improvements in Windows 10
by FireBeyond on Tuesday January 12, 2016 @01:11PM
(#10889144)
On your Server, check the Computer Properties for Remote Access. One property discusses allowing Remote Desktop, another discusses mandating certificates, versus warning.
Re:Remote Desktop Protocol Improvements in Windows 10
by ghurlman on Tuesday January 12, 2016 @11:07AM
(#10888151)
It doesn't require one, unless your group policy (or local server policy) has been set as such.
Re:Remote Desktop Protocol Improvements in Windows 10
by jrcii on Tuesday January 12, 2016 @11:10AM
(#10888179)
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.