Wow, people sure do get bitchy when you don't just arbitrarily give them a password simply because they asked.
"We're trying to install some security cameras, and the port over which the feed is broadcast is being blocked by this application. What's the password to unlock the interface so I can edit the policies?"
"How do you know it's that application doing it?"
"It's in the log file."
"Okay, fair enough. Can you send that to me?"
"What?! Can't you just give it to me?"
"Only after you show me the log file."
"This is ridiculous grumble bitch mumble inefficient blah."
~45 seconds of verbal diarrhea later~
"Yup, there it is! Here's the password."
See, was that so HARD?! Douche.
"We're trying to install some security cameras, and the port over which the feed is broadcast is being blocked by this application. What's the password to unlock the interface so I can edit the policies?"
"How do you know it's that application doing it?"
"It's in the log file."
"Okay, fair enough. Can you send that to me?"
"What?! Can't you just give it to me?"
"Only after you show me the log file."
"This is ridiculous grumble bitch mumble inefficient blah."
~45 seconds of verbal diarrhea later~
"Yup, there it is! Here's the password."
See, was that so HARD?! Douche.
no subject
Date: 2008-09-11 04:50 pm (UTC)no subject
Date: 2008-09-11 04:54 pm (UTC)If you're annoyed by copying and pasting the text already on the screen into an email and hitting Send, your priorities need adjusting.
Edited for spelling.
no subject
Date: 2008-09-11 05:06 pm (UTC)Either they're not supposed to have the passwords and someone at your location is supposed to make the changes no matter how much the people at that location complain about it, or they're allowed to manage things themselves, in which case they should have the access they need.
I like the policy I work under. When customers call in with a problem, we can answer questions, and get log files/configuration information so that we can replicate the problem and come up with a solution, but we're never supposed to go in and make changes on their systems ourselves. That way we can never get blamed for breaking anything.
no subject
Date: 2008-09-11 05:09 pm (UTC)no subject
Date: 2008-09-11 05:41 pm (UTC)And I never said there was something wrong with a hands-on approach, especially if that's what you're paid to do. --Just that the particular policy you described doesn't make sense to me.
no subject
Date: 2008-09-11 04:58 pm (UTC)We get people calling on behalf of other people, and they throw OMG hissy-fits when we can't change the password on their say-so for this other person. Reason being? HIPAA (Health Information Privacy Act). This policy has been in place a couple years, and people still try to push it. If we cannot speak to (and verify) that the person indeed needs their password reset, we can get in metric fucktons of trouble.
That sounds rough... :( And some people don't seem to understand policies which are in place for a valid reason.
no subject
Date: 2008-09-11 06:42 pm (UTC)"B-B-B-But he's in a meeeeeeeeeeeeeeeeting!"
that's why we're a 24-hour support line, bia.. now get him on the phone or STFU
no subject
Date: 2008-09-12 05:29 am (UTC)But one supervisor asking for, say their bosses password? there are exactly two people that can get away with that at my place- the admin assistants to the executive team, and the execs generally call it in themselves anyhow.
no subject
Date: 2008-09-11 05:15 pm (UTC)Read: We need photo ID. Preferably the one the agency issued you.
Don't like it? Tough.
no subject
Date: 2008-09-11 05:28 pm (UTC)no subject
Date: 2008-09-11 05:35 pm (UTC)no subject
Date: 2008-09-12 04:39 am (UTC)