Tweet
We have 21 Alpha systems spread throughout our various plants. They run specific applications for these plants, and we have to check them three times each shift (6:00, 12:00, 6:00, yea we double it up at 6:00 each day) to make sure that specific jobs are active.
We have a program that scans the batch queues for us. All we have to do is start it up, give it the operator password and away it goes, logging into each Alpha in turn, displaying the batch queue in question, and moving on.
Can you see where this is going??
I get in today, tired because I didn't sleep well, and kick the scan off and head to the bathroom. I come back and find that it went through and failed to log into each system. Bad password.
Ok, I try again, and again, leave my desk, this time to load backup tapes.
Come back and find the exact same thing.
Once more, and this time, I hen-peck the password, so I KNOW it's right, and it goes through each of the 21 systems, and the message is basically that the account is locked out.
So, in two overly-quick attempts to do this, I managed to lock one of our accounts out of 21 systems. To tell the truth, I have to think that the day-shift operator tried and miss-typed the password at least once, and didn't try again (otherwise, the bad password count should have reset).
Luckily, it's only ONE of our accounts. The other, and more important is the one we use to create and modify accounts, including unlocking them. I had to log into each one in turn and re-enable the account on each system.
Tomorrow, I'm going to try and get more sleep....
Eric the Grey
We have a program that scans the batch queues for us. All we have to do is start it up, give it the operator password and away it goes, logging into each Alpha in turn, displaying the batch queue in question, and moving on.
Can you see where this is going??
I get in today, tired because I didn't sleep well, and kick the scan off and head to the bathroom. I come back and find that it went through and failed to log into each system. Bad password.
Ok, I try again, and again, leave my desk, this time to load backup tapes.
Come back and find the exact same thing.
Once more, and this time, I hen-peck the password, so I KNOW it's right, and it goes through each of the 21 systems, and the message is basically that the account is locked out.
So, in two overly-quick attempts to do this, I managed to lock one of our accounts out of 21 systems. To tell the truth, I have to think that the day-shift operator tried and miss-typed the password at least once, and didn't try again (otherwise, the bad password count should have reset).
Luckily, it's only ONE of our accounts. The other, and more important is the one we use to create and modify accounts, including unlocking them. I had to log into each one in turn and re-enable the account on each system.
Tomorrow, I'm going to try and get more sleep....
Eric the Grey