"But they are so cute!" Tech Support

"But they are so cute!"
"Yes, it's in the switch"
"It's definitely NOT the file format!"
"Left. More left."
"I'm telling you, it's not there!"
"How was I supposed to know?"
Rules of Tech Support 2022-05-26
Sometimes, you do something that makes you realize you know your job.

Posted: 26 May 2022 05:58 PM PDT

A long time ago, I was on a contract job, doing desktop support for a fairly big company. I got pretty familiar with the good users and the bad users, and I placed a lot of machines for new hires. We had a pretty normal spec desktop for 90+% of the users, and then a workstation spec for power users. This was much more expensive, of course, and it required additional approval.

So one day I placed a new desktop for a new hire. I could tell by the size and location of the cubicle that this was not a VIP, just a regular user (there were definite "class" lines - higher ranks got nicer cubes, higher ranks still got offices). The work order said they got the standard workstation, so that's what I delivered. Got it all set up, working fine. Closed the ticket and moved on with my life.

A couple of day later, I got a new ticket from a name I did not recognize. User states they are a new hire, and the machine performance is unacceptably slow, to the point that they are not able to do their work, and requesting the power user spec desktop. Based on the person's title, their work would have been using Word, Excel, and Outlook, and the standard machine was perfectly adequate for that workload, so something was definitely amiss.

I contacted the user, and they said that they were not even able to open a simple Excel file in a reasonable time. I figured there might be something wrong with the excel file, so I asked them to mail it to me. When it showed up, I was able to open it on my own standard-spec machine with no issues. Not the file, then - something on the machine. I went to the user's desk. It was the same desk, and it was the same machine, I mentioned earlier.

The machine was running full tilt. The cooling fans were at full speed. I asked to sit and check out the machine, and it was immediately apparent that it was CPU bound. It had all the symptoms of a badly overworked machine. The only windows open were, as expected, Office apps. But there were also a bunch of little animated sheep roaming around on the desktop.

Remember these? Or rather the old 16-bit version of those? The user thought they were cute, and so had run a bunch of instances of the e-Sheep so they would have lots of them.

I used the task mangler to kill all the sheep. The machine immediately returned to normal, the fans went back to idle, and the machine was suddenly completely usable. Word, Excel, and Outlook all snappy and working just fine. I advised the user not to run the e-Sheep anymore, and that I would not be recommending her to get a power user machine.

submitted by /u/Automatic_Mulberry
[link] [comments]

"Yes, it's in the switch"

Posted: 26 May 2022 07:35 AM PDT

This story is from a my first ISP job. I worked with designing, building and implementing solutions for business customers, LAN and WAN. This event took place during a very busy friday afternoon. I get a call with a person on the other line who seems to be in a hurry to finish before he goes home.

Unknown caller: Hey, I'm hooking up some new IP-phones and I need you to allocate a new VLAN for them so I can get them to work...

Me: Hey! Who am I speaking to?

Still unknown caller: I'm the networking engineer at company XXYY. Now can you help me so I can go home?

\caller identification process cleared\**

Me: It would be better if you placed an order through the order system. If it's ONE phone I can help you test it out now, more than that and I will have to charge consulting time as you know.

XXYY: Yes, yes. It's one phone lets go.

So I should mention. This company is a big one with alot of offices that have somewhere between 2 and 10 switches managed by us per office.

Me: Sure where are you at and where do you want to connect the phone?

XXYY: I'm at the office (he says this as if I'm stupid for even asking, again ~15 offices available), the phone is in the switch...

Me: Okey. I will have to know at which office and what port and switch you are connected to.

XXYY: Well I'm at ZZXX location, if that really matters... The switch says "Cisco" on it, I think I'm in port 35...

Me: Okey...

At this point I just want this over and done with so I don't question it... I check the switches in Meraki at that location and notice a new phone on one of the ports, create a new VLAN and set it up for VOIP.

XXYY: Good it works, now we can do the rest!

