Windows 10: Windows Hello for Business

We are piloting Windows Hello for Business on laptops running Windows 10 21H2. Hello is configured to used Cloud Hybrid Trust recommended and for the majority of the 70 users trialling all is good. What is now hard to ignore is 2 users have randomly hit an intermittent issue whereby initial desktop sign-in via biometric or PIN fails. On providing either method a blue spinning circle remains until it eventually times out. One user reboot and all worked once more. The other just decided to sign-in using existing username/password against AD. Issue occurs regardless if device is connected

:)

 

Windows 10 Hello for Business with Physical Smartcard and roaming uses across shared PC's

Hi Rosenbrier,



Thank you for writing to Microsoft Community Forums.



With the recent ratification of security keys by FIDO, Windows Hello allows security authentication for shared devices that allows full roaming experience. For more information, I would suggest you to refer to the article
Windows Hello and FIDO2 Security Keys enable secure and easy authentication for shared
devices and see if it helps.



If you have any further query regarding the same, I would suggest you to post your query in the
IT Pro TechNet Forums, where we have support professionals well equipped with the
knowledge on Windows Hello for Business.



Additional Info:

• Implementing strong user authentication with Windows Hello for Business
  
• Windows Hello for Business Frequently Asked Questions
  
  

Regards,

 

Can't disable Windows Hello for Business

I receive this error in Event Viewer whenever I boot Windows 10 Pro version 1709 build 16299.309.

Windows Hello for Business provisioning will not be launched.

Device is AAD joined ( AADJ or DJ++ ): Not Tested

User has logged on with AAD credentials: No

Windows Hello for Business policy is enabled: Not Tested

Local computer meets Windows hello for business hardware requirements: Not Tested

User is not connected to the machine via Remote Desktop: Yes

User certificate for on premise auth policy is enabled: Not Tested

Machine is governed by none policy.

See Windows Hello for Business cloud Kerbeity for more details.

I tried the following suggestion:

"Type gpedit.msc Go to Computer Configuration > Administrative Templates > Windows Components > Microsoft Passport for Work OR Windows Hello for Business Edit "Use Microsoft Passport for Work" OR "Use Windows Hello for Business" and set it to disabled."

I checked the registry and \HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\PassportForWork Enabled is set to 0.

I am using the Administrator account.

The error continues at every bootup.

Thank you.

 

Windows Hello vs Hello for Business?

I’m sure for a consumer it’s impossible to setup Hello for Business since it’s dependent on a certificate based authentication vs using just the Hello which uses a convenience PIN, which is a bit less secure than Hello for Business. And plus, Hello for Business requirements are that a pc needs to be joined to Azure AD which a home user account cannot accomplish. Is it still good idea for a consumer like me on a Standalone pc to use just the convenience PIN to login to Windows?