3 ms·
How so? In my experience you are prompted to use it, and you can click and use standard credentials if desired. I deployed WHfB at our $LARGE_ENTERPRISE and op
by c0nsumer 6y ago
How so? In my experience you are prompted to use it, and you can click and use standard credentials if desired.
I deployed WHfB at our $LARGE_ENTERPRISE and opted against using BT RSSI as a trusted signal because it's just too unpredictable. Probably because the Windows space is much more varied, but an RSSI that'd work for one device at ~8' away would fail to lock another when two cube rows away. Meaning, we knew users would start to depend on it, but it wouldn't work as they thought.
Thus, still policies of locking machines, it's now just easier to unlock. (And arguably more secure because now less password typing means far fewer chances for keyloggers to get network-usable credentials.)
- bombcar 6y agoI enabled Hello on my VM Windows 10 Enterprise and then was unable to connect via Remote Desktop from my Mac - so it didn't have single sign-on but it wouldn't fall back to anything I could use. So I disabled it and now it's happy.
- c0nsumer 6y agoThanks. I'll test this in the morning. AFAIK it works for us, but I don't know for sure. Which RDP client were you using? And did you disable the password provider (leaving just the WHfB factors)? And you had full Windows Hello for Business? (This one: https://docs.microsoft.com/en-us/windows/security/identity-protection/hello-for-business/hello-identity-verification https://docs.microsoft.com/en-us/windows/security/identity-p...) Or, were you using standard Hello? (The two are similarly named, but are quite different under the covers.)