Me: Sorry what?

XXYY: Yea, this one went fast lets get this done before the weekend!

And that my friends is how I charged 4 hours of weekend consulting time for swapping a phone system for a customer who already had a functioning system. How these "technical" people get put into position of responsibility is beyond me...

edit: verification clarified.

submitted by /u/FreakFromSweden
[link] [comments]

"It's definitely NOT the file format!"

Posted: 26 May 2022 12:03 PM PDT

I built one of my AP clerks a flimsy little process to split vendor PDFs by invoice number and then use a couple of excel sheets and some AutoIt glue to look up data and rename the files.

It saved her about five hours of mindless tedium a week with about a 45 min investment from me. She'd been using it happily for about three months and then it quit working. What's odd is that it ran just fine on my PC. So I'm remoted into her PC looking around and she tries to "help" me but she's just annoying me.

"Could this be caused by the server outage last week?"

"No. This is hosted on a completely different machine than the server that was down. So they're not related"

"I noticed there's a file in there named the same as the program I click on but the extension is au3. Maybe that's the problem."

"No! That's just the autoit source code. It's always been there. You just haven't noticed it before"

"One of the excel sheets says it's an excel file and the other says it's an excel 2007 file. Is that why it's not working?"

"No! That's no the issue! One is a 2007 file because that's just how it comes out of the accounting system. Excel can open both files JUST fine. It's definitely not the file format!"

Well after a couple of hours fucking around with AutoIt - which CAN be a little weird sometimes - I decide to convert the 2007 file to an XLSX file. What do you know. It started working on her PC again.

Fuck!

Now I gotta endure a few months of her reminding me about the time she figured out a problem before me and how she should really listen to my advice in the future because she is a very intuitive person and can sense problems easily.

Gonna be a long few months of biting my tongue.

submitted by /u/laplandsix
[link] [comments]

"Left. More left."

Posted: 26 May 2022 10:26 PM PDT

I work in tech support for my small college. It's focused on our learning system and I do accessibility technology work.

Night shift, beginning of summer semester which is basically online only. An older gentleman got on the live chat and said he couldn't find the menu. No problem, click on left side of the screen. User reports that he did and nothing. Hmm. The left most side has a clickable and collapsible menu. Click on it once you find via hovering on the left. User reports negative to usefulness. Great. I get on Zoom.

This is when I learned he was older. Keep in mind, I'm a student worker. I have him show his screen as best as he could via phone (another mess, but not messing with it too much). He is not left enough. I say to go left. User just...doesn't. If there 3 ways to tell someone to go left, I said 10 at least. User just didn't get it. Even my dad (I was at home and he was sitting next to me) told him to go left.

I show him my screen. Show him the menu. It took at least 20 minutes I tell y'all of Reddit to have him go the very left side it the screen (collapsed menu hidden). I basically pulled the "just trust me" card at least twice. I was at my breaking point of confusion. I wasn't sure for a while if this person was using a screen reader, but via Zoom seemed to be sighted. The menu bar collapse and in general sucks for screen readers.

Rule 368 of college support: students of all ages struggle with left and right. Some just refuse to listen when told to go more left.

submitted by /u/Bookworm3616
[link] [comments]

"I'm telling you, it's not there!"

Posted: 26 May 2022 09:44 AM PDT

So a user wanted a certain program installed, lets call it IguanaKit(purely because I was recommended an iguana sushi video before writing this, for some reason):

Me: *sees ticket*

Ticket: I filed a request to have IguanaKit installed on my computer and it is closed successfully, but I do not have it installed. I have IguanaBits, and I see the installer for IguanaKit in the work folder [where we copy things to then use on their computers], but no IguanaKit.

Me: ....Meh, I'll just install it for him again. Aaaand, done. *Closes ticket*

Ticket Reopened: I still do not have IguanaKit, I only see the installer in the work folder, but I do not have permission to run it.

Me: *checks his computer* It is there, its folder is simply called Kit in Program Files. Do not look for it in Work, it will not be there. *Closes ticket. Again*

