Overheard at the Office #37

There was only one phone line to the office and Donald was first in line to answer incoming calls. When someone called in, he would transfer the call to the appropriate party.  If said party was at their desk and picked up, all was good.  However, if they weren't, that person would come in the next morning and find a voicemail of Donald saying Hello over and over again because he didn't get the difference between someone picking up and voicemail picking up. 


Hello?        Hello?          Hello?        Hello?


Mitch saved one of these voicemails where the Hello's went on for at least 3 minutes, and then before hanging up you could hear Donald grumbling "Doesn't anybody work back there anymore?"

Overheard at the Office #36

User submits a ticket stating that he can't see emails for today in Outlook.  Previous days are fine however, as is the OWA page. User just so happens to be one of the owners of the client, no big deal right?


Mitch gets the ticket and updates it asking when he can look at the machines. This of course sends an email to the client which he will never see.  A few hours later I see this ticket, put 2 and 2 together and give client a call.  It turns out he hit the little arrow to collapse today, and hitting it again restored visibility of today's email.  "I guess I've got a trigger finger," laughed the client.

But how are you going to send someone an email that you know they'll never see?

Overheard at the Office #35

DOH!

ATM located in the building where I work.

Overheard in My Livingroom #2

A computer that I was asked to take a look at. Surprisingly, it was a software issue, not an overheating GPU.

Overheard at the Office #34

Coworker, reviewing the vulnerability scan's report: ...so we need to disable FTP, Telnet, and TCP on all these printers....
Me: WTF?  You can't disable TCP!
Coworker: Yeah, all these are TCP vulnerabilities, we need to disable TCP.
Me: Well, I guess that will mitigate all risk for the printer....

Overheard at the Office #33

Coworker on the phone with a client:

Yeah, but that doesn't always work. Because of the way memory works these days, what with capacitors and such, it doesn't always erase it all when you reboot. Sometimes you have to shut it down for a minute

Me to a different coworker on Lync:

Are you hearing this?

Overheard at the office #32

This one comes courtesy of my current job, and thankfully I was just a fly on the wall as it went down.

User forgets password and calls I.T.
User is able to log in once.
User locks account again.
User calls IT again.
User gets password reset.
User is unable to come up with a new password, calls IT for help.
IT refuses to make up a password for user.
User finally comes up with password, but Active Directory won't take it.
User is upset and sends manager to go talk to IT.
Manager talks to IT, discussion eventually leads to 3 members of IT staff getting involved in this dilemma.
It is eventually noticed that users's chosen password contains the user's entire first name, hence the problem.
Third member of IT suggests changing one of the letters in the password to a symbol that looks similar to one of the letters in users name, DC accepts this password.
User's manager is rushed out the door.
IT all goes out for a smoke break, even the ones who don't smoke.