Warning: Angry Language Inside

Thursday, September 9th, 2010 | IT

It’s been one of those days.  We start off by four people calling in sick.  Well, two calling in, and the third, after he already knew we were down two people, gives a shitty lameass excuse for why he has to leave early.  The fourth looked legitimately sick, so that’s fine.  The two who called in?  Biggest waste of IT space ever.  Four people down in my department makes my day turn to shit, tons of calls, tons of e-mail, and of the few people who are here, only two of them, myself included, are worth a damn.

So my last call, I have to give a hearty “Fuck you” to the local tech at the hospital.  Fuck you, Tech-man.  Fuck you in your stupid old man face.  I swear to all that is holy that if you ever again tell a user that my instructions won’t fix their issue, and that you’d prefer to waste 4 hours of their day by running scandisk and defrag, that I’ll drive up to your hospital and punch you in your retarded mouth, you fucking moron.

We have a known issue caused by some group policy issues, and a new fix was put out last week, but the catch is that the PC needs to be rebooted to receive the fix.  The issue causes some TCP ports to hang, which then causes all kinds of crap to go haywire including slowness on the network, and eventually causing the network connection to fail completely.  The user was trying to install Adobe Reader via our network install, and it’s showing that it’s going to take 2+ hours to install, when it’s a 5 minute install.  I tell him to reboot, he says he’ll do it, we hang up.  He calls back two minutes later and says, “Oh, the local tech said that rebooting won’t fix it and he wants to run some cleaning applications.”  So basically, the local guy tells the user that I don’t know what I’m talking about, and makes me look like an ass, when it’s a well known and documented issue.

So screw you local guy.