“Credentials could not be verified,” Error!
This can be a frustrating error to get for users, for those of though that are technical minded this is an easy to understand situation. The reason for this error is that Active Client does not have the user’s credential cache loaded. A lot of the time you’ll get calls for this because your user is impatient. Windows finishes starting up and therefore the user thinks the computer is ready to be logged into. However Active Client has not finished loading, therefore your user should remove their CAC from the reader and wait a few more seconds (I typically make them wait 1 minute) before trying to logon again. Nine times out of ten this will resolve the issue, especially if they are on the same network as the authentication server.
There will be times however where a user is on the VPN and during their VPN session their account gets disabled for whatever reason. Now there session will continue until they log off or it times out. Once the session has ended and the user reboots the machine they will be locked out and their credentials will not be able to be verified. The only way around this is to have the user return to the network and login there so that their credentials can be re-cached to the machine.
Recent Comments