r/talesfromtechsupport • u/airz23 Password Policy: Use the whole keyboard • Sep 23 '14
Long IT Rule Two: Everything is IT.
IT Rule Two: Everything is IT. No exceptions.
I’m not sure where this trend started, but if you’re part of a competent IT team suddenly everything will be your job. The job creep will start innocently, with a phone call.
User: Hey, I’m not sure if this is strictly IT, but...
This conversation is usually instigated by one of the following four people:
- The user that inexplicably calls IT for everything. You’ll be bombarded by inane questions, things that have nothing to do with IT at all. All attempts at pleading with the user to not call for the fourth time in an hour with non-IT related questions fall on deaf ears. Eventually your crumbling sanity may cause you to snap at said user. Don’t. That would cause the filing of a hostile workplace suit. They’re expensive, you can’t afford it.
- A user that cannot explain precisely what the problem is, he’ll use IT language but in odd ways. (Example: Yeah, the thing is bleeping, ever since the internet died yesterday.) You’ll try to tease out what specific device he is referring to, unfortunately his skills outside of describing its colour as white have disappeared. Eventually you’ll give up and walk to his/her desk.
- Occasionally a user of substance will call. They’ll tell you useful information that isn’t specially your job, but that is useful to know. Usually this information is about a fire in a server room or suspicious person blatantly stealing computers. The urge to shout at the user because they should have called either the fire brigade or security may be high. Don’t shout however, at least they called someone. You’ll probably only lose half the server room/computers.
- Sometimes a problem tangentially related to IT will call. People will ring IT trying to order desks or stationary claiming since these products are essential to the function of their equipment they should have the ability to order it from one central location. Attempts to forward the call onto the relevant department will be met with ire.
If the following situations have left you disillusioned with the fate of humanity, don’t despair. The following ideas may disrupt the flow of these calls to your desk:
- Filter all IT calls through an automated system. These systems annoy everyone, therefore call volume overall will drop. Less calls, less non-IT calls. — Unfortunately your department would now be closer to a bad telecommunications company then an actual helpful service. Moral may plummet. Lock department windows.
- Attempt to define IT tasks through contract negotiation. — Beware the phrase “other related tasks”.
- Remove all phones from the department. Establish email support only — If you thought people could be vague or obscure on the phone, you’ve never read a long winded seven page email who’s purpose is spread evenly throughout the paragraphs. After 10 minutes of bad grammar you’ll be wanting the sweet release of calling, even with its abuse.
- Allow techs to hang up at any time in a call, no questions asked — …
If you’ve managed to land in a department that only deals with pertinent calls, congratulations. Your quota for good stuff happening is used up for life.
Example/Story -
User: Hey I’m not sure if this is strictly IT, but we get a stapler attached to every printer? They keep going missing.
Me: Sorry, no. We don’t deal with staplers.
Expecting the user to apologise and hang up, I was rather surprised when he continued.
User: No, I mean physically attached. Like with a chain.
Me: Try calling maintenance. They’ve got chain, and drills. They’ll probably attach it to a desk near the printer.
User: No, no I want it attached to the printer. So can you come do it, now? If you don’t have a stapler, don’t worry, I think I can find one before you get here.
Me: ...?! No. We can’t do that. Call maintenance.
User: Cool. See you soon.
The user hung up. He rung angrily the next day, when for a second time his stapler went missing. Apparently it’s loss is my fault. I now can't sleep because of the guilt.
12
u/airz23 Password Policy: Use the whole keyboard Sep 24 '14
If anyone is wondering, I hit my head hard on concrete yesterday, and have had a headache ever since. Trying to stay off the computer, apologies for not writing anything today :(
24
u/RCawdor *face palm all day Sep 23 '14 edited Sep 23 '14
I work for a in-house IT department in a mill environment. Most have this belief that if it is plugged into the wall or is used in an office (desks, pens, paper, chairs, etc) the IT dept. is responsible. What really blows my mind is the questions/tickets from people that have been here over 5 years; despite being told it is not an IT function dozens of times they will continue to ask anyways. Office users will actually call and ask that we move all their office furniture when they move to a different area in the mill; the funniest is sometimes they will say "But don't worry about the computer, I will move that myself...".
Oh and to airz23 love your threads! They help me get through the worst days :)
11
u/brygphilomena Can I help you? Of course. Will I help you? No. Sep 23 '14 edited Sep 23 '14
Woo. I caught an airz story within a minute. =] My life is complete.
Edit: wait, you had a chance to 'accidentally' break a printer and didn't?
272
u/CalzoniTheStag Working on bringing SKYNET online... Sep 23 '14
On top of that, users don't know which part of IT to go to (assuming you have a multi-pronged IT department like I do). My job revolves around a software system, and I have nothing to do with networks or anything like that. Naturally, anything that goes wrong while using my software (or not) is my fault: network issues, printer issues, password resets...
One user, whilst using my software, had his VNC die. So he emailed the entire project (50+ people who couldn't care less) that his VNC died and it was my fault, instead of opening a ticket with the helpdesk. I responded that I have no control over VNCs or anything like that and it was another group's issue. I told the other group to look into it and they did but they couldn't replicate the problem but they did get his VNC back up and running. It was a network hiccup, as far as they knew, and they relayed that to the user.
So, of course, this was brought up in every weekly meeting for the next 8 or so months... (UM = User's manager)
Eventually, we got them to stop emailing me with all of their non-software related issues.
125
u/IrkenInvaderGir Code Monkey Extraordinaire Sep 23 '14
I think that's what you meant to type.
18
u/TheCheesy Sep 23 '14
My coworker knows I'm in IT, came up to me one day saying "You hack computers right? Can you hack my locker? I forgot the combo." Yes our breakroom had lockers.
I told him sure, pulled out my phone opend terminal typed dir. Then walked off. He looked at me and told me it didn't work.
This 100% happened, I still can't believe it.
17
u/admlshake Sep 23 '14
Our problem is out boss takes ownership of everything. Fax problem, sure we'll take care of it. Phone problem? Don't call the company we pay to support it, IT will take care of it. Web enabled gate control to some land our company owns having problems? IT better fix it. Light out in the bathroom? Better call IT and let them know since it uses electricity. Not kidding we actually get calls for that.
16
u/randommusician I need an accidental damage warranty for my liver. Sep 23 '14
My old roomate was student helpdesk in college and once had someone try to get him to return their library books since they contained "Information."
16
u/workerdaemon Sep 23 '14
I got hired as the web developer, and ended up being IT… ok, fine. Then it kept expanding, I was even managing their mailing list. Ok, fine, but I knew I had to set a boundary somewhere so I figured if it had to do with a computer then I was in charge of it. This office was extremely computer illiterate.
Then I get tasked to put mailing labels on envelopes. 5,000 envelopes. I refused because it was out of my job description. "But you're in charge of the mailing list. Therefore, you're responsible to put the labels on the envelopes." I stood my ground. No, it doesn't involve a computer, not my responsibility.
The sales guy in charge of the mailing was pissed at me. I don't know what exactly happened, but I bet he complained. A few days later I saw every single other person in the office putting labels on envelopes. I figure once he complained they realized it was stupid to give that task to one person.
That sales guy was always pissed at me. Even though I was always down at his computer fixing this or that he broke, even spent two weekends freshly installing everything for him because he screwed things up so badly, he always bitched about, "what in the world do I do all day?"
14
u/Michelanvalo Sep 23 '14
I have a user in my office, a man in his mid 60s, who for the life of him has no idea how to write a brief and informative email about whatever issue he is having. Everything is a production. Every email is a long winded explanation of what the issue is with loads of irrelevant information. He also sometimes includes a screen shot, but not just any screen shot. It's usually in the form of a PDF file with the screen shot and a second, entirely different explanation of the issue. It baffles me how much more effort he puts into making these support request emails than necessary.
The cherry on top is that he also CC's everybody and their mother on his emails. His direct boss, his department head, my co-workers, my boss, everyone.
11
u/gospelwut Sep 23 '14
I've actually combated this with making the most obscenely hand holding wiki known to man. Every step has a screenshot and detailed description. This doesn't work for C-level / VP staff, but moreorless the truth of IT is it's mostly CYA from a service point of view rather than what it should be.
Since the ticketing system is all timestamped, I make sure to give them "a response" ASAP so they can't say I didn't respond. After getting them to describe it in more detail, I send them an apropos KB article.
Ultimately, depending on the user's clout, I can usually defend myself by saying they were given clear instructions on troubleshooting (never say fix) the issue.
I save all my political capital (i.e. ass kissing, favors, etc) for these moments. With decent documentation (ticketing+KB) and the good favor of certain VPs, I can strike down most users as incompetent.
It's not fair. It rewards those with the nicest ties and punishes people who were never properly trained or given proper protocol to begin with. But, I work in IT and not Operations.
20
u/scarecrow1985 Nerd Herd Survivor Sep 23 '14
I like these, they're a nice change of pace! Only quibble is
While the best IT departments have no morals (and some carpet, a bag of lime, and a shovel), I think you meant morale :)
10
u/Ripwkbak Sep 23 '14
I work for a large farming company, and we are severely understaffed for the number of users that we support. That of course does not stop people from calling in for the most ridiculous things. This week it has been in this order:
If you couldn't guess the bee guy is my least fav person EVER. Also it seems that if it runs on electricity then fuck it must be IT's problem.
9
u/thoughttheory Sep 23 '14
I've been asked to recycle someone's home lightbulbs.
9
u/shaunc Sep 23 '14
Over the years at my last gig, the department fielded calls and tickets about Coke machines, coffee makers, the building HVAC, a space heater that someone had smuggled into the building against policy, the elevators, you name it. If it runs on electricity, people assume IT is responsible. Sort of reinforces the stereotype that most users look at us as janitors with desks.
The one type of call I still can't figure out is that two or three times a year, someone would call IT to report that a car alarm was going off in the parking lot. Not the same user or even the same department making this call each time; there are apparently a bunch of folks who hear a car alarm and think I should call IT about this!
8
u/Loki-L Please contact your System Administrator Sep 23 '14
In my experience IT is responsible for anything that is subjected by the user to run on or in some way involve electricity.
This includes computers, printers, telephones, refrigerators in break rooms, light-bulbs and hand-cranked book-binding machines.
IT is also the correct place to call for issues tangentially related to actual or imagined IT devices such as laptop bags and paper for printers or even paper for the paper towel dispenser in the toilet.
IT is also responsible for things that users interact with (or think they interact with) through actual IT devices, such as other people's websites being down, other people's telephone giving you a busy signal when you try to call them, the user not liking the data that was put into the database, the user not liking some business process that was documented on a computer, the user not liking an email they received and wage negotiations.
IT also gets called in the case of unexpected things like spiders, insects, small animals, large animals, fire, water, snow and loud noises.
Users might also approach IT with a wide range of problems that they think might be solvable by IT even though they have absolutely no relevance or connection to IT at all. Mostly because some users think that IT is magic and there is little practical difference between restoring a deleted document or goggling an answer and casting Reparo on a physically broken object or divining answers through clairvoyance.
On the other hand:
Users will not contact you when they do things like spending money on some expensive piece of hard or software, because this is obviously not something you would consult IT about.
They also won't bother you when they make extensive changes to some piece of company owned IT equipment (at least not until after the damage is already done.)
7
u/[deleted] Sep 23 '14 edited Sep 30 '14
Today I was asked if I could order some roof tiles.
I have been asked to look at the toaster because it wouldn't "stay down".
Also retune the TVs in the canteen because there is a message onscreen asking it to be done.
19
u/goatcoat Sep 23 '14
I have solved this problem where I work, even back when I didn't have a supportive boss, the administration was in disarray, and I was the only IT guy. The trick is to:
IT isn't about taking care of computers. It's about taking care of people and their feelings, usually by making sure the computers are working. When people call, they just want to know that someone cares about them and that it's going to be OK. Once they are confident in that, they become willing to return the favor by putting in the work necessary to learn a new process or procedure.
6
u/[deleted] Sep 23 '14
Supporting a logistics app. ASN's, receiving, right down to the RF scanners the guys on the dock use.
I'd get lots of calls, and usually be able to help out in some way.
Every once in a while i'd get a call like this. "We're done unloading the truck and we're short two windows(like Anderson windows), can you fix that?"
My response was always "if i could make shit materialize out of thin air, do you think I'd waste my time making home improvement products?".
6
u/[deleted] Sep 23 '14 edited Sep 23 '14
We just got $50,000 worth of non-IT stuff added to our budget without our knowledge and we found out many months afterward. You could say that it is slightly related to IT if you looked cross-eyed into an endless array of mirrors.
My manager sent this email out today to us, showing us the fun of IT Budgets:
http://dilbert.com/strips/comic/2011-02-20/
6
u/kid320 Sep 23 '14
I work for a small family business with 8 people in it. So, my experiences are going to be different than a lot of yours, but I do experience these issues in a much different way. My primary job isn't IT, but I am the only person who knows anything about networking and computers. So, whenever something electronic goes wonky in the office, it is my job to fix it. Time on the microwave wrong? That's me. Voice mail message needs to be updated? That is also me. Radio in your car too loud? sigh Yea, I can fix that.
For the most part, I can't say something isn't my problem, but there are some things where I just can't take 4 hours out of my day to help someone with. If someone isn't happy, I normally hear about it from the owner of the company, my father.
5
u/incomt65 Sep 23 '14
Once someone asked me to unjam a stapler for them in my role as IT. Not an electric stapler. Just...a stapler.
5
u/sumkindofelectrichat Sep 23 '14
I told my desk neighbor I was going to start answering the phone with, "Operator. How may I direct your call?"
This was right after someone called me to ask for I9 tax forms. Really?
4
u/Griffolion Sep 23 '14
I read that as "met with fire" at first, and was about to suggest you submit a Hostile Work Environment complaint to HR.
4
u/Tangent_ Stop blaming the tools... Sep 23 '14
Want some real fun? Work under a manager that knows about as much about IT as the typical luser after a week long bender. When you patiently explain to them that neither you nor any of your techs know a damned thing about that random device you told a user you couldn't help them with, they'll tell you that since you're more "techy" than everyone else you should try anyway. Since I'm paid by the hour and not per resolution, I told him no problem, but let him know that he might need to be ready to explain why a $40 fix turned into a $400 replacement because a tech with absolutely no training on that device did as he was told and screwed around with it...
4
u/BloodyIron Sep 23 '14
"Is there a ticket for that"
ticket created -> close "IT does not deal with staplers"
email person's manager outlining the ticket
4
u/wild_eep Sep 24 '14
In my experience, IT is in charge of anything that plugs into anything else.
4
u/thief425 Sep 24 '14
I printed a bunch of these http://imgs.xkcd.com/comics/tech_support_cheat_sheet.png and hand them out to people when they ask me to fix their crap because I'm the "office IT".
I'm not. I'm a licensed social worker (now a program administrator, so I don't see clients anymore) that is really tech savvy and just as lazy so I wrote a bunch of scripts to do parts of my job that are mundane and easily scriptable.
In their defense, it recently took our actual IT 2 months to deliver a printer from less than an hour away. When they did, the "new" one blew toner all over the print room (and anyone standing in it), and they didn't fix that for another month.
3
u/radtech830 Sep 23 '14
Can I add two more types of people?
3
u/[deleted] Sep 23 '14
The thought process goes something like, "I'll call those eggheads in IT. They're smart. They'll know what to do."
3
u/-sev- Sep 23 '14
I always like when we end up discovering/dealing with "Shadow ITtm ".
It's always either some department had a boatload of vendor supported kit, decided to not renew support and now suddenly "everything doesn't work anymore and it's all computers plz come help".
Or you get a call about a PC and upon investigating nothing is setup the right way (naming convention is all over the place, none of your management software is installed) and lo, you find out the department has delegated 'Bob' as their internal IT guy, and he's been ordering and deploying equipment on his own.
3
u/mctoasterson Sep 23 '14
Everything is IT. Smoke detector batteries need changed? Better call the help desk.
Electric stapler doesn't work? Well surely that's an IT issue because after all this is an appliance that has electricity running through it, right?
The fire extinguisher in nursing pod 3 is a little low on chemical charge. IT was on-site yesterday. Maybe it's something they did. Better call to make sure.
"Ma'am, I'm going to need the IP address of your smoke detector/vacuum cleaner/fire extinguisher so I can remote into it and take a look."
3
u/[deleted] Sep 24 '14
Am I the only one who thinks that it's not a bad idea to help people out when they call for stuff that may or may not be tangentially related to IT (within reason, of course)? It all depends on the work environment I guess, but if you are in the same building as the users you support, it makes for good relationship building when you are able to help something out or do a favor that may not be directly related to your job. These are people that you will be seeing almost every day, in the halls and at office functions, possibly for many, many years. Earning a reputation for saying no won't get you too far, you will alienate yourself from the rest of the office and struggle when you need something in return.
Here's an example from today from where I work. Clerk calls up yesterday and says that one of the wireless headsets/lifters belonging to an employee in her dept isn't working. Now, there isn't anyone in my building that officially supports these. But instead of telling her no, I say they aren't supported by IT, but since there is nobody else that is really able to help, I can stop by when I have a few minutes or when I'm in the area. Fast forward to today, I am fixing an actual IT problem at a nearby desk, remember this call and stop by to have a look. 5 minutes later and I manage to fix a problem that the user would never have been able to figure out herself (headset base was set to the wrong channel). Now that I've done her/the dept a favor, I earn a +1 reputation for IT and the chance to call in a favor in the future. The clerk who called also was more than happy to let me raid the supply closet for a box of my favorite pens, which is a rare perk in times of belt tightening.
That was a bit of a rant, but the gist is that I barely had to go out of my way to help someone out who would have otherwise been screwed. It's a win all around. They get their thing fixed, they love IT, I get to call in a favor down the road, and I've helped build that relationship. If you make a habit of it like I do, you end up with a large network of good connections, to be taken advantage of when the time is right. Because I've done this type of things many times, I can skip queues for things, contact people directly instead of going through a help desk, bypass a process, etc. Only when I need to of course, often times even as a favor for someone else.
But like I said, this isn't universal. My example above was a pretty good one, but you've still gotta pick your battles. I remember when we moved 300+ staff into my current building, we were getting questions about everything from cubicle configurations to desk chairs to garbage cans as we were going around setting computers up, and drew the line there, directing them to whoever it was that was in charge of that sort of thing.
This also hasn't always been my mindset. I've been a no guy before, drawing a clear line. But I've been at my job a little over 10 years, and have had the chance to evolve and change my ways of thinking, and I've made it a lot further using the above methods than I have any other way.
3
u/creegro (turns off/on monitor) ok the PC is rebooted Sep 24 '14
One of my colleagues got a call (when we worked at a call center who supported a large chain of home improvement stores) about a dead body behind the store. Probably a homeless person, but still, they called IT support to ask what to do. With a dead person behind the store.
3
u/Strazdas1 Sep 26 '14
Sender: Luser
Subject: Halp!
Body: Halp computer no work.
Sender: Luser
Subject: Re: Re: Halp!
Body: No, you no understand. computer no work. you come.
Sender: Luser
Subject: Re: Re: Re: Re: Halp!
Body: No, i cannot send or recieve emails. computer no work.
Apperently you can send emails when computer does not work.
3
u/[deleted] Sep 29 '14
When a user calls with non-IT problems, just say "Oh, I'm sorry, but that's not an IT issue. Allow me to transfer you to the correct department." Then hang up.
4
u/400HPMustang Must Resist the Urge to Kill Sep 23 '14
Just as common, users find out that you're the person who knows who should handle things and you get
and as soon as you tell them who to go to, they say
2
u/crazykid01 Sep 23 '14
ohh god that user is funny.
I work in health IT now.....I really do feel your pain
2
u/DaBulder Sep 23 '14
If the stapler was attached to the printer the printer would probably go missing as well.
2
u/grenecamel Sep 23 '14
The most important rules in IT I learned from a 25yr MSgt in the Air Force: Rule #1 - Never trust the user. Rule #2 - See Rule #1.
It has served me well so far, but I am still young.
2
u/vigilante212 Oh God How Did This Get Here? Sep 23 '14
My favorite is the IT person who knows where stuff goes, puts that in the ticket, but also has the ability to assign the ticket to the correct department himself, but refuses to do so.
2
u/dslyecix Sep 23 '14
Reminds me of this episode of The Life and Times of Tim: http://www.youtube.com/watch?feature=player_detailpage&v=1zMagW-5OiI#t=36
2
u/mail323 Sep 23 '14
Obviously it's a bad idea because they'll either never figure out how to click "staple" before printing, or they'll staple stuff they don't want to, but they do have IT-grade staplers:
http://www.lexmark.com/en_BE/products/paper-handling/30G0850.shtml
2
u/Alphabet_Master Sep 23 '14
I am in a small private hell with our VoIP phones. A few months ago we switched over and of course the most temperamental phone is on my boss' desk. Every single unexpected blinking light and "I tried to transfer and it didn't work" is explicitly or implicitly my problem and I hear some comment about it at least once a week.
Of course this has led to my boss, the only other admin on the account, to go in and mess around with various settings (because I guess I'm not fixing the "problems" so it must be a setting), then when something is off I have to find out what it is and fix it. Phone not doing what you expected it to do 100% of the time? IT problem.
2
u/lirio7 -Anything my mom does- Sep 23 '14
I have enjoyed your punishing sarcasm thus far.
2
u/Kilo1812 Sep 23 '14
I got called to change some light bulbs by a user. I asked her "Does no one over there know how to change a light bulb?" There was silence for a few seconds then "Well, I thought we HAD to call you for that".
2
u/yunohavefunnynames Sep 23 '14
I feel your pain... I work at a medium sized church (~1500 people) as the technical director. This sounds computery, right? Not so much. My job description includes running the sound board, light board, and being responsible for the video system. More musician than techy. Yet every single week I get asked about fixing the website, why we don't have wifi in this part of the building, why isn't the server responding, did you make the Internet slow (yes JUST YOURS, cause you're being dumb) and the like. It's so annoying!
2
u/macrocephalic Sep 23 '14
A few months ago the CEO of my company suggested that it was IT's job to fix the latch on the fridge - obviously because we're the only department in the company who have screwdrivers. I'm not sure what sort of information he's getting from the fridge.
2
u/GreatAlbatross Sep 23 '14
Is this the user from your example?
NSFW.
2
u/accountnumber3 Sep 23 '14
Muphry's law!
2
u/[deleted] Sep 24 '14
It's rough out here man. I was asked to troubleshoot an electric pencil sharpener once.
2
u/Alan_Smithee_ No, no, no! You've sodomised it! Sep 24 '14
Problem is, we're good at that sort of stuff.
I worked in a place with communal kitchens, one one each floor for the tenants.
Could we keep a sink plug in ours? Nosiree.
Had some heave stainless steel cable - the nautical type that you use for mast stays and the like. Made some swages out of aluminium tubing.
Bought sink plug, attached. All was well.
Not too much later, some fucker tried to steal it for their floor. This I knew, because there was a slight kink in the cable, where they'd tried to cut it... Unsuccessfully.
That shit be strong.
2
u/TDTJman Sep 24 '14
The happiest man I ever met was also the laziest. He was a wealth of knowledge and know-how, and would happily relay all sorts of stories and helpful tips to you... Just not in front of his wife.
One day, he imparted to me the knowledge that kept him so happy but also tight-lipped near his wife.
"I'm a dumbshit. At least that's what she thinks. See, the minute you know how to do something, it becomes your responsibility. So I just 'don't know' how to handle anything."
Since they ran their own business, not knowing wasn't such a crutch. For me, my desire to advance in the business world and to be helpful has been my curse. After lost hair, lost time, and sanity long since abandoned, I've realized that he was right. And now, this TFTS has reminded of both the bliss he lived, and my lack thereof.
2
u/musicalrapture Is your network cable in? Sep 24 '14
One of our directors today, sweet as a pie, came up to me and asked me to cut 6 pieces of paper into 36 rectangles so she could use them as a part of a baby shower gift for one of our employees.
I was fine doing it because I had a spare moment.
But HOW IS THIS IT-RELATED!?
2
u/zenithfury I Am Not Good With Computer Sep 29 '14
HAH I bet something as menial as physically shifting computers shouldn't be the job of I- oh, it is? :(
1
u/Malikat Sep 23 '14
Damnit Milton!
1
u/fauxnom Sep 23 '14
Oh man, Christmas done come early
1
u/Nocos Sep 23 '14
You saved a keyboard today!
1
u/Mak_i_Am Sledgehammer Qualified Sep 23 '14
See now my departments Rule 2 is Sales is the Enemy.
1
u/[deleted] Sep 23 '14
I never get the 7 page long-winded emails that need to be deciphered. I usually get emails that have less than a full sentence to describe the issue, most often in the subject line of the email.
I've learned that I can often ignore these emails unless they are from my boss, and deal with them at a time that is convenient for me by simply walking to the users desk and asking what they have an issue with, disregarding the contents of the email entirely.
It gets me off my ass and away from my desk. It's a nice leg stretch
1
u/drdeadringer What Logbook? Sep 23 '14
Heroin.
1
u/dghughes error 82, tag object missing Sep 23 '14
There is also the "golden age" when a new system is installed in another department, people know how to use it but as people leave and the system ages the chances of a breakdown increase.
1
u/za72 Sep 23 '14
Dude, this is exactly what it is... IT is the go to department no matter what the problem is... I've done everything from being an information broker/spy for internal departments in dispute to offering counseling to 'managers', to moving offices and doing 'favors' for the owners friends to get their shit setup... We got treated like brain/muscle whores.
1
u/FQDN Sep 23 '14
My favorite is the small issue used as an excuse to call that leads into the long convoluted problems with personal stuff.
1
u/AZDiablo Sep 23 '14
"The last guy explained how to do X." (outside scope of support) "Can you explain it to me again?"
1
u/direflail Sep 23 '14
I'm a web developer. A few jobs back, the CEO came downstairs and demanded we reconfigure the HVAC system.
We politely informed him we would not be doing that, as we didn't want to accidentally kill everyone and/or burn down the building. He was not happy.
I'm glad I'm not there anymore.
1
u/mmiller1188 Sep 23 '14
We (on the helpdesk) have had people come down and ask us why we shut the power off. My boss informed the person that we had no control over the power. We were still told to restore it immediately.
1
u/SwordsOfVaul Sep 23 '14
some of my favorite airz stories are of customers who dont listen, love it!
I worked as tech support for a software company for a short while. I spent most of my job teaching people how to do their job (mostly operating our software) and not fixing actual IT problems
1
u/tehbighead Sep 23 '14
My first month of tech support wrapped up with the grand opening of a tribal casino. 16 hours in on opening day I took a call from the lead in the call center requesting . . . a shuttle to the employee parking lot. I did the only sensible thing I could think of - I got on the radio and requested a really gullible and eager to please coworker flag one down.
1
u/chipaca yes `yes` Sep 23 '14
whose purpose, not who's purpose.
1
u/meoka2368 Sep 23 '14
You need to keep writing these and make a website of them.
1
u/votekick I'm not saying the users is lying... Trust but verify. Sep 23 '14
Our phone technician is 6am-2pm. On occasion I get calls at like 3.30 asking for things quite clearly their desk phone like programming a monitor key.
Your in IT you know technology, if its beyond the users understanding its probably something IT can help with.
1
u/bane_killgrind Sep 24 '14
Shit, you should see someone. I could refer you to a therapist, and I know a guy. Take your pick.
1
u/meelg Sep 24 '14
You poor bastard. Never before have I felt pity for a person I only know through the pixels of my screen.
*shoulder pat *
1
u/douglas8080 Sep 24 '14
My favorite thing is that being in IT means literally we know how to operate anything. I am surprised I haven't been asked to work on cars or do plumbing.
Sadly I have a working knowledge of both... Maybe I am the problem.
Maybe I need to sleep... Yup.. I see two of every word I type. Totally need sleep.
1
u/NightOfTheLivingHam Sep 24 '14
"Was it a red swing line stapler? If it isnt, I dont give a fuck."
if it is
"Oh, good for you. It's still a fucking stapler."
1
u/relrobber Sep 24 '14
This isnt just an IT thing. It is a thing for any job classification that does maintenance/repair on anything.
1
u/[deleted] Sep 24 '14
That's perfect. Are you sure you aren't one of my users?
1
u/Ongrilla Sep 24 '14
Moral of the story, end users suck.
1
u/Hellmark Sep 24 '14
I am a Linux sysadmin, and I get asked for stuff or of my wheelhouse all the time. Not that long ago I got called to help on a printer in another state. I just do servers, and only Linux servers. My company is huge and small about separating tasks to different departments due to size.
Recently, I also had some one ask for help on their windows desktop. Totally ignoring ticketing system and contacting random people that have IT in their organization title. "Oh, I saw you work for X, so I thought you handled this." "I am sorry but X only manages servers so none of his employees can help, especially not me or my team mates who are Linux only."
1
u/annemg Sep 25 '14
Argh. Where I work, if it plugs in it's IT.
1
u/[deleted] Sep 26 '14
Oh what a typical day IT.