Ticket Re-Reopened: That is not what I need. I need IguanaKit, and I have no such thing!

Me: ......Program Files / Kit. It is in there. I can see it right now. *Closes ticket.... Again.*

User then opens a direct chat to me...

User: Hey, you were trying to help me with Iguana, but I still dont have it installed.

Me: ...... ಠ_ಠ

*Renames Kit folder to IguanaKit*

Me: There. Better?

User: Thanks, thats the one!

submitted by /u/Nazamroth
[link] [comments]

"How was I supposed to know?"

Posted: 27 May 2022 02:24 AM PDT

My last job was in a school - 200 staff, ~2000 students. Each classroom has a desktop PC with an interactive display board and enough storage space for every staff member who uses that classroom plus a couple of students (in an emergency) to log in and have a local copy of their profile saved. The teachers have been asked not to let students routinely log in to the machines.

So far, so straightforward. Except for one teacher who loves doing student presentations. And don't get me wrong, they're great teaching tools! But he insisted on having every. single. student log in separately, load the PowerPoint, display the presentation, and then log out for the next one.

Naturally, I get a panicked phone call.

Teacher: Help! The computer is so slow! It's taking five or ten minutes to log each person in!

Me: Huh, that's weird, I know you've used that classroom before so it should be quick for you.

Teacher: No, I mean my students. They're all supposed to be giving presentations but it's not logging them in!

Me: Oh, right. As discussed at [staff meeting], students shouldn't be logging in to teachers' PCs- they should share their files with you so you can present them.

Teacher: Well, how was I supposed to know that?! Just fix the machine!

Me: I'm happy to restart it and clear out the saved student profiles, but I will need you to log in, not the students, once I've done that.

Teacher: mumblegrumble

Which... fine. Okay. He's having a bad day, I guess, but at least we solved the problem. Except two weeks later -

Teacher: Help! The computer is so slow! It's taking five or ten minutes to log each person in!

Me: Hi, yes, your students should be sending their files to you so that you can present them from your account.

Teacher: Well, how was I supposed to know that?!

submitted by /u/aimsmeee
[link] [comments]

Rules of Tech Support 2022-05-26

Posted: 26 May 2022 08:13 PM PDT

This list is also available at https://github.com/morriscox/Rules-of-Tech-Support

Rules of Tech Support

Rule 1 - Users lie.

Rule 1A - It may not be malicious or willful, but Rule 1 is always in effect.

Rule 1B - Users assume you don't know they are lying.

Rule 1C - Users continue to lie as a result.

Rule 1D - When caught in a lie, users get angry.

Rule 1E - Users lie even when they aren't users.

Rule 1F - If they are not lying, then they are wrong.

Rule 1G: Accept that you will eventually have to lie to get the user to do what you need them to do.

Rule 2 - Explain everything as simply as possible.

Rule 2A - There is no language simple enough to make a user understand anything.

Rule 2B - Emojis are NEVER an answer.

Rule 3 - User caused problems are caused by tech support.

Rule 3A - As it's your fault, they don't want to be billed.

Rule 3B - All issues are user issues. If there are no users, no issues get reported, no tickets get created. Ergo, it must be users who are responsible.

Rule 4 - If it doesn't work, it is your fault.

Rule 4A - If it does, you had nothing to do with it.

Rule 5 - If you take the time to visit the user's desk, the problem will magically have fixed itself.

Rule 5A - Or the solution is bound to be really simple.

Rule 5B - Or the user left the office moments after entering the ticket, and won't be back for days. How long is uncertain as these users never use their calendar.

Rule 5C - Or when they do, they won't have shared it with you or they entered an all-day event as taking an hour.

Rule 6 - All users consider their situation to be more important than others, even if they know you are helping someone else.

Rule 6A - All users want VIP treatment.

Rule 6B - But they don't ever want to pay for VIP treatment.

