The LED is blinking but it seems fine otherwise Tech Support |
- The LED is blinking but it seems fine otherwise
- A wrong number and a very happy customer
- Unofficial USPS IT guy 5
- That's not my job, that's morning shift's job
| The LED is blinking but it seems fine otherwise Posted: 17 Aug 2019 06:41 PM PDT First time poster, blah blah blah. I work for an Internet/TV provider and manage, among other things, the TV backend and client software. Received a ticket from the inventory people saying that the set top boxes being tested (returned from customer, tested before being refurbished) have their front LEDs blinking non-stop, but otherwise seem okay, asking what to do. Confused, I make the trip to see it myself. Normally a continuous flashing LED means it's still booting so that doesn't make sense to me. On arrival I see that the description is correct, but I misunderstood the meaning of blinking. The blinking was rapid, indicating that it's receiving continuous remote control signals. All our remote are IR-based (not radio) which should make finding the source straight-forward. I walk up to the bench confirm my hypothesis: putting my hand in front of the box stops the signal and removing it resumes the signal. So now I slowly use my whole body to try blocking the signal while also pulling up the camera app on my phone in case I need it. Upon the flashing LEDs returning to solid (to the surprise of those working on the floor), I rotate 180 degrees and look at what's right in front of me... A large transparent plastic container full of remotes haphazardly placed within it sitting on a shelf. I don't even need my phone to find the exact culprit remote - it's the one on the bottom. The ticket creator is following me and, upon seeing the glowing buttons on the remote control, understands what is happening. Ticket closed. Cleaning up the remotes is their problem. [link] [comments]  |
| A wrong number and a very happy customer Posted: 17 Aug 2019 08:37 PM PDT Yet another riveting (?) tale from my days as hospital IT. This particular Friday was glacially slow, so I was almost relieved when the phone rang.
The elevator panels went to 8 (thanks, eBay spares) but we only had 4 floors. For a second, I thought she'd lost her mind. Then, I realized we had no red tower
This poor lady sounds totally defeated. I feel even worse for her because I'm going to have to ruin her day. I'll have tell her I can't help her. See, we were contractually PROHIBITED from providing IT support to all Affiliate Hospitals because reasons. I took a quick glance around. No one is in earshot. YOLO time.
For context, most hospitals have some kind of incident management software. They use it to document customer complaints, slip and falls, medication errors…it's basically ticketing software for medical oopsies. They take it very seriously and run a lot of reports out of it. I'm chuckling inside. At first, I doubted if I could help her at all, but I was trained as the local guru on it. I've spent so much time with the incident reporting system that I almost know more about it than the admins at Corporate IT. I gotchu fam.
I remoted to her PC and had her show me what it was doing. Same dumb .NET error I fought every day, plus an INI file error from being uninstalled wrong in the past. Ten second fix, hopefully. Today I get to be someone's hero. So, I ran my .NET script, deleted the INI, and had her try it again. My hero status is in jeopardy...it's still not working. Time for the hop-on-one-foot-and-bark dance that this hot garbage requires. Reset IE, disk cleanup, clear cookies, reboot PC, re-run the scripts that Corporate IT doesn't know I have. If this doesn't fix it, I got nothing. Ritual dance complete, we try it again.
That call still puts a smile on my face. [link] [comments]  |
| Posted: 18 Aug 2019 02:50 AM PDT This could also fall under idontworkhere or notmyjob. My friend was asked to help set up a new computer in a post office. He was sitting at a desk about 6 feet behind the counter. After unboxing the computer. He was hooking cords when he heard someone clear her throat. Looking up, a woman was looking at him. The postmaster was busy helping someone else but intervened. He here for the computer, I can help you in a second. She turned, I need this sent out. Like I said, I'll help you in a second. I just have to help him first (motioning to the man in front of her) The man walked out, the woman sent out her package and the postmaster apologized. Told him he just needs to set it up, update, and he's done. The setup was easy, the update would take time. And he sat in a chair waiting. After a little while, the postmaster said she needed to grab the mail from the blue box outside the door. There hadn't been anyone in a where so she figured it would be a good time. There were 2 way to enter the building. It seemed as the postmaster walked out 1 door. A woman walked in the other. She walked up to the counter. Impatiently cleared her throat and glared at my friend. Sorry, she'll be right in to help you. I saw her outside. Why don't you help me? (So much attitude) I can't. I'm just here to hook up the computer. You work here. You're wearing a post office ID.( hanging from his shirt) That's to prove I'm allowed to be back here. I don't have access to those computers, to sell you things. (Pointing to the computers at the counter) Well, I need stamps Do you have the login code for those computers?(he has no idea if he needed login code or not) No Well neither do I. So you are going to have to wait. Seconds later the postmaster walked up to help her. After she left my friend asked if it was him or was everyone obnoxious. She just smiled, try being here all day. Shortly after, the computer was done and he went home. Note this will be my late post for a while. I received messages that I posted too many, too fast so I'm taking a step back to work on other projects. [link] [comments]  |
| That's not my job, that's morning shift's job Posted: 18 Aug 2019 04:51 AM PDT So I worked in tech support for 6 months. I have fortunately quit that job. We provided tech support for a software that is used in call centers and tech support. This happened during an evening shift of mine, around 6-7 pm (it was 24x7 support). So this client had an issue. We provided a short term solution, but it needed to be fixed with a patch update for a proper fix. Depending on the issue, we provide various patch updates. So in this case 4-5 patches needed to be updated. The size for them was around 1-2 GB. The patch update required atleast 1 hour downtime. But we asked clients for 2 as a buffer in case anything went wrong. So what we did was, we uploaded the patches on WeTransfer, where you upload files, it provides you with a link. Anyone can down the files by clicking on the link. The thing is, the link is valid for only 2 days. So I am talking with this customer. Me - C, so I am providing you with this link. You need to download the files through this link, and just copy them onto your server. Then we will update the patches on x date. C: The update will be performed in morning time not evening time. So, that's not my job, that's the morning shift's job. Me: (ugh) Fine, sir can you please tell your morning shift, to download and copy the files, otherwise we will not be able to do it. C: I will do it. The update was scheduled on x date. I provided the customer with the link 8-10 days before that. Update day: Person who will perform the activity (A): Sir where are the patch files? Different person on client side (Cx): what files? We weren't provided with any files. A: Sir, the link is on the ticket. Cx: but I wasn't informed of it. A calls me over and asks me about this. I tell him I had informed C about this A: Sir, your coworker C was informed about it. Cx: but why didn't you inform me, as I would be your PoC today. A: we were also never informed who would be the PoC. Anyway let's download the files. A tries to download the file but the link has expired because 7 days have passed. A and Cx get into an argument again. After a pretty useless argument, A downloads the patch files on his computer from our repository, then upload it to wetransfer, provide Cx with the link. Cx then downloads it on his system and then copy them on to the server. A then finally updates all the patches on the system. Overall the time taken was around 2-2.5 hours with 1-1.5 hours of downtime. Cx was fucking mad because we took so long and didn't provide the link beforehand (yes he said that). As if that wasn't enough, he then proceeded to write a feedback on the ticket itself about the same things. We had to explain everything to our department head. [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