Why won't it stay on? Tech Support |
- Why won't it stay on?
- Tech support / murder investigation
- Machine swallowed my card!
- Marines and computers don't mix well
- I finally found out what that blinking light means
- Tale of the phantom printer
- The Movie Party
- of focus
- Of course I remember...
| Posted: 16 Dec 2019 03:19 PM PST I had a couple of people suggest I should cross post my tech story to here. I edited it and shortened it to make it compliant with the rules on here. I hope you all enjoy! Strap yourselves in for the background. I am a woman in the tech field, and I just so happen to go by my last name. So, if you worked for the big box company but weren't in my store, you probably wouldn't know my gender. This is important. Due to circumstances, we ended up getting a new manager from another store out of state. His first day was on my day off. My co-workers told me he wanted two hours with each of us to learn our thoughts on diagnosing issues, and he was really eager to learn from us. He was especially interested to learn from the top tech who he heard about in his previous store, i.e. me. Until he learned I was a woman. I won't go into details here, but his face fell when he met me for the first time. He went from wanting to meet me, and learn from me, to ignoring me, or at the worst, talked down to me at times. Fun. Manager got it in his head that he was going to do something to prove he knew his stuff so when a customer came in wanting a custom built computer (which we weren't supposed to do) he grabbed the opportunity. He helped the guy pick out the parts, compare prices, and sold him the labor to put it all together. He also told me he was going to build it in my repair space (taking away a whole bench in the process from me), and he was doing this alone. And, I will never forget this: "Don't tell me how to do this. Let me learn." Oh. I will. Cue the manager putting this machine together on the bench behind me while I continued my work, just waiting. Manager has it together, hits the power switch. Computer turns on, then off. Then on, then off. He unplugs, then takes it apart. Then together again. Same result. As someone who put together a lot of computers, I know it's something to do with the processor right away based on the power cycle. Because a tech I know is good helped him install the parts, I know they are in right. I also glanced at the box which had the socket of the mobo listed as compatible. So, there's really only one option left after that. So, I can HEAR the wheels turning behind me, but he told me not to give him advice. So, I keep working with my mouth shut. Let him ask me when he's good and ready. He then believes parts must be bad. So, he has the customer send parts back, wait for the new ones, then try again. Same result. This continues for TWO MONTHS! He has the customer, who is obviously very angry at this point, send every. Single. Part. Back. Then have a whole new set of parts delivered. He has PROMISED the customer this is the last time. This time it will work. He definitely knows what he is doing! The day arrives where the customer brings in the parts. The manager is there. I am there. I stop repairing computers as he puts the final part in, and I lean against my bench to watch what is about to happen. How could I not? He hits the power. Same. Result. He is FURIOUS. He throws the screw driver across the bench, denting the wall, and curses so loudly I am sure a customer heard. He puts his hands on either side of the machine, head down, shoulders slumped, utterly defeated. In a quiet... oh so quiet voice he asks, " OP... what's wrong with it?" Me: "The motherboard and processor aren't compatible without a bios update." Manager: "How long have you known this?" Me: "Since you first turned it on two months ago." He turns. He is red in the face. Veins are bulging, and I'm pretty sure he thought about decking me for a second before composing himself with a very, very deep breath. Manager: "Why didn't you say anything then?" Me, smiling sweetly: "Because you told me not to, and to let you learn. So... have you learned?" He stormed off, and out of the store. He ended up taking two personal days, and I ended up building a new PC that actually worked without having to ship in a new CPU just to install the update. Customer was cool once I explained everything. I showed them how I cable managed to allow the best cooling and looks with their clear case. It became the legendary story to tell all new techs, not only as a cautionary tale (Always ask for help!) but also a fun jab at management who seldom understand tech. [link] [comments]  |
| Tech support / murder investigation Posted: 16 Dec 2019 03:59 PM PST Ok Everyone, This one is from way back in the day. I'm doing my normal rotation on Saturday morning tech support at a medium size dialup ISP. This would be back in 1998. We had a few thousand subscribers, and I had been working there in one capacity or another since 95. We didn't have a really deep bench of helpdesk staff, so 2 of us would rotate through on the weekends. Since it was just 8 AM to noon on Saturday, and closed on Sundays (yes, that long ago many ISPs didn't have 24x7 helpdesks). Anyway, I have tons of good stories, but this is about the only really haunting one, that still gets me all this time later. We have a receptionist/triage front desk person, and the two of us taking helpdesks calls in the back office, no other staff on hand that day. A call comes in for some help with a PC issue, and the girl at the front desk gives me a heads-up that it might not be internet related. Policy is that we support the customer's modem and dialup/internet software, no general PC support. People had no boundaries back at that time, and they would hit you up for help with anything related to their computer, since helpdesk guys were "computer smart" and most computer manufacturers didn't do after business hours support. So I get the username for the account from the caller, and ask her to explain what issue she was having. She was pretty worked up, but it boiled down to her having done some hard drive cleanup, and after that the machine wouldn't boot anymore. I told her our policy about just supporting internet related issues, but took a shot at some of the basics. Do you have a dos boot disk? Do you have recovery media? Do you have any backups? The normal stuff you would do to see what options seemed within reach of what you can walk someone through over the phone that has very little comfort with technology. It wasn't looking good, no boot disks or backups, didn't want to use recovery media because that meant a format and that they would lose everything already on the system. As we talk she gets more and more upset. "He's going to be so mad when he gets home" ramping up to "oh no, he's going to kill me!". This was a time when even a cheap computer would be $2000 new, and that was pre 2000's dollars, so a lot at the time. This situation was not all that new to me, although more often this kind of thing came from teenage boys that broke the family computer, rather than the wife/girlfriend. With nothing else to really attempt over the phone I tell her that her best bet would be to take it in to a local computer store and have them check it out. She's not happy, but I don't have anything else to try, and I had been on for 20-30 minutes and had other calls piling up on me to return. I give her the name of a decent computer repair company in her town (she's about an hour's drive from my office), and I figure that's that. About 11:00 I am starting to get restless and looking forward to being free until Monday. Just chit chatting with the other helpdesk guy and figured since it was looking really nice outside today that we wouldn't get too many more calls. The phones ring and the front desk rings my extension- "you took the call from {subscriber_login} earlier, didn't you?" I say,"Yes, I did, but couldn't get her PC booting, did she have another question?" That's when I hear, "No, it's the county sheriff's office and they want to talk to you." I was freaking out a little, but I don't think I did anything wrong. "Hello, this is {my_name} how can I help you?" He says, "We are investigating an incident, and I need to ask you a few questions. Your number was the last outgoing call made from this line." At this point the deputy asked me a bunch of questions about the call, I just give him the rundown of what I went through with the caller, and I did mention that the woman was very upset and kept saying that the guy that was on his way home was going to kill her. I think the deputy was pretty freaked out too, because near the end of my recollection he kind of blurts out "well he did kill her". At that point he just asked how best to follow up with me, and that was the last I heard about it. I never tried to get a newspaper from that town, and didn't look into it any more. I really didn't want to know any more about it. I still can't help thinking that if I had come up with a fix before the guy came home that the lady might still be alive. [link] [comments]  |
| Posted: 16 Dec 2019 08:26 AM PST So, some back story, I used to work tech support for a company that provided financial software. The software was installed locally and was authenticated using a Gemalto USB smart card reader. All users were issued with their own cards and a PIN. Fairly foolproof, or so I thought... I'd visited a site about 4hrs drive away a few months prior, installed the software and the smart cards on all the PCs that required them, and also hand delivered the pre-encoded smart cards (their PIN numbers were sent in the post separately, for security reasons). Completed the installs, then went to the manager of that team to distribute the smart cards and test them before I left the site. There were 8 cards but only 7 staff present. Manager said "Oh, that's Sylvia's card, she's off on long term sick, if you leave that with me, we'll sort her out when she gets back." No problem, that's me all done. I pack up my kit and leave. Fast forward about 3 months. I get a call from the manager on site that I spoke to on my last visit. "Hi, Sylvia is back and she's having some issues with her card and software. Can I patch her through to you." "Yes, sure." "Hi, it's Sylvia here. I'm afraid the machine has swallowed my card!" "Hello Sylvia, when you say swallowed, what exactly do you mean?" "Well, I started the software and it asked me to insert my card into the reader, so I did, and now I can't get it back out." "Right, so just to clarify, is it stuck in the reader? What happens when you try to pull it out?" "Oh, I can't see it at all, it's disappeared into the machine completely. I can't see a cancel button anywhere to return it." Now just to clarify, these Gemalto readers are small handheld units that you slot the business end of a smart card into, with a digital display and a PIN code pad. The card only goes in about an inch at most and it's pretty much physically impossible for a card to become stuck. Still, it was possible that the card may have been cracked or damaged and it may have gotten stuck in the reader so I ask her to package the reader back up and send it back to us. "OK, how do I get the reader out?" "Just follow the wire and it should just unplug from the back of your PC." "I can't see any wire, do I need to take the PC apart?" Starting to lose patience at this stage. "No, it should just be on the desk under your monitor, follow the wire back to the back of your PC and pull it out." "Oh wait, you mean this thing that looks like a calculator?" "That's it." "OK I've unplugged it, can't see the card anywhere." "It should be sticking out of the top. The card only goes in about an inch." "Ah, is this where I was supposed to put my card?" "Yes, where did you think it was meant to go?" "The slot on the front of the computer that looks like the one on the cashpoint." "Riiiight.. Can you put your boss back on the phone?" Explain to the boss that it sounds like she's shoved her smart card into one of the drives on her PC. He says he'll get his internal IT team to come down and take a look. He rings me back later that day to confirm that they found her smart card wedged inside the floppy disk drive. They eventually managed to get it out with some pliers, and as a precaution they left the drive out of her PC, and replaced it with a blanking plate to prevent further incidents. [link] [comments]  |
| Marines and computers don't mix well Posted: 16 Dec 2019 12:48 PM PST Saw a post here about a Marine bringing in a broken computer to a store and it reminded me of when I was a Marine doing IT/Network Admin/Server Admin work. I was gonna comment on that post but I think making its own post would be better, so here's the comment that never was. Former Marine checking in here. Angry Marines + Computers = lying Marines and broken computers. I used to be an 0651 and it was labeled as "Cyber network Operator" and on paper we were supposed to be network/server admins. In reality if it looked like a computer we were in charge of it, broken Blackberry? Our fault. Broken desk phone? Our fault. Broken Radio? Our fault . There are job fields in charge of that but we were the ones usually called first. Anyways this reminds me of the time I had a Major call in about "his laptop keyboard not working properly." We went to go check it out and sure enough the keyboard had keys sticking. A quick glance at his desk showed coffee stains all over it, so we asked "Sir did you spill coffee on the laptop? The keys are sticking as if something was spilled on it." "No I did not spill anything on it. I'm the only one that uses that machine and I came back from the gym and when I came back it was like this." (Back story: This was on deployment, we were living on a Navy ship and Officers had their own room, so it was common for us to make visits to their room to work on laptops). We took the laptop over to the maintenance dudes who fixed hardware for us and sure enough there was coffee all over the inside of the machine ( it was an old Lenovo thinkbook). We ended up giving him a replacement laptop with a weatherproof keyboard (Called them G-tacs, think of the 'military laptops' you see on movies) which was way worse than the one he was using but it wouldn't break if you spilled something on it. He asked if we had the others to give out and told him we didn't (we did). He never made calls back to us for the rest of the booze cruise. Lessons learned: Marines don't like to admit when they're wrong (especially if they have any rank on them) and don't lie to the people trying to help you. [link] [comments]  |
| I finally found out what that blinking light means Posted: 16 Dec 2019 05:31 AM PST So I landed a computer tech job, fresh out of the military. I had been trained in electronics, and my preference was a computer-related job. This happened in the late 1990s. It turned out that I was to be the only person in the entire IT department. I would report directly to the manager of this facility. My job duties included technical support, computer installations, and some telephone systems management. Except for one little fact, this sounds a lot like other IT jobs in the 1990s… however, this was a call center. Back in the 1990s, a call center was all done primarily using POTS (plain old telephone service), WATS lines, and basic trunk lines. Ours was not a typical call center. We had all new equipment, and in fact, we had one of the largest and highest cost systems around at the time. The main phone system (PBX) was a Lucent Definity, a behemoth that was bolted to the floor in my new office. I think it took 3-phase power, I kid you not, and it had a massive 5000 VA UPS backing it up. Our Lucent or Avaya (formerly AT&T) Definity system was populated with a handful of ISDN-PRI lines in which each physical line into the PBX was capable of 23 simultaneous phone calls. We had at least 120 circuits. We also had a handful of POTS lines for good measure. There was a large number of station cards which allowed agents in the call center access to the phone network. Each station had a feature phone. We had voice mail on a server PC. We had direct-inward dialing, a phone tree, least call routing, and tons of programming options. I was told at some point that all of these components had cost the company roughly $600,000. That was before a companion office was opened up next door and began sharing the switch. I would get overtime pay to go next door and work for the other office. Both offices were in the same corporation, but entirely different branches. This was a large facility. It was actually an old Wal-Mart building that had been bought by our corporation due to its awesome location in the city. It was at a key point for telephone and data lines. There was actually a third office in the old Wal-Mart that held data servers. Ironically, they had a different phone PBX, but also better LANs, and much better connectivity to the Internet than we did. (SONET rings were new then, and they connected to one.) In case I've confused everyone, there was Account services in suite A, data servers in suite B, and a business office in suite C. When I got hired to the company, there was only about 10 call center agents and a bunch of managers. There was a lot of hiring going on. We were in the ramp-up stage to get the facility up and functioning. This was a satellite call center to the original one in another state, which had reached its capacity. The other one was in another time zone and hundreds of miles away. My boss, let's call her Sheri. Sheri was a corporate-ladder climber. She lived 200 miles away and commuted weekly to this job and rented an apartment nearby. Sheri had learned her skills at the primary call center. She was pretty good at a lot of things, but technically, she was lacking. So she had tired of making mistakes and being unable to troubleshoot stupid computer problems. Hence, me. Young geek to the rescue!! Wish me luck! Because this was quite an elaborate setup. We had hundreds of stations, each with a Windows 95-capable PC that was going to be installed with DOS programs. And all of the managers needed Windows 95 setup. All of the setup was done by me. These were Pentium 120 MHz systems or something. Why the computers? I'm glad you asked. First off, each agent received a PC for running a black screen, old text application. A server in my office room ran OS/2. I'll bet it's been a long time since you heard of OS/2! The app that ran on the OS/2 PC was a call center app. It was hooked to the Definity and to our TCP/IP LAN. Everything was running 3Com network cards at 10 Mbps. While the folks in the server department next door boasted of 100 Mbps speeds, my office ceiling was where every station's wires terminated to a 10 Mbps switch. The server guys next door also mentioned having IP phones, a phenomenon which would make our call center's setup obsolete! Ok, so this is how it worked. Every time a call came in to our call center, the Definity would find an agent. If an agent answered the incoming call, she was supposed to say, "Hello, this is XXXX Account Services, blah blah, blah." But as soon as the incoming caller's number was interpreted, her screen would automatically show a matching account name and number. We had 800 service and ANI, which is better than caller ID. This sped things up for inbound callers. Meanwhile, the server would also dial out and connect people the same way, and it was fast. "Hello, can I speak to ….. [screen pops up with the correct name] … Joe Ford, please." To the agents, they just heard a beep, saw their screen pop, and they would hear the 1990s classic greeting, "Hello?" This was a billing call center, so we were collecting accounts receivable. We had a PA system that blasted mind-numbing white noise the entire day on the "floor" which made me retire to my even noisier "office." So after a lot of initial setup work and learning my job, we had a few technical glitches. My boss was normally the one fixing things at first, but I eventually learned some things about this complicated call center. Basically, a lot of things were taken care of remotely. We had a few modems, and the other call center tech (salaried) would run reports and make changes. I noticed that my pay was pretty low, so I continued acting like an hourly guy and not over-performing. But I am a pretty observant kind of guy, and I ended up getting someone in big trouble once. Or twice. Sheri had baby-sat this facility for the entire construction phase. She talked about running all of the wires in conduit… the Cat 3 and 5 cables that went all over the facility. She had not only seen the cables run, but had coaxed them and helped them along. She told me that the air conditioner in my office cost $100,000. I hated that stupid thing. It was the noisiest piece of junk ever, sitting on the ceiling blasting 50 degree air into the room no matter the weather. The server room, my office, was set at 68, but I occasionally shut it off because I was freezing. It didn't take long to heat up that room, I might add. Well, one bored day, I decided to finally take stock of some things. I went over and looked at the phone system and all of its wires. I looked at the UPS. It was an APC Smart-UPS brand, top of the line. It had a bunch of lights on it, one of which was always blinking. There were a lot of other rack-mount UPSs in the room, but they didn't blink. Hmm. This was a time of the nascent Internet, the World Wide Web. I think I was able to download the manual and print it out, just to see what it was supposed to do. I was pretty green, and I wasn't familiar with UPS systems. Well, it turned out that the blinking light meant that the input voltage was high. Always. Hmm. That's odd. So me being the hourly guy, and this not being in my job description, I went home at 5:00 like always. Back at home, though, I decided to dig out my volt meter and get to the bottom of this. The next day, I went around to the back of our (now) $800,000 Definity PBX. There was an unused 120 VAC receptacle back there. The voltage tested high. That's really odd. Why is the voltage 138 Volts? My next step was to go figure out this crazy building's electrical circuits. There was an electrical closet adjacent to the server room, across the wall behind the PBX. I wasn't allowed in there, but I peeked anyway. I started crawling all over the call center. The cubicles had 120 VAC to them, and I started to see gremlins there, like floating voltages. By then, my boss asked what the problem was and I told her that our Definity system's power was bad and I was suspicious of the rest of the building. After some tense moments of reflection, I told my boss that I wanted to talk to the electrician who wired the call center. He reluctantly came, and I showed him the problems. After some arguing with me, he left. Everything was fine. But after some reflection and system knowledge, I finally had an answer. Delving deep into the realms of serial ports and baud rates, VT100 terminals and odd cables, I found a way for the APC Smart-UPS to spit out some hard numbers. Its input voltage was running about 258 volts, past its 5% threshold, hence the flashing "bucking" LED on the front of the UPS. It had been blinking since the day I was hired, and presumably before. I now knew that the Definity's power outlet had high voltage because the electrician had tapped the transformer wrong. The improperly-tapped transformer only ran the phone PBX's 240 VAC outlet and the unused 120 VAC outlet. I told Sheri to call the electrician back to come re-tap the huge transformer in the room adjacent to the server room. The entire server room would need to be taken off line, so we would need his services after hours. I would have to stay late for overtime. Trust me, there wasn't anyone that was happy with my assessment. The other call center bosses would definitely want to know. Sheri's boss wasn't happy. So at the end of the work day, we got everything secured and ready. Everything had to be turned off, and I mean everything. It was eventually just me, Sheri, and the electrician. We had some tense words. But Sheri decided to try and leave the huge Definity turned on and run it off the UPS. Remember the 5 KVA UPS? Yeah, the one that may not have been charging for the last 6 months because it was constantly bucking a high input voltage? The blinking UPS? Against my better judgment, we left the stupid refrigerator-sized PBX turned on and allowed the UPS to BEEP us to insanity for the next… I don't know, but it seemed like 2 hours. Everything eventually came back up, but since Sheri wanted no overtime for me, I was told to come in late the following day. When I came into work the next day around 10, the systems were still down and Sheri was on the phone with the salaried tech support guy trying to figure out what needed to be turned on after everything had been secured. She'd frequently get completely confused like this, so I often could fix things in a few minutes to her chagrin mixed with happiness. It was probably just a mis-typed command or a switch left off. This was not the only boneheaded electric thing I found out at this wonderful job. Once we got more employees, there was the microwave incident. I was sent to investigate. It turned out that the electrician had thought that 2 massive industrial-grade microwaves could be on the same 20 amp breaker. When person A cooked his lunch and person B popped her popcorn, the breaker would trip. Solution: call the electrician to fix it for free again. IT department noob, 2 Electrician, 0 [link] [comments]  |
| Posted: 16 Dec 2019 06:18 AM PST Was recently graced with this subreddit and it made me reflect on some of the highlights of my career over the last few years. One story came to mind immediately. While working as an IT intern at my college a few years we were tasked with installing a new networked printer for the HR lady. Now to give some important pretext i want to emphasis how lazy this woman was, she was very large in size and i had almost never seen her out of her chair. Anyways, after installing the printer me and my fellow intern tested it and ensured everything was operational. We said our goodbyes and returned to our IT dungeon in the basement of a building across campus. Just when we got comfortable my phone started ringing, it was the HR lady. She explained that the printer we had just installed was not printing... my coworker and i were bewildered, we had tested it to ensure functionality. We walked back across campus and back to her cube in the office. She explained that she had sent a specific spreadsheet to the printer but it had not printed. I walk over to the printer, which is approximately 10-15 feet from her just outside her cubical, and immediately check connections, check for power, check for paper in the tray. Nothing. Everything looks good. Then i see it. The paper she had printed was right there in the completed tray..... the spreadsheet she said had not printed. We go over to her with the spreadsheet in hand not sure what to say. We asked her why she had said it didn't print to which she replied "i didn't hear the printer so i assumed the document didn't print"... she essentially sent us on an escapade across campus to take her printed document to her because she was to lazy to walk 10 or so feet to check for herself. TD;DR: HR Lady had a new printer installed, assumed that because she didn't hear a document print it hadn't printed. [link] [comments]  |
| Posted: 16 Dec 2019 07:49 AM PST Hi TFTS, It's been a while since I posted anything here, however I believe that this short story belongs here. Since we're in December, our Communication team wants to organize a "movie party" within the company, so basically they want to project the movie inside the main conference area, a large open space with a big screen. However, as you'll see, they didn't really had a clear idea of how to organize this... $Me => Myself $ComUser => A member of the Communication team, who is in charge of the event
This isn't the first time this user "organize" events like that, it's actually an habit with her. She sends a general email to inform that the event will take place, and only then will she start to think about how she (we) can make it work. [link] [comments]  |
| Posted: 16 Dec 2019 05:32 AM PST TL;DR when moving keep focus or you'll crash $me: obvious $application admin: too busy to be bothered $user: confused and angry by now $other_user: very helpful So, we have a ticket that keeps bouncing back. One day it is noticed solved, the next it opened again. Complaint on $application: "the application has generated an error and will now close." THE bog-standard error message of any .Net application. Yeehaw. To make matters worse, we are in the middle of a windows 10 migration. This is why, more worse, $application, a scanner frontend application needs to be upgraded. It scans then files documents into a CMS database. The connection to the database has been flakey at best in the first few incarnations of the new version. The scanners have some sort of add-in card that does image processing. Drivers for them have been developed until roughly halfway 2012, 3 years before Windows 10 was released. On top of all this, the location we're in is also complaining about slow connection to the central fileshares and the internet. To summarize: Flaky network OS upgrade Backend upgrade Client upgrade Application upgrade Ancient drivers Non-repeatable non-triggerable errors AKA: the perfect storm $me: "So, can you show me the error? I mean is it possible to trigger it somehow?" $user: (snippy) "Well no not really, otherwise I would tell you so." $me: "I see. This happens totally at random?" $user: "Yes, I already told the servicedesk a hundred times!" $me: "Can you show me your normal workflow? Maybe I notice something out of the ordinary." $user: "Fine. But this was already done before and then the error will not show."" $user starts clicking, scrolling, typing, and processes several documents from start to finish. No errors. I keep watching for maybe 10 minutes more but nope, not today. I start fooling around on another system with the same application to see if I can, blissfully ignorant, trigger the error. At some point I just open loads of other applications at random, click/move whatever until "the application has generated an error and will now close." Out of nowhere. Right. We are not chasing ghosts at least. I reset the workstation and start again, now taking better notice of what I am doing. And, I trigger it again. But how? I had focus on a spreadsheet, then moved my mouse then, ummm what? Rinse, repeat... $other_user walks in: "Yo $me, I may have found something" $me: "Oh please do tell" $other_user: "When you told me you were moving around with your mouse I remembered that only recently we got dual monitors." $me: "Oh, I wasn't briefed on that one" $other_user: "It looks like whenever $application window is not in focus and you scroll the wheel inside $application window, it crashes. So if you check an email, go back to the scan task queue list and scroll before clicking, it goes bang." Whoa, what?!? I try to replicate and indeed. Take focus to another application, move mouse back inside the area, scroll, crash. Wait a moment, it can't be. I open the application, no other applications open yet, click on the taskbar, move back, scroll... crash! $me: "Thank you sir, we have found a genuine bug in $application it seems." $user: "ok, but now what?" $me: "Workaround is making sure you click in $application before scrolling your mouse. A more permanent fix would be mice without scrollwheel." $user: "no thank you, we'll try to get used to this until they fix things." Here's the real kicker: there was already a hotfix available for this specific error in $application. But they did not want to patch $application because they feared it might "break something". Sure, like you could keep track of what breaks anywhere anyway with the project like this. Six months later, i haven't had any notice on the hotfix being implemented. [link] [comments]  |
| Posted: 16 Dec 2019 01:38 PM PST Just had a customer call in for tech support, now with out getting too detailed we sell approximately 20+ machines a month, to distributors, who then sell to end users. Guy had no idea what machine he had, so asked me if I (a tech, with no involvement in sales) remembered the machine we sold to one of our larger (they buy and sell multiple machines a month) distributors about 4 or 5 years ago. I am ashamed to admit I lol'ed at that question, and explained to the customer that I have nothing to do with sales so no, I wouldn't remember that sale. [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