Rule 7 - It doesn't matter how much time the user claims something will take. See Rule 1.

Rule 8 - Users never read error messages, if they read anything at all.

Rule 8A - If a user reads an alert or error message, they don't know what to do even if they can only do one thing.

Rule 8B - The more advanced degree a user has, the less likely they are to read anything.

Rule 8C - They will give the wrong error message.

Rule 8D - If a user receives an error, when asked what it says, the user will reply: "I don't know, just an error. I closed it."

Rule 8E - "Isn't it YOUR JOB to know that?"

Rule 8F - Users will not read you the entire error code or message.

Rule 9 - Expect any and all jargon and technical terms (such as wireless) to be misunderstood.

Rule 9A - Expect everything to be misinterpreted.

Rule 9B - All jargon is the same to users.

Rule 9C - All jargon will be used incorrectly.

Rule 10 - About half of tech support is solving issues that are only partially related to what is supposed to be fixed.

Rule 11 - No system is idiot-proof enough to best all users.

Rule 11A - If you haven't found a user able to best your system, it's because they haven't found you yet.

Rule 11B - Nature will take as a challenge any attempt to create an idiot-proof system.

Rule 12 - There is nothing so stupid that no one will do.

Rule 12A - Stupid questions do exist.

Rule 12B - There is no such thing as a stupid question, just stupid people. Asking a stupid question identifies a stupid user and therefore the question itself is not stupid.

Rule 13 - Never believe a user who claims that there is nothing that needs to be saved. See Rule W10 and Rule W10A.

Rule 14 - Sometimes you need to trick users in order to get the job done.

Rule 14A - Sometimes you have to make people, not just users, terrified to get them to do what they are supposed to.

Rule 15 - Users care more about things working than in how you pulled it off.

Rule 16 - A user's appreciation for your work is inversely proportional to how difficult it was.

Rule 17 - If you have an accent, then you will be perceived to be in a foreign country.

Rule 18 - Never trust a user.

Rule 18A - Everyone is a user. Even you.

Rule 19 - The most intelligent person you know will be defeated by a mere computer.

Rule 19A - Even if it's you.

Rule 20 - The quickest way to find out who is responsible for something is to do the scream test. Remove that something and see who complains.

Rule 20A - If nobody screamed instantly, users may wait until it has been long enough that the thing has been thrown away and can't be recovered any more. Then you will learn that said thing was critical for some task that absolutely has to be done right now, just like every X years.

Rule 21 - Never underestimate the power of the end user to complicate things.

Rule 22 - If it looks different, then it's broken.

Rule 23 - Never give a user options.

Rule 24 - When you receive a ticket and call the user immediately they definitely won't be at their desk.

Rule 24A - If you email them they will already be on vacation.

Rule 24B - The less time that they're in the office, the more urgent their issue is.

Rule 25 - Watch out for Finagle's Law which states that 'Anything that can go wrong, will — at the worst possible moment.'

Rule 26 - Always have a small list of phrases to get users to do what you are trying to get them to do.

Rule 26A - Only share these with other techs.

Rule 27 - Don't let people know you are a tech. They are likely to ask for free tech support.

Rule 27A - Never, EVER, give out personal contact information.

Rule 28 - Sometimes, you will be the one who is wrong.

Rule 29 - Expect equipment to be placed in bad locations.

Rule 30 - It's always the printer|DNS|server|browser|connection. It's never the printer|DNS|server|browser|connection.

Rule 30A - It's always the printer. Printers are evil.

Rule 30B - Printers are evil because of users.

Rule 30C - If a document fails to print, users will keep trying just to make sure it prints.

Rule 30D - The true importance of the documents they are trying to print will be inversely proportional to the fit they are throwing.

Rule 30E - Users will mash buttons and go through random menus and do random actions until errors go away or the printer is messed up. See also Rule W84.

Rule 30F - Did you check DNS? Check again.

Rule 31 - All user provided information must be verified.

Rule 32 - If you are a female tech, users will ask to speak to a man.

