Quote:
Originally Posted by Katsunami
LOL. Try this one.
"Hello, <helpdesk>. Good afternoon."
- "Hi, I have a <computer>. I've lost the password to my e-mail."
"I'm sorry to hear that sir. You'll have to call the service that provides your e-mail, and have them reset it."
- "But... but... It's *YOUR* computer! Can't you look that up for me?"
"Yes sir, it's one of our computers, but it's *YOUR* e-mail, so we can't find out your password."
- "Why not?!"
"Because the fact that *WE* can't know the password to *YOUR* e-mail is the entire point of a password, sir."
- "DON'T YOU BE TALKING SMART TO ME YOU HEAR!"
*Sigh... Long day ahead....*
Been there, done that. I'll NEVER work in support again. Ever.
|
I went through that supporting both Windows and Linux users. In both cases, the stack answer was "I can
reset your password so you have to create a new one. I
can't tell you what it currently
is. It's stored in an encrypted format for security reasons."
My favorites were the folks in the Win3.1/9X days complaining that they needed more memory. The problem was that Windows back then had the concept of "resources", that were allocated by applications when they ran. The amount of resources was fixed (two 64K heaps in Win 3.X, one 128K heap in Win9.X,) no matter how much memory was installed. Various applications would allocate resources but not properly free them when they exited, and when resources were exhausted, all you could do was reboot. (Microsoft Excel was a worst offender about not properly freeing resources.)
Getting across the distinction between memory and resources was a challenge. I was
delighted to switch to Win2K at home when it was available and those constraints no longer applied.
______
Dennis