C
Christian Urich
We are in the process of transitioning our laptop deployment from Local AD to Azure AD using Autopilot. We've noticed a behavior in Windows Hello that has changed with this transition: Upon logging in with Windows Hello, the system no longer seems to have cached credentials and you cannot login seamlessly to other systems like file server, VPN and WIFI (etc.). If you use your account name and password, all works fine. While using our Local AD, we did not have this issue with Windows Hello; it had cached credentials either way. Is there a way to get Windows Hello to work with cached credentials
Continue reading...
Continue reading...