Rule 32A - You will be the only one who can actually help the user even though they will not believe a girl really knows anything.

Rule 32B - You actually know twice as much as the male techs but get only half the respect.

Rule 32C - Guys will pay more attention to your looks/voice than your mind.

Rule 32D - You'll get tons of calls from men (especially if you are attractive) who will even disconnect stuff to get you to go to them.

Rule 32DD - Women will cause IT problems to keep you away from men.

Rule 33 - Just because it worked yesterday does not mean that it will today.

Rule 33A - Just because it didn't work yesterday does not mean that it won't today.

Rule 33B - Things only work when you are paying attention to them.

Rule 34 - Never refer to this Rule by its name.

Rule 35 - Updates will be both solutions and banes, usually at the same time.

Rule 36 - Sometimes, you have to nuke everything.

Rule 37 - Focus on getting things working, then on getting them done right.

Rule 37A - By hook or by crook.

Rule 37B - When things are working right, leave them alone.

Rule 37C - If something starts working, even if you KNOW what you just did shouldn't have fixed it, raise your hands in the air unthreatening-like and slowly back out of the room.

Rule 37D - You only think it's working. The real cause will wait a while and then break everything in a spectacular fashion a few months down the line. Luckily, by then it's usually no longer your problem.

Rule 37E - It will still be your problem.

Rule 38 - There's always a relevant xkcd.

Rule 38A - If you can't find a relevant xkcd, it's because you haven't looked hard enough.

Rule 38B - If there is no relevant xkcd, there is always a relevant Dilbert strip.

Rule 38C - If there is no relevant xkcd or Dilbert strip, there's a relevant entry in The Seventy Maxims of Maximally Effective Mercenaries. Link L1

Rule 38D - If you can't find a relevant xkcd, Dilbert, or Maxim, your problem does not exist.

Rule 39 - You and your work will never be appreciated since if you did your job right, none of these problems would have happened.

Rule 40 - All IT urban legends are true.

Rule 41 - If it takes TFTS to turn you paranoid, you likely haven't been in tech support for very long.

Rule 41A - You aren't paranoid. They really are out to get you.

Rule 42 - You already know the answer.

Rule 43 - Every tech is also a user.

Rule 44 - Never make changes before going on vacation.

Rule 45 - The more you specialize, the less you will remember about basic desktop functions.

Rule 46 - No technical person reads all of the rules. They will act like they know them until the place catches fire, then complain about incomplete documentation.

Rule 46A - Especially if it was the documentation that went up in flames first.

Rule 47 - Don't help anyone who is not paying you in some way as they won't take your advice seriously.

Rule 48 - Vendors will tell you that you need to upgrade to the newest version in order to fix things. If you are on the latest version, they will tell you to wait till the next version.

Rule 48A - If the problem remains reproducible on the latest version, they may tell you to downgrade. Even if you just upgraded per Rule 48.

Rule 48B - It's not a bug, it's an undocumented feature.

Rule 49 - Never assume anyone else is smarter than you.

Rule 49A - Never assume you are smarter than anyone else.

Rule 49B - A user's intelligence will always be precisely what is needed for maximum damage.

Rule 50 - Scheduled updates won't.

Rule 50A - Anything scheduled will break things, especially if you are not available.

Rule 51 - Drivers will drive you bonkers, if you can even find them. Even if you can find them they may not be compatible.

Rule 51A - Drivers are the real threat, not hardware.

Rule 51B - Drivers using hardware [heavy machinery] are also a real threat. Backhoes/diggers have a magnetic attraction to fiber optics and the drivers have an innate ability to find optical fiber. Link L2.

Rule 52 - No is the answer for every request as long as it's plausible.

Rule 53 - Treat your job like a role playing game. Link L3.

Rule 54 - Don't run stuff that you are not supposed to unless Rule 37 and Rule 37A apply.

Rule 55 - The Seventy Maxims of Maximally Effective Mercenaries are always applicable. Link L1

