I'm currently testing Windows Hello for Business (WHfB) with a colleague and we're facing an issue. When using the RDP client, it keeps asking for a PIN by default, which isn't working for us. From what I gather, we would need to set up a Public Key Infrastructure (PKI) to enable RDP to function properly with the PIN, but that's not an option for us right now. We need to connect to both local servers within our Active Directory and also to external clients, and I'm not sure if the RDP client only prompts for a PIN when connecting to servers joined to AD. I'm looking for a way to stop the RDP client from asking for a PIN every single time we try to connect to a Remote Desktop Services (RDS) server. Is there a way to bypass this requirement while still using WHfB to log in to our computers?
4 Answers
When I connect to my virtual PC, it prompts me for a PIN initially, but what I do is click on 'More Choices', select my ID, and enter my password. However, I can see why you'd want to avoid those extra clicks every time.
Since we have PKI in place, I went with Kerberos Cloud Trust, and honestly, the setup wasn't too troublesome. If you're logging into the server with your current user account, using 'More Choices' works. But if you're connecting with a different account, make sure to specify that before connecting.
If you're using WHfB, why not implement Single Sign-On (SSO) for your RDS sessions? I followed a guide that allowed me to click on the RDP link without any prompts, logging in automatically to the RDS server. You could check it out for an easier solution!
It seems like the default login method is tied to how you're connecting. I also use a different account to access servers and have an RDP file set up with my username already included, which makes it smoother for me.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures