My computer is sentient Tech Support |
- My computer is sentient
- "I know I'm doing it right, I'm not stupid.."
- Some thoughts are only for INSIDE your brain
- Watch what you say.
- This has been happening for over a year
- If a hole exists someone will fill it
- Try doing the other steps after Step 1
| Posted: 28 Apr 2018 08:13 AM PDT I do not work in IT. I am fairly tech savy though and grateful for IT's assistance. The following is one of the stranger issues that I submitted to them, which they did not believe at first. It happened a number of years ago. The first bit of this story took place over a couple weeks. I became frustrated because IT kept closing my ticket even though the problem persisted. My Issue
IT
Me
IT
Me
IT
Me
IT sounding annoyed
Me
I pointed at the green power light on the tower of my computer, to show that the light worked. I then logged out and shut down the computer. The light turned dark and the computer hardware sounds stopped. Me
IT nods and looks at me like I'm a bit dumb. He moves forward as if to boot it up. Me
We both stared at the powered down computer tower. Awkward. After about a minute, there was an audible "click" sound. The green power light lit up. The hardware began to make its usual noises. After another few moments the login screen appeared. IT looked stunned. Me
IT
IT then searched around looking for loose cables around my desk and peeked over the cubical wall to see if others were pranking both of us. Finding nothing, he then disconnected my tower, took it to the IT desk and provided me with a loaner laptop. A few days later, he returned with a new desktop tower. Me
IT laughed, sounding a little amused and slightly sheepish as he plugged everything in for me, then booted it up to the login screen. When he finished that he answered with a big grin. IT
Me
[link] [comments]  |
| "I know I'm doing it right, I'm not stupid.." Posted: 28 Apr 2018 02:39 PM PDT So, I work in a large warehouse for a logistics company on the admin team. One small but regular part of my job is sorting out issues the warehouse floor workers get with the equipment that they use to scan products that are going to be shipped out. For some products, you have to first scan the barcode on the box as usual, then enter a number on the numpad, and then scan it again because the weight of that particular box needs to be recorded in our system so we know how much to charge the customer. This is the cause of a super common issue with new employees because they always scan the wrong barcode the second time and get an error message on their screen, which sends them running to me. It's a really easy fix, and 90% of the guys that encounter the problem get the idea after the first time and don't do it again, but last week I had a guy get stuck on this over and over again, coming back to me every two minutes to get it fixed insisting he was scanning the correct barcode. Usually I can sort this out without having to leave the office so I'd normally be a little annoyed, but I wasn't that busy at the time and I wanted to be fair and see if maybe it was just a weird problem with that particular scanner he was using. He seemed competent enough and shit happens, you know? So I walk out with him to his pallet where the boxes were, take a quick look to make sure they're the right product. (Sometimes a product will get put into the wrong spot in the warehouse) Everything seems fine, so I ask him to scan them again just so I can maybe see what's going on. He assures me again that he's doing it right, so he kneels down and starts scanning the barcodes.
...but this noble error message is not enough to stop him, he just keeps on scanning boxes. He doesn't even close the error message, so nothing he is doing is actually coming up on the screen, he's just going at it like it wasn't even there. I really didn't even know where to start.. sure, I'd encountered people who just click straight through error messages without reading them before, but this was a different kind of beast. Continuing the motion of using the screen as though there wasn't a huge error message waiting for confirmation sitting there, preventing any other input.. [link] [comments]  |
| Some thoughts are only for INSIDE your brain Posted: 28 Apr 2018 06:44 PM PDT Many many years ago I was young and clever, and I knew everything. I worked repair for some very large machinery. I discovered that I'd much rather NOT do that. So I found a gig in an office translating the machine operators list of problems into actual words the repair crews could understand. This has proved a very handy skill in that I frequently have no problems discerning what $users are trying to tell me in my current IT field. This tale comes from my time in that office. The Machinery my department repaired had lots of complex systems and some of them them (all of them) had been built by the lowest bidder, which led to all sorts of many fun times. One system in particular was crucial for the operators safety, and was slightly better than garbage. $system frequently failed, frequently like 50% of the time. Part of my job was to document any issues the operators identified, as I said. One night and operations crew came in and told me the system had failed, so I appropriately documented this issue within our computer machine system like this: $system broke again. Big surprise. Happy me trots off home at the end of my shift, and returns at my scheduled time the next day, to find my boss wanted some of my time. $boss: "superflu....did you put this ticket in?" $me: "hehehe nervous chuckle yeeeeesss?" $boss: "well. I find it amusing, if not particularly professional, however the division manager (my bosses, bosses, bosses, boss) did not find it funny. He's been convinced to let it go this time, if it happens again you can assume your career will not fair well". Moral of the story: Don't document your own smartassery, it occasions offends. [link] [comments]  |
| Posted: 28 Apr 2018 04:14 PM PDT This is a bit of a short one. I've only posted on here once before, but as a bit of background info I do tier 1/2 for a small construction company. Anyway, TLDR of this thread; Watch what you say.
I was finishing up a ticket with a user, in person. As we're a small company we don't have remote access software installed on every PC to keep costs down (I'm gonna get arthritis by 40). While walking out of the room, a guy stops me. This guy, let's call him Frank, goes "on site" a lot. I believe he's a supervisor, so sometimes he does work in the office, like reviewing plans before going out, etc. Anyway, Frank called me over and asked me to take a look at his tablet, it was slow and he wanted a new one. - I joked with him before looking at it, the quickest way to get a new one is to pour coffee over it. I spent fifteen minutes cleaning it up, and handed it back to him and didn't think much of it. One morning, about two weeks later, I arrive to see my co-worker inspecting a tablet. He said it appears water damaged. Frank said it "just stopped working". Co-worker said he thinks Frank spilt coffee on it. [link] [comments]  |
| This has been happening for over a year Posted: 28 Apr 2018 08:05 PM PDT Just a short story that has been happening to one of our clients which we've had to escalate to Microsoft because sigh. Most of our clients are on Office 365 for email based on the fact they're either small or are not always working from their office. Delegate access is probably best for giving a PA control to accept or decline invitations as well. Sadly it's usually the first thing to come up when you Google how to share calendar Outlook. But what we discovered is that the delegated permissions were "stuck" for the lack of a better term. We all had a think about it and looked for PowerShell fixes but nothing useful came up.
To cut a conversation short, they didn't understand.
Simply put: I call $User1 and explain what we're doing and she's happy to get it fixed. I take a moment to hide anything that shouldn't be seen by outside eyes start the capture, send a test invite, it appears then I go into the settings and show that delegate access is completely blank. Did I mention they're Mac users? I feel that may be worth mentioning.
I try to finish up the call.
There's what I want to say and what I actually say. I face palm and turn to my colleague who looks at me expecting me to ask a question.
THIS time I finish up the call and hangup. I call $User2, leave a voicemail. She calls back in the afternoon we do a similar process and I reply to the email Microsoft sent with the ticket number asking for a call back. TL;DR There is no ending to this story just yet as we're waiting for a technician to run "some back end scripts". When it is resolved I can't imagine it'll be worthy of a story. [link] [comments]  |
| If a hole exists someone will fill it Posted: 29 Apr 2018 12:05 AM PDT This isn't so much a story more just my questioning the sanity of the human race. I was a tech at a high school for five years. In those five years the thing that amazes me the most is the things people would put in CD/floppy slots/trays/bays. The short list off the top of my head: -Peanut butter -Vaseline -Vaseline again but this time with air soft pellets -grapes. They were pretty much wine and rot when we found them. -fingers - an approximation of a CD made from some form of lunch meat -paperclips. Constantly. -dirt/sand/sawdust -shaving cream -what I think was oobleck once but was pretty much hard dry paste when we found it And those are just some of the things that were intentionally put in there. There was also the endless stream of spills, and impacts caused by some higher up thinking that securing the tower under the desk was a good idea [link] [comments]  |
| Try doing the other steps after Step 1 Posted: 28 Apr 2018 01:21 PM PDT I'm a small-time computer tech helping mostly home users. I use a RAT (Remote Access Tool), that gives very detailed, simple instructions to clients for how to install it. Those instructions are even specific for which browser the client is using. They are given as Step 1, Step 2, etc. Included in the instructions are screen captures showing exactly what the client is supposed to do. I was stumped as to why the RAT was not working for this one client. He kept insisting that he was following all the instructions to the letter, but nothing what happening. After awhile, I determined that in Step 1, he was clicking the "Download" button in the screen capture EXAMPLE, not the actual "Download" button. Great! Problem solved, right? Sigh, not yet. He kept saying he was following all the instructions, but it turned out that he just kept pressing that "Download" button repeatedly, not progressing beyond Step 1. [link] [comments]  |
| You are subscribed to email updates from Tales From Tech Support. To stop receiving these emails, you may unsubscribe now. | Email delivery powered by Google |
| Google, 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States | |
No comments:
Post a Comment