Rule 55A - Sometimes the applicability of the Maxims is not immediately obvious.

Rule 56 - Get to know the Dunning-Kruger effect. Link L4.

Rule 57 - You might want to consider starting the day with coffee or tea and ending with whiskey or scotch or bourbon or beer...

Rule 58 - Vendors might not follow standards.

Rule 59 - You might find people who support you. Reciprocate.

Rule 60 - When a user activates the Swedish Fish rule, they get preferential treatment.

Rule 61 - Like the military says, never volunteer.

Rule 62 - Some bugs are Heisenbugs; they can only occur if they are not being observed. Users do not count as observers.

Rule 63 - Something will be needed right after you get rid of it.

Rule 63A - Once you replace it, you will no longer need it.

Rule 63B - You will buy something and then find out that what you currently have already has what you needed.

Rule 64 - User managed projects will always fail.

Rule 64A - And they will blame you.

Rule 65 - You will complain about something and then realize that you are the one that is guilty.

Rule 66 - You will find yourself putting out fire after fire without any chance to document anything.

Rule 66A - Then get blamed for not documenting everything.

Rule 67 - Try using metaphors and analogies in addition to or instead of technical terms.

Rule 68 - The higher rank an employee is, the more problems you will have with them.

Rule 69 - Refer to Rule 34.

Rule 70 - Anything that will show up as a link should be a link.

Rule 71 - Never take actions that assume a system is a certain way.

Rule 71A - Especially if not assuming makes little or no difference to the troubleshooting process.

Rule 71B - And never if the incorrect assumption will be recognizable to the user.

Rule 72 - Always give users the least amount of access/permissions that you can realistically get away with.

Rule 73 - It's always Dave or Steve or Kevin. Unless it's a Karen.

Rule 74 - Try to phrase things in a way that helps users save face.

Rule 75 - Maintenance, and sometimes coworkers or users, will unplug things and plug them back in wrong or not at all.

Rule 75A - If anything goes wrong they won't tell anyone. You will get to handle the "website down!" or "the internet stopped working!" tickets.

Rule 76 - Only have the minimal required equipment needed for users.

Rule 77 - Your company will be in a very old very shoddy building.

Rule 78 - If someone is acting odd, it might be a social engineering attack. Verify everything.

Rule 78A - VIPs within the company that actually do have the power to have you fired at whim will be the most angered by attempts to verify and will be the hardest to verify.

Rule 78B - Social engineering attackers know Rule 78A.

Rule 79 - Users think they can connect to anywhere from anywhere.

Rule 80 - If this port is taken, port 443 will be as well.

Rule 81 - Most of your job is figuring out what users are talking about.

Rule 81N6 - The GoogleBing awaits.

Rule 82 - Temporary solutions aren't.

Rule 83 - Rule 83 - Every company has a Production environment and a Testing environment. If you're lucky, they are separate environments.

Rule 84 - Users already have a certificate of proficiency in computering.

Rule 85 - Always let someone know that you are there to fix a problem.

Rule 86 - You might encounter a user who is nice, doesn't need everything explained, takes you seriously, reads you complete error messages, and does what you tell them to do with no drama. neigh Seriously, they do exist.

Rule 87 - Users who always demand the latest hardware never work in a position that requires the latest hardware.

Rule 88 - Sometimes you need a user to fix your problem.

Rule 89 - You will be expected to be your own tech support.

Rule 90 - You will have to support software older than you are.

Rule 91 - The OSI model has layer 8 (user) and layer 9 (management).

Rule 92 - It's always a bad sign if someone is happy to see you.

Rule 93 - "Only one thing" never is.

Rule 404 - You will never find it. See https://www.explainxkcd.com/404

Rule 404A - If a page is not found, then the entire site|Internet is down.

Rule 600613 - Used to go to websites instead of going directly.

submitted by /u/morriscox
[link] [comments]

Sometimes, you do something that makes you realize you know your job.

