Windows 10: i deployed windows hello for my org , today i found that one of my user is able to use...

I deployed windows hello for my org , today i found that one of my user is able to use windows hello credential for RDP. but others cant. i tried my self still no luckhow to enable and configure it ?why its only working for him ?both user are domain admins

:)

 

Lenovo Ideapad 110 with Win 10; Not able to switch the user

Lenovo Ideapad 110 with Win 10; Not able to switch the user..

Boots up with earlier configured user name, prompts for his password. Doesn't allow to switch to a new user, or creation of one.

Use case: Laptop was given to an employee, who left the org. Now it need to be re-purposed with a different user. Any suggestions?

 

Current active users that are friends

The other reason I suggested this is that users can add characters to their username that are not alphanumeric (e.g. user*). This confuses things somewhat when looking at the list.

 

Deployed Windows hello for Business with cloud trust, Forti does not recognize the affected users's login

Hello guys!

I hope you're all doing great!

So, I have deployed Windows Hello for Business using Cloud Trust Authentication on a client's environment (I had previously Hybrid domain joined their users and devices and subsequently deployed co-management as they have config manager). We went through all the steps as per described by MS Docs and the deployment worked as expected: One would login to the device and then never had any other form of authentication requested again (Upon accessing to MS 365 apps).

So far so good, but little did I know the client has Forti Guard for proxied addresses. After some investigation on their side, they concluded that Forti guard cannot read the security event for Logon 4624, so when the user tries to access anything that isn't related to MS (They whitelisted all MS Services IP's) they would get a certificate error as Forti Guard does not have any registered user for that logon (The one performed through Windows hello for business).

Is there any chance that since the authentication is happening on the Cloud, on prem services is not seeing it? I reckon that having AD Connect synchronize both domains (cloud + on prem) should prevent this from happening but maybe there's something we are not seeing here.

Thank you very much in advance!