I tend to just check uptime before asking this question.
If I see the machine has been up for weeks and they tell me they rebooted it, I know i'm dealing with someone who doesn't know that pressing the power button on the monitor doesn't turn the computer off.
I had one where yes everything was plugged in but... The power strips never plugged into the wall... They were just plugged into each other.
That one turned out to be an annoying bit of cable management that I wouldn't have had to do if they would have just left things alone and let me handle the original ticket
Took my freshly re-cobbled together computer to local computer guy after an upgrade with hand-me-down parts. He asked what was wrong and I said there was an alarm for the CPU fan, and that I'd torn the case open and hooked a second fan into the CPU fan connection and it also didn't work, and the I plugged the CPU fan into a different connection and got it working, so by elimination I was pretty sure the fans were good and the connection in the motherboard was bad.
He seemed mildly amused/impressed by my spiel. I'm not really a computer person, but swapping out parts to narrow down the source of the problem seemed logically basic.
I ended up chilling with him while he worked on things. He found WinZip on my desktop and let out a "whoa retro." which hurt me deeply.
E2: of course that's not why I told her. I explained how fastboot sometimes takes over and doesn't actually restart the device, only "refreshes" the experience. I recommended she restart at least once a week. We'll see what happens.
windows doesnt actually shut down, its some kind of hybrid hibernation now. it only really reboots if you actually reboot. so they may actually be "shutting down" every day.
If I had a nickel for every time I was troubleshooting with a friend and discovered they thought turning the monitor off and on again was "rebooting the computer" I'd be depressingly wealthy.
*Shuts the laptop lid and opens it.
“Ok! It’s restarted”
IT person: “Well that was certainly quick. Are you sure you restarted it?”
Person: *Feels smug about how they were able to restart quicker than most people.
I feel like there's a specific peak between total technical ignorance and a weary understanding of how fickle technology can be. On this peak is the height of arrogance, where you believe you've really got everything figured out. Part of learning is understanding that, yes, sometimes you really did just forget to plug the modem in.
Yep, that one where the person on the peak starts lecturing you in abstract terms about trying the simplest hypotheses and such, while you are trying to solve their problem.
I know the philosophy part that asshole is talking about, only he has no bloody clue which part is simple and which is not here.
I remember some old movie that was on TV ~30 years ago. A terrorist group broke into some computer room to destroy the data. They shot the monitors to smithereens and ran away.
Considering our IT department replaces computers without moving over our files (like come on, just swap the drives!), I honestly wouldn't be surprised if that's how they'd treat it.
Honestly most unsavvy people don't even realize they can turn their monitors off. Especially if the buttons are behind or under the screen, they wouldn't even know the buttons were there.
There's some older ones where there are actual buttons on the bottom of the screen. Beats me how the people who press them to turn it off manage to press the power button for the PC to turn it on.
As someone who has been asked to restart the computer, even though I already did that before calling IT support... I internally sigh, but begrudgingly do it again just to appease their process. Because I assume plenty of people don't do it and make y'alls life a tiny bit harder, when a restart would've fixed it
Also, how many are solved by making sure the power cable is not just plugged into the wall, but seated into the back of the computer as well?
I swear I could hear the call center employee (probably not really an IT guy at this stage) sweating when I called them after a thunderstorm fried my router's entry port and I read them the list of troubleshooting I already went through before calling them.
"Hi so to save us some time I've restarted the computer, went ahead and assigned a static IP to all devices and put them all on the same sub net. While in the router I noticed there was a firmware update so I managed to do that removing the ROM chip and wrote an open source os that uses half the resources of the factory one..."
I spent months trying to tell my ISP that their side of a DHCP transaction wasn't giving me my IPv6 address, being so specific as to send them the exact offending packets but it wasn't until I took my entire network apart, unboxed their shitbox router and plugged that in that they would believe me.
One day my MIL's Macintosh stopped being able to connect to the Internet over its internal ethernet, which was directly connected to the cable modem.
They called Comcast a bunch of times to no avail, so they sent someone out to check it. He had no idea what was wrong, so I said "Let's connect your laptop to the Mac with an Ethernet cable just to make sure the Ethernet works."
Dude looked at me like I had two heads. "It doesn't work like that."
I proceeded to grab a patch cable, hook them together, and mount the Mac's public shares on the Windows machine, thus proving the Ethernet worked on both systems.
Turns out Comcast had changed the MTUs on the modems one night, which made the Mac not work for some reason. But getting a cheap router and putting it between solved the problem.
I worked with a guy that would tell people that coax needed to be "released to ground" occasionally, by unhooking the cable and putting your thumb over the end. That's how he made sure people were disconnecting and reconnecting the cable from the back of the box. He also told someone that "data might be trapped in the Ethernet cord" and advised they unplug it from both ends and swing it around their head in a circle to "loosen the stuck bits and clear the line"...
I think the idea is that average people have no clue what color they are. So they'd be forced to take it out to check and thus have to restart their PC. It's a trick!
Altho, maybe I'm misunderstanding something because all the pins of all the electrical cords I've ever seen have been silver?
I'd make up some BS about an old version of the product using brass or copper, and newer versions using aluminum or iron, so knowing the color will help me know how to fix it
Then you look at the uptime. 247 days. No longer have you been elevated. Now you're the vilest of vile. You're the user that lies. You just say what you think we want to hear, don't you? Well, now you're getting put on hold. For as long as your uptime was.
Yup this is exactly what I was going to post. Was in the industry for 10 years and call me pessimistic but the second they told me they'd already rebooted I'd check uptime.
We have a running leader board for uptime. Servers don't count.
That said, I've seen some people who think they actually are turning it off but the machine just enters sleep mode. I only trust
Contacting IT is always my last line of defense and I get unreasonably frustrated when they refuse to help without walking me through basic troubleshooting. It's like, I've already figured out the cause of the problem, just tell me where the button is to fix it. The worst was when I had to RMA my Pixel phone and they made me go through every step I'd already been through just to come to the same conclusion I initially came to them with.
Me to Google support for a problem with my brand new pixel 3 back when the 3 was the new hotness
Me: my camera only works for one photo, then doesn't work again until I reboot it. Then it again works only for one photo, then it gives the error "camera [number] is locked" (screenshot)
Support: that sounds like a fault. Could you reboot your phone and tell me what happens?
Me: ok. ... Right I'm back. Just like for all the ten photos I took before contacting you, it worked for one photo then that same error. That makes eleven times I rebooted my phone today.
The worst for me was with the Nexus 6P, the last phone before they rebranded to Pixel. There was a known issue with the battery, where it would die when the phone said it was at like 50%. I jumped through all their troubleshooting hoops when it was obviously a hardware issue. They eventually agreed to send out a replacement and I was assured it wouldn't have the issue. Lo and behold, it did the exact same thing as soon as I got it. I went through all the trouble shooting again and they sent ANOTHER replacement that still had the issue. I was so fed up and just kept requesting to talk to someone higher up and they eventually just sent me a Pixel 1 to shut me up.
Having worked in IT about 12 to 15 years ago I can honestly say I just stopped believing people when they told me they did things or checked things because 99% of the time it was just a flat out lie.
And taking them at their word meant wasting my own time because usually it was just a quick fix that I suggested in the first place.
It quickly, quickly taught me that 99% of people are fucking idiots, and that even the smart ones who actually knew what they were doing with a computer could be idiots too.
Google support is a joke, I had to RMA a tablet, obviously went through all the troubleshooting before (factory reset included). The dude on the Hotline was like: "fantastic you did everything I would have told you. Unfortunately our system doesn't accept that way of working I need to send you an email with the same troubleshooting steps you already did and you need to call again in a few minutes and confirm to a new support agent that you followed what the email told you"
To their credit it was accepted afterwards with no issues but that whole process is more than braindead
Depending on what you're needing done, a lot of times IT has to cover their asses. If it didn't happen on that phone call, it didn't happen. I always appreciate the gumption, you probably saved us like, 30 call just from figuring out other issues yourself. If it's anything that will cost the company money, though, like replacing hardware - if I don't take due diligence in making sure those earlier steps are done, it's my ass on the line.
You know you're smart enough to do the troubleshooting, but that technician has probably 1000+ users that rotate weekly, they can't keep a log book of which ones are good and which ones will land them in the shit. I totally get the frustration, but the ones who lie about doing simple troubleshooting ruin it for everyone.
My buddy had google support tell him to send a screenshot of his phones screen burn in. They took a good amount of convincing before they admitted that that wouldn't work.
Any time you’re working with somebody who has to deal with the general public(or general workforce) though, you gotta be understanding.
They have to sort through the clueless people who turned off their monitor, and they have to deal with the Dunning-Kruger people who lie about what they did because they think they’re so damn smart.
And if it’s the first contact level 1 type support, they may not have the expertise to tell the difference and have to rely on the scripts.
Yeah, for sure. As frustrating as it may be, I'm always understanding with the support agent. They're just doing their job, it's not their fault there's a procedure they need to follow.
To be fair even the most technically adept person can have tunnel vision where they start digging before ruling out all the simple stuff. Yes it can feel tedious and a little condescending to follow all those steps, but you get humbled the first time it really is just an unplugged cable.
As a former IT help desk person, I can confirm that we do in fact love it when people give us good info. People who write screen broke shouldn't be working with technology more advanced than a shovel
I find this a fascinating phenomenon. Some of it is ignorance of the technology. Which I get because you can't expect everyone to be experts (but if you don't know the difference between a browser and your desktop just fuck off back to the bronze age).
The other is a true lack of empathy in the context of communication. Being able to communicate effectively with an equal onus on both parties to understand and adapt the dialog until the information has effectively been transferred is not hard, really, but some people just don't care enough about the person on the other end of the line to be bothered.
That is infuriating when you're trying to be helpful.
Developer here, same applies to bug reports, I have one or two clients that have realised if they put in a high quality bug report, the Dev team will just jump on it straight away because they have all the info they need and we love fixing bugs. Whereas the vast majority of "X doesn't work", or "I can't do Y" tickets have to be triaged by the support team which can take hours or days.
Tl;dr Give your techs all the info they need to be able to investigate your problem and you'll get faster service and more respect.
I work in our service department myself (not as support tech though), but obviously, all tickets are supposed to go through 1st level. I don't wanna be the dick skipping queue, so I did then one time I had an issue.
There's a unique feeling of satisfaction to submitting a ticket with basically all the 1st level troubleshooting in the notes, allowing the tech to immediately escalate it to a 2nd level team. One quick call, one check I didn't know about, already prepared the escalation notes while it ran. Never have I heard our support sound so cheerful.
Still riding the high of RMAing my Index. Included all the steps I did and the reply was essentially, "Thanks for troubleshooting, confirm your address and we'll ship your replacement."
My favorite little story was while working short-term at a company. Had some issues, did my normal troubleshooting steps and Google searches, identified what I felt the issue was and knew I wouldn't have enough access to fix it. Reached out and got a response "Blah blah blaaah schedule blah blah Remote-In."
Later on he sent me a message and remotes into my computer. I take control quick, open up notepad, and type out "Hi!"
To this day I swear that little show earned me more difficult fake phishing attempts. Which I mention because he specifically told me one day he had experience in the information security sector. Lo' and behold!
Recently, I decided to install arch linux on an old laptop my sibling gave to me. I'm not new to Linux, I've been running a debian server for a year now and I have tried several VMs with different systems. But this was my first time installing arch without a script, and on bare metal.
Installing arch itself wasn't that much of an issue, but there was a bigger problem: the PC didn't recognize the pendrive for boot in UEFI mode. It seemed to work in the regular boot mode, but I didn't want to use that. I made sure to deactivate safe mode and all the jazz. Sure enough, I could get UEFI boot working.
I install arch, works fine, I reboot. Oops! I didn't install dhcpcd and I don't know how to use network manager! No internet, great!
In my infinite wisdom, instead of trying to get NM to work, I decided to instead chroot back into the system and install dhcpcd. But my surprise when... The boot menu didn't recognize the USB again. I tried switching between UEFI and normal boot modes on the bios and trying again, after all it appeared last time after changing it, right?
"Oh it doesn't appear... Wait, what's this? No boot partition found? Oh crap..."
Turns out, by changing the setting on the BIOS I probably deleted the nvram and with it the boot table settings or whatever they're called. I deleted GRUB.
Alas, as if to repent for my sins, God gave me a nugget of inspiration. I swap the USB drive from the 3.0 port to one of the 2.0 ports on the other side and... It works, first try. The 3.0 port was just old and the connection bad. And I just deleted GRUB for no reason.
Usually, I would've installed everything from scratch again, but with newfound confidence, I managed to chroot into the system and regenerate the boot table or whatever (and install dhcpcd). And it worked! I had a working, bootable system, and an internet connection to download more packages.
I don't know what the moral of the story is I just wanted to share it :)
I like to imagine an IT person telling someone that story to see whether they understand it or get a stroke, as a way to check if they were telling the truth about being good with computers and having tried everything, or something.
I was on the phone with our ISP after our internet service went out. The rep asked me if the box had a green light on it - yes - then asked me to plug a light into the same outlet and confirm the power was on. I said, "Look, I understand you have to follow a script, but you literally just asked me to confirm the power light on the box was on. Clearly the power is working."
Same ISP sends me an email whenever we have a power outage letting me know that our internet might not work when the power is out. (I've joked that this email arrives before the ceiling fans have come to a stop.) But when my internet goes down, they're completely clueless. "Ohhhh it must be that your power is out even though we monitor that closely and aren't showing a power outage right now!"
As an IT person, hearing that someone has already restarted to try to fix it, gives me mixed feelings.
First, they might be lying. I've had it happen that people tell me they've done something when they have not. Restarting is usually an easy one to verify, just check the uptime of the system.
Second, maybe they did everything right, and actually restarted, that's cool that they tried something before calling in. I appreciate that.
Third, if the second thing is true then, I'm now frustrated, because now I have to get dirty with whatever is happening since a reboot that should have fixed the problem, didn't fix it. I know it's not going to be an easy fix. Most of the time, I'm right, unfortunately.
I'm all for users trying stuff before calling in. But recognise that you don't, and shouldn't have access to some things. Sometimes that's administrator rights, sometimes that's a piece of software, sometimes it's the ability to turn off the AV/firewall.
It can be a lot of things. If you're not sure if what you're trying won't screw things up more than they already are, then don't do it. If it's something simple that you know how to do, go for it. If you happen to get it fixed, so much the better.
"Customer self resolved" is usually the fastest way to get a problem resolved. That's good for you, for me, and good for everyone.
If I am calling IT to fix anything, it's because I've exhausted all the usual things to fix it (restart, clear cache, make sure everything is seated, googled the issue, etc). 9 times outta 10, they're just as stumped as I am and the device simply gets replaced. That 10th time tho it's something I've never encountered but they have.
I would call IT and give them error codes and attempted remedies. They would do house calls and leave with a few rip its. Everyone in my office usually had my call IT because they (my coworkers and the IT guys) knew I'd at least tried something. If someone else from the office called IT, they knew that I was out of the office or the user was lying about something.
I support doing the troubleshooting yourself. Just be aware, if you call with one of those 9 out of 10 cases, we're still going to have to do ALL of those steps again, so I can document that we tried them before sending any hardware. I've been burned one too many times by someone telling me they've already tried something.
I started in IT before switching to development. I have CCNA, A+, and Apple Pro certifications. I run Arch at home, btw. But when I have to contact IT, usually for something that needs elevated permissions or bad hardware, I'm just another user. It's mildly infuriating to go through all the steps again, even after explaining what I did. I get it, I really do, but it's not fun at all.
Meanwhile I had an IT guy think I was just being an idiot. He was so confident I hadn't checked something. Felt good when I showed him where it went wrong.
As system administrator, yesterday, one worker told me that they accidentally exited email and couldn't get in, guess what, i just hit the log in button and it entered, guy just wanted a smoke break
I have a dark secret. I used to have CenturyLink DSL around 5 years ago, and the tech asked me if I had restarted the modem during one of the many stints where I would get bits per second rather than the "10mbps" we were supposed to get
I lied every time. I'm sorry CenturyLink tech support employee, but man did CenturyLink suck, and man am I absolutely sure that it never fixed the issue.
At one point I filed a complaint with the FCC and got a letter from CenturyLink telling me that they knew about the complaint!
Its actually the worst advice when you haven't figured out what it is, something like a virus (ransom ware, ad shit or similar) usually only works after a restart, if you don't restart, the IT guy can remove it without much damage.