It's about time!

[majicke.livejournal.com]

        *Developer walks on to the floor and targets acting manager*
   
"Hey! We've been trying to find ways of easing the call load. It's not good you're busy - It makes us look bad with upper management"

    *raises an eyebrow*

"We thought it'd be a good idea if this *insert admin-y type function* was done by the local admin instead of the helpdesk"

    *falls over in shock*
    *does several head-desks*
    *gives him a "ya-reckon" look*

*Acting manager grins - she's been busy doing the "we can't cope anymore" thing to someone who actually cares*

Comments

[the-s-guy.livejournal.com]

Say WHAT?

Now can we get a developer permanently assigned to us so that they can be constantly correctly the development team's screwups which have been CAUSING our massive amounts of phone calls for the past eight years?

[attackgypsy.livejournal.com]

*grabs chest in best Fred Sanford immitation*

I'M COMMIN TA JOIN YA, LIZIBETH!

[gilmoure.livejournal.com]

Heh, we just had the Windows team lead show up at our help desk staff meeting and give us a schedule of Windows patches and Office update roll outs. What a concept; give help desk a heads up!

We got slammed earlier this week when they released OfficeXP SP2 update and a Windows security patch on Monday. Would have been bad enough ("I have a window saying click OK to install security patch. What am I supposed to do?") but within 1/2 hour, calls were coming in about not being able to save in any Office app. Turns out patch caused problems, but only on machines that had HP scanner or printer drivers installed. Luckily, only a few of our 15,000 users use HP peripherals so help desk wasn't slammed too hard.