Question - I have Endpoint Encryption loaded on some of our netbooks and today I'm having issues with the pre-boot login. Some of my users are getting this error. Not all, but several are and we've never seen this before. Can anyone give me an idea on how to "enablbe" password entry again?
it's because they have put their password in wrong too many times (or someone else has). All you can do is wait for the timeout to expire, then put the correct password in.
I guess if you are in a pinch, you can do a challenge/response recovery on them? That will clear the timeout?
You don't mention which version of EEPC though so it's hard to advise further.
Safeboot - sorry about that we're running 5.2.41 - I was able to do a recovery and get logged in, but then the same issue occurs if I shut the netbook down and log back in.
what kind of recovery did you do though? Only logging in successfully or creating a new token for the user will reset the timer.
you could create a new token for the users in EEM and make sure the machine syncs? But really, a user password reset recovery is what most people would do.
Here is my issue - we created a universal user and password for the encryption. We run this for over a year without issue. It appears that sometime over this past weekend, someone attempted to login unsucessfully over and over and over. Thus locking the universal user and it's password. I think I'm running into an issue resetting the user's password, because we have remote users attempting to login as the universal user constantly because they aren't getting in.
yes, you'll end up in a loop - you'll reset the account, then someone else will break it again when they try to login - when you boot their machine using a recovery, this lockout will end up back in the db and will get sent back out to everyone.
sharing an account is a big no-no under every recognized security practice as you probably know. And, this is the kind of thing that occurs if you do it.
Not sure what you can do other than live through it I'm afraid - the whole system was not designed to consider that the same person might be logging on everwhere. I guess keep resetting the account to the same password, maybe make a script which resets it every 30 seconds automatically perhaps?
you could turn off your database server for a while? That would stop machines getting re-infected, but you'd have to do a challenge/response password recovery on anyone having the issue.
Once everyone is back online, turn the server back on and watch for the account getting locked again.