Posted: 26 May 2022 11:09 AM PDT

I was reading another post on here that involved VoIP and switches. It reminded me of an incident that happened at one of my past jobs, and my first one in the corporate IT world. Not a particularly good story, but eh. We ain't all u/lawtechie or r/airz23.

Small background, this place had what they called L1, L2, and MAC teams. L1 was phone support, L2 did the onsite/more involved tickets from L1, and MAC was the Move/Add/Change team. They did installs/moved equipment/etc. Everyone rotated through once per week (i.e., you were L1 every three weeks.)

Two of us were hired on at the same time, so during training, I was on L1 for two weeks, L2 for a bit, and it was a good month before they put me on MAC. The other guy started on MAC and swapped with me after a few weeks.

The guy training me (and later friendly coworker) and I were sent out to install a temporary network switch in a conference room that was going to need a handful of VoIP phones, and laptop computers. We arrive with the crustiest 10/100 Cisco 48 port switch (they didn't need fast) and he plugs it into one of the two available network jacks in the room. Switch lights up, then when he tests it with our laptop, can't get access to the network. A little fussing and we see the activity light isn't active on the uplink.

Eh, we try the other port. Maybe that one has an issue. Same thing.

I don't recall how I came to it; but I asked if we used BPDU or similar on our network. He'd never heard of it; and I wasn't a network admin, just reasonably familiar due to playing around with gear since I was in my early 20's (I would have been 32 at this time.).

I explained the best I could (remember, not an SME by any stretch) about what port security was and he called in a favor to one of the network admins asked about it. Turned out that, yes, we had port security and a single MAC address limit. So the switch was fine, but when you'd plug in the laptop, it'd trip the security and shutdown the port. They opened it up and we were good.

After a week, I was on normal rotation. A few years later I was talking with him and that first day came up. I think I mentioned how the other guy had, had, like three weeks of training and I had only one week. That was when my friendly coworker told me, "Yeah, I went to my team lead and said, we don't need to train him. He already knows more than I do." So they taught me some of the the specifics that week, but just let me get on with it afterwards. Turns out that the other guy got so much training because he just didn't get it. And still didn't get it. Then finally kind of gave up and stuck him on phones.

TL;DR - Sometimes, you actually do know your stuff, don't ever think you're an imposter.

submitted by /u/Slightlyevolved
[link] [comments]

Breaking News

Tech Support

Friday, May 27, 2022

"But they are so cute!" Tech Support

"But they are so cute!" Tech Support

Rules of Tech Support

Rule 1 - Users lie.

Rule 2 - Explain everything as simply as possible.

Rule 3 - User caused problems are caused by tech support.

Rule 4 - If it doesn't work, it is your fault.

Rule 5 - If you take the time to visit the user's desk, the problem will magically have fixed itself.

Rule 6 - All users consider their situation to be more important than others, even if they know you are helping someone else.

Rule 7 - It doesn't matter how much time the user claims something will take. See Rule 1.

Rule 8 - Users never read error messages, if they read anything at all.

Rule 9 - Expect any and all jargon and technical terms (such as wireless) to be misunderstood.

Rule 10 - About half of tech support is solving issues that are only partially related to what is supposed to be fixed.

Rule 11 - No system is idiot-proof enough to best all users.

Rule 12 - There is nothing so stupid that no one will do.

Rule 13 - Never believe a user who claims that there is nothing that needs to be saved. See Rule W10 and Rule W10A.

Rule 14 - Sometimes you need to trick users in order to get the job done.

Rule 15 - Users care more about things working than in how you pulled it off.

Rule 16 - A user's appreciation for your work is inversely proportional to how difficult it was.

Rule 17 - If you have an accent, then you will be perceived to be in a foreign country.

Rule 18 - Never trust a user.

Rule 19 - The most intelligent person you know will be defeated by a mere computer.

Rule 20 - The quickest way to find out who is responsible for something is to do the scream test. Remove that something and see who complains.

Rule 21 - Never underestimate the power of the end user to complicate things.

Rule 22 - If it looks different, then it's broken.

Rule 23 - Never give a user options.

Rule 24 - When you receive a ticket and call the user immediately they definitely won't be at their desk.

Rule 25 - Watch out for Finagle's Law which states that 'Anything that can go wrong, will — at the worst possible moment.'

Rule 26 - Always have a small list of phrases to get users to do what you are trying to get them to do.

Rule 27 - Don't let people know you are a tech. They are likely to ask for free tech support.

Rule 28 - Sometimes, you will be the one who is wrong.

Rule 29 - Expect equipment to be placed in bad locations.

Rule 30 - It's always the printer|DNS|server|browser|connection. It's never the printer|DNS|server|browser|connection.

Rule 31 - All user provided information must be verified.

Rule 32 - If you are a female tech, users will ask to speak to a man.

Rule 33 - Just because it worked yesterday does not mean that it will today.

Rule 34 - Never refer to this Rule by its name.

Rule 35 - Updates will be both solutions and banes, usually at the same time.

Rule 36 - Sometimes, you have to nuke everything.

Rule 37 - Focus on getting things working, then on getting them done right.

Rule 38 - There's always a relevant xkcd.

Rule 39 - You and your work will never be appreciated since if you did your job right, none of these problems would have happened.

Rule 40 - All IT urban legends are true.

Rule 41 - If it takes TFTS to turn you paranoid, you likely haven't been in tech support for very long.

Rule 42 - You already know the answer.

Rule 43 - Every tech is also a user.

Rule 44 - Never make changes before going on vacation.

Rule 45 - The more you specialize, the less you will remember about basic desktop functions.

Rule 46 - No technical person reads all of the rules. They will act like they know them until the place catches fire, then complain about incomplete documentation.

Rule 47 - Don't help anyone who is not paying you in some way as they won't take your advice seriously.

Rule 48 - Vendors will tell you that you need to upgrade to the newest version in order to fix things. If you are on the latest version, they will tell you to wait till the next version.

Rule 49 - Never assume anyone else is smarter than you.

Rule 50 - Scheduled updates won't.

Rule 51 - Drivers will drive you bonkers, if you can even find them. Even if you can find them they may not be compatible.

Rule 52 - No is the answer for every request as long as it's plausible.

Rule 53 - Treat your job like a role playing game. Link L3.

Rule 54 - Don't run stuff that you are not supposed to unless Rule 37 and Rule 37A apply.

Rule 55 - The Seventy Maxims of Maximally Effective Mercenaries are always applicable. Link L1

Rule 56 - Get to know the Dunning-Kruger effect. Link L4.

Rule 57 - You might want to consider starting the day with coffee or tea and ending with whiskey or scotch or bourbon or beer...

Rule 58 - Vendors might not follow standards.

Rule 59 - You might find people who support you. Reciprocate.

Rule 60 - When a user activates the Swedish Fish rule, they get preferential treatment.

Rule 61 - Like the military says, never volunteer.

Rule 62 - Some bugs are Heisenbugs; they can only occur if they are not being observed. Users do not count as observers.

Rule 63 - Something will be needed right after you get rid of it.

Rule 64 - User managed projects will always fail.

Rule 65 - You will complain about something and then realize that you are the one that is guilty.

Rule 66 - You will find yourself putting out fire after fire without any chance to document anything.

Rule 67 - Try using metaphors and analogies in addition to or instead of technical terms.

Rule 68 - The higher rank an employee is, the more problems you will have with them.

Rule 69 - Refer to Rule 34.

Rule 70 - Anything that will show up as a link should be a link.

Rule 71 - Never take actions that assume a system is a certain way.

Rule 72 - Always give users the least amount of access/permissions that you can realistically get away with.

Rule 73 - It's always Dave or Steve or Kevin. Unless it's a Karen.

Rule 74 - Try to phrase things in a way that helps users save face.