More Work Order Fail

[phrogg.livejournal.com]

toxico's entry reminded me of one particular work order i came across a few days ago. The particular details of this one are slightly fuzzy by now, but let's assume this fellow's name was Joe Snuffy.

WO# xxxxxx
Requestor: JOE SNUFFY
Summary: JOE SNUFFY
Contact #: JOE SNUFFY
Description: (care to take a stab? That's right...) JOE SNUFFY.

This nitwit entered his own name in every field. So not only did he give us absolutely no information on the issue (aside from the fact that he is, indeed, a moron), he also reminded me alot of Bob Dole giving a speech as i read through the ticket. "Bob Dole. Bob Dole, Bob Dole..."

Apparently, this isn't the first time he's done this, either.

I begged for permission to simply close this one out, putting my OWN name in caps for a resolution, but my boss recognized the name and dug up his number so that i could actually call and find out what his malfunction was. :(

A couple of simple ones.

[toxico.livejournal.com]

I was standing near the help desk folks in time to hear the breaking of wills when the following ticket came in:

"Help Desk ticketing system not working."


Yesterday, the following was submitted from the admin assistant for the most important people in the company, regarding one of their phones:

"It is staying all lit, goes straight to vm. We are unsure what to do to
dismantle this? Help?!? LOL"

We always suspected she wasn't hired for her professionalism...

Ah hazing, you never get old (or approved)

[toxico.livejournal.com]

We have a relatively new help desk guy who likes to leave his computer unlocked. Our boss (okay, really just my boss, but due to repeated date rape of our organizational hierarchy he could be this other guy's boss - no one knows) likes to go to his computer and send an email to the Network Ops team and the help desk stating that lunch is on him. This has happened a billionty several dozen a few times.

After today's occurrence, this went out to everyone from my boss:

We're getting these often enough from $helpdesktech's email that it's time we start enforcing it. I'll be at Chik-Fil-A at 2 PM (I'm serious). If you're not there, I'm disabling your account at 2:15 and creating an out of office reply in your Outlook stating that you've fallen in love with a flea infested Water Buffalo and are moving to the Serengeti to experience true love. See you at 2. I hope to see EVERYONE there.

All domain admins and helpdesk operators now have a new screensaver GPO timeout assigned. It will lock your screen after 3 minutes of inactivity. "Suggested" by $higher_up...brought about by $helpdesktech. Everyone make sure to stop by and give $helpdesktech a hearty "thank you" and metaphorical slap on the back of the head. For those of you who don't know, metaphorical means that you don't really slap him on the back of the head while on company property. I think a Chik-Fil-A sandwich to go with the free Chik-Fil-A sponsored ice cream is in order.

He then schedules a meeting for 2 PM at Chik-fil-a and sends the invite to everyone.


At about 2:15, after a few of us had returned from procuring free ice cream, we see $helpdesktech walking by with about a dozen chicken sandwiches and a shamed look on his face.

x-posted to my lj

Computers are supposed to make our lives easier!

[margaretc.livejournal.com]

So, who knew that VMware defaults to allowing 24 machines max? And instead of a nice helpful error like 'You have too many machines running on your vSwitch', you get a useless 'Resource Locked' type error. This no worky when you have 26 machines running on the system.
You can reconfigure the vswitch, but you have to reboot the vmware server to let it take effect.

And $boss said it was just me. Ha!