I'm trying to figure something out - maybe someone understands this better and can explain?
I have the full Endpoint client installed, including FDE with preboot auth, and VPN.
I currently have the Endpoint policy password sync set as "bi-directional".
I have two scenarios. The first one sets the scene. The second one is my actual problem now.
Scenario 1 - User wants to change their password.
- On the Preboot screen - click "Change Password"
- Change the password. Old password, New password, etc.
- Boot in to Windows. Ctrl+alt+del. You still need your OLD password. It doesn't sync.
Presumably because it's a domain user, and while I am sat at home the laptop can't talk to the Domain Controller to do the password update. Kinda makes sense.
So....
- VPN client - enable Secure Domain Logon.
- Reboot.
- Try again - Preboot password change....
This time when it boots into Windows the VPN login pops up first. Perfect! 😍 Log in to VPN, then it carries on into Windows (SSO) and the users' domain password is also updated in the background. Perfect! And I prove this by locking or logging out of Windows, then it needs the new password to get back in. Great. All good.
Fast forward to the next scenario...
Scenario 2: User forgets their password.
This time we need to use Remote Help, challenge/response to issue a password reset. This bit works fine until it boots into Windows.
Now in Windows, Secure Domain Logon does NOT trigger. It just sits at the Windows Ctrl+alt+del login screen wanting the OLD (forgotten) password. So we still can't log in to Windows.
Is there a reason why SDL works for a normal password change, but not for a challenge/response password change?
Am I just missing something really obvious? (probably!).
How do other people deal with challenge/response password changes for updating domain computers while they are off the LAN? How do I log in to Windows in this offline scenario if password sync doesn't update the Windows password and I've forgotten my old password?