Guest User!

You are not Sophos Staff.

This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

1 fingerswipe locked out for more then 4 hours......

We are using Safeguard easy 5.50.1.17 with Lenovo T510's. We have the fingerprint reader working for POA. I had a user yesterday boot their laptop for the day, swipe their finger then had multipal flashes on the screen that said "Log-on failed" and then had to wait for the next attempt to log-in for more then 4 hours...I am not sure exactly how long because they were booting their machine for the fist time in the afternoon and the lock cleared over night while I was not here. I have never seen this behavior before and I was wondering if anyone else had? and if so had any thoughts on why it would happen?

Thanks in advance!

:5202


This thread was automatically locked due to age.
Parents
  • RL thanks for your help! and thanks for pointing me towards that link. I am currently contacting our Account Manager to see if the T 510 was left off for some reason.

    I did finally get my person so they have no more problems logging in. What I ended up doing was clearing the fingerprint data out of BIOS, logging into POA with their password, clearing all fingerprint data out of the Lenovo software, re-enrolling their fingerprints, then logging off Windows, then logging back into Windows with the fingerprint data and then rebooting and using the fingerprint data to get thru POA.

    My person stated they had never been able to just swipe their finger once and get a good read that would log them in. So possibly in this case it is just some really bad fingerprint data, but still seems odd that it would register multiple log in denied's.

    :5229
Reply
  • RL thanks for your help! and thanks for pointing me towards that link. I am currently contacting our Account Manager to see if the T 510 was left off for some reason.

    I did finally get my person so they have no more problems logging in. What I ended up doing was clearing the fingerprint data out of BIOS, logging into POA with their password, clearing all fingerprint data out of the Lenovo software, re-enrolling their fingerprints, then logging off Windows, then logging back into Windows with the fingerprint data and then rebooting and using the fingerprint data to get thru POA.

    My person stated they had never been able to just swipe their finger once and get a good read that would log them in. So possibly in this case it is just some really bad fingerprint data, but still seems odd that it would register multiple log in denied's.

    :5229
Children
No Data