Windows 10: Unable to use Fingerprint after changing Domain username

I'm the network administrator on our company domain, and I've recently had to change my domain username due to a naming convention change.


Windows 10 on my laptop (ver 1903 build 18362.356) now no longer lets me login using the fingerprints previously set up in Windows Hello, and reports that "Your password was chnged on a different device. You must sign in to this device once with your new password, and then you can sign in with Windows Hello."


My password hasn't changed at all, so this error message is inaccurate. Once logged in using username/password, I can unlock the computer using biometrics, but it still doesn't let me login using them.


Within Sign-In Options, Windows Hello PIN says "This option is currently unavailable - click to learn more" If I click more it tells me "Sorry - this PIN isn't working for your organisation's resources. Tap or click here to fix it". This leads me to a screen to set up a PIN (which had already been set up before my login name changed). When I proceed, I get this:




True to form, Microsoft don't list the error code on their error code page (well done again Microsoft), so this error page is meaningless and unhelpful.

The necessary GPOs are enabled to allow use of biometrics within the domain, and Hello was working until my username change. Does anyone have any ideas? I've tried all of the suggestions I can find online, but none of them have worked so far.

Thanks in advance.




***Modified title from: Windows Hello probems***

:)

 

domain\username

I signed up for Phone Insider.

When I try "Find a program" it asks for domain\username and password.

What is my domain\username and password?

 

Unable to setup fingerprint option in WIndows 10 domain Joined computer

Hello Shushanth,

Since you're connected to a domain, there's a possibility that the account you're using to login to the server does not have administrative rights. The program used by the Microsoft Modern Keyboard with Fingerprint requires administrative privilege to function,
we recommend contacting the local IT in your premise for further assistance.

You may also check the links below for additional troubleshooting:

• Troubleshoot problems with Surface Keyboard, Surface Ergonomic Keyboard, and Microsoft
  Modern Keyboard with Fingerprint ID
• Troubleshooting Microsoft Modern Keyboard with Fingerprint ID

Let us know if you have other concern.

Regards.

 

Raising the windows domain and forest issues?


hi,

I run a domain that was all 2003 r2 servers. I recently upgraded all my domain controllers to windows 2012 r2.
That went off without any problems.. Our trust relationships had no issues also.

My first step was to raise the Domain and Forest levels past 2003 to 2008. This went off without a hitch.
These are the features for raising the levels to 2008:

• Features and benefits include all default Active Directory features, all features from the Windows Server 2003 domain functional level, plus:
• Read-Only Domain Controllers – Allows implementation of domain controllers that only host read-only copy of NTDS database.
• Advanced Encryption Services – (AES 128 and 256) support for the Kerberos protocol.
• Distributed File System Replication (DFSR) – Allows SYSVOL to replicate using DFSR instead of older File Replication Service (FRS). It provides more robust and detailed replication of SYSVOL contents.

Forest Level Windows Server 2008

• Features and benefits include all of the features that are available at the Windows Server 2003 forest functional level, but no additional features. All domains that are subsequently added to the forest will operate at the Windows Server 2008 domain functional level by default.

My next step is to raise the domain and forest to 2008 r2, then 2012, and finally 2012 r2. I have been trying to find out exactly what I could expect from raising the Domain and Forest for each step.

The step involving 2008 r2 seems relatively a non issue. But getting the couple of new features seem very nice

Domain Level Windows Server 2008 R2

• All default Active Directory features, all features from the Windows Server 2008 domain functional level, plus 2 new features

Forest Level Windows Server 2008 R2

• All of the features that are available at the Windows Server 2003 forest functional level, plus the following features:

• Active Directory Recycle Bin, which provides the ability to restore deleted objects in their entirety while AD DS is running. <== New Feature very cool
• All domains subsequently added to the forest will operate at the Windows Server 2008 R2 domain functional level by default.

Here is my big concerns for the next raising of domain and forest to 2012.

Forest Level Windows Server 2012:

• All of the features that are available at the Windows Server 2008 R2 forest functional level, but no additional features.
• All domains subsequently added to the forest will operate at the Windows Server 2012 domain functional level by default.

Domain Level Windows Server 2012 R2: <=====Need to investigate more and why this post

• DC-side protections for Protected Users. Protected Users authenticating to a Windows Server 2012 R2 domain can no longer:

• Authenticate with NTLM authentication <==============(what issues may arise)
• Use DES or RC4 cipher suites in Kerberos pre-authentication
• Be delegated with unconstrained or constrained delegation
• Renew user tickets (TGTs) beyond the initial 4-hour lifetime

Will this affect my exchange anywhere users with remote access authenticating either clear of NTLM???
and what would/may not to work properly day 1 when I raise the domain and forest to 2012. I cant really find anyone that can answer a straight question.

Has anyone gone through this? what problems did you have, if any , if a lot???

Any thoughts and suggestions will be much appreciated??

thanks


- - - Updated - - -

One more point... I am not sure if I posted this to the correct forum.. So if I was wrong and it should be in a different one..
PLEASE LET ME KNOW