However, there can be other reasons as well. This error is usually triggered by an outdated biometric device driver. “Windows Hello is preventing some options from being shown.” Does Microsoft have any plans to stabilize this setup process for simple usage?ġ) I removed it from the domain to see how it behaves: The fingerprint option is enabled.“This option is currently unavailable” “Something went wrong- try again later”. I've also seen a number of posts regarding earlier versions of Win10, and it seems incredibly frustrating that this seems to change with every new release. Is there a way to get Windows Hello working on this domain-joined laptop for fingerprint authentication to sign-on to a local profile associated with a domain account, like how Windowsħ works: just enable biometrics in the Control Panel for a domain account? I *really* don't want to have to deploy Windows Hello for Business. Even before this policy was built and deployed, no other GPOs were managing account logon as related to biometrics,īut there's a notice at the top under Accounts > Sign-in options that "Some settings are hidden or managed by your organization" and Fingerprint, Password, and PIN were all disabled.Īfter this GPO was enabled, PIN is enabled, but even after setting one, I still can't get fingerprint to enable.
The device in question is a brand new Lenovo X1 Carbon (fully patched Windows Update and Lenovo drivers/firmware) with Fall Creators Update. Do not use the following security devices: TPM 1.2 (Disabled) Use a hardware security device (Enabled) Windows Components > Windows Hello for Business Allow users to log on using biometrics (Enabled) Allow domain users to log on using biometrics (Enabled) Turn on convenience PIN sign-in (Enabled) There is a central store of Fall Creators Update ADMX/ADML files in SYSVOL, and I have a group policy setup as follows:Ĭomputer Config > Policies > Administrative Templates I'm running an on-site domain (schema level 87) with two DCs (Server 2012 and Server 2016).
0 kommentar(er)
