TFTS Top Tales - November 2019 Tech Support

I work in a moderately-sized company where we have both internal employees and contractors at client sites. My job is about what you would expect: Fix issues as they come in, image and setup machines, and deal with standard BS mixed in. I've been there for a few years now and have some great stories. This one comes from the beginning of the year when a new user thought he could game the system for a better machine.

We're about a 50/50 split in PC and MacBooks. The machines that each user get are very similar in specs. The determination of what machine they get is based on the client and their position. Of course, PC users who don't like PC will do what they can to get a MacBook, only to get denied. We also get MacBook users who want upgrades to a newer system, citing "slow systems" and "needing the latest and greatest" to get their work done that magically gets done anyways.

That brings us to the user at the center of my story today. This happened just after Apple released the latest MacBook Pros with the atrocious touchbar and butterfly keyboard that I loathe. Naturally, we get a dozen or so requests the next day, all of which are marked with the same response:

"Request denied. Your machine is within our lifespan and still under warranty."

Both PC and Macs have a four year lifespan. When the lifespan expires, we upgrade as inventory allows.

Naturally, we get a few users who show up and try to plead their case in person and I turn them away.

Then I get our specific users who won't take no for an answer. We'll call him Mike.

Mike is a diva. Mike will always go to bat for himself, prop himself up, and complain every step of the way. He's a good developer, but he's not as good as he says, according to the guys who work with him. For some reason, Mike looked at that touchbar MacBook and determined he had to have it.

Mike puts in a ticket like everyone else, going on and on about how the touchbar functionality is suddenly vital to his job (Spoiler: It isn't) and he should be able to order one.

"Request denied. Your machine is within our lifespan and still under warranty."

Copy/Paste/Close.

Mike was in my office within ten minutes.

Mike: HelpDeskHero, why did you reject my ticket?

"Because your machine is only two years old. You don't need a new one."

Mike: But my machine has been really slow the last month and I think I should get an upgrade!

"Where's your ticket for the slow system?"

Mike: I'm too busy to deal with your ticketing system.

"Then I can't help you if I don't know there's a problem."

Mike stormed out of the office after more whining. I wasn't stupid, though: He wasn't going to give up. I went ahead and re-opened his request ticket and updated it with our "conversation" in my office. CYA, everyone.

A week later, a ticket comes in.

MacBook has a broken screen.

Yep, it was Mike's.

Mike included a picture of the broken screen in the ticket to help me out, of course. Sure enough, half the screen was unusable. Before I can even reach out to him, he's in my office with the MacBook. He's doing his best to look upset.

"So how did it break, Mike?"

Mike: "I'm not sure. I walked away for a little bit to use the bathroom, came back, and it was broken.

"Screens don't just blow up like this, Mike. Something had to have happened."

Mike: "I don't know what happened, HelpDeskHero!"

It wasn't my hill to die on just yet, but I told him to give me a bit to see what our AppleCare coverage included. He disappeared as I pulled it up, confirming that we got a discount on accidental damage but it wasn't fully covered. Just about everything else was. A quick call to Apple Enterprise Support confirmed it wasn't going to be cheap to replace, somewhere around $700 with our discount.

I go to my boss and tell him the whole situation. Of course, I can't prove he was the one that broke the screen and he's going to at least need a loaner before we decide what to do.

Boss: "What do we have in inventory?"

"We're pretty tight right now. Just a couple available. We have a pending quote for our re-stock with the new models."

Boss: "Do we have any other machines?"

Before I answered, it dawned on me: We still had older MacBooks. You know: The really fat ones with the disc drives still in them. The ones that, at this point, were about six years old and we kept for emergencies. Boss had the same idea and we both shared a laugh.

Boss: "Go get one of the fat Macs. Image that and don't tell him it's just a loaner. Let's let him sweat."

Mike came back not long after and I told him that we were still deciding what to do about his machine but that I would at least get him a loaner for the time being. Mike somehow twisted this around into hearing that he was getting a new machine.

Mike: "Okay, when you order a new one, I need more than 16 gigs of memory. I need 32 gigs and a stronger processor. Oh, and a 1 terabyte SSD. Thanks HelpDeskHero!"

Before I could even break the news to him, he was gone.

Oh HELL no. You did not just do that.

I took great pride in imaging that fat MacBook. I got everything ready for it and messaged him that the loaner was ready for pickup. He came upstairs....and almost fainted when he saw his temporary machine.

Mike: "I can't use this!"

"Yes you can. Log in."

Mike: "This machine is so old!"

"But it has a fresh image on it so it should run faster than your other machine, right?"

After going through his setup, he stormed out of the office. It wasn't long before his boss showed up wanting to know what the hell was going on. After a quick explanation and showing him the broken MacBook, he just sighed and shrugged. He asked if we were going to give him a new machine. I told him he wasn't getting rewarded for breaking a company asset, but I'd get a replacement that matched the one he broke. His boss agreed and let it die.

Apple got the repair done pretty fast and I messaged Mike to come pick it up. He was in my office so fast, ready to throw the fat MacBook out the window. Much to his disappointed (and my delight) he saw his old machine ready to go with a brand new screen.

Mike: "But, that's my old machine."

"Yes, Apple got the repair done pretty fast. All your data was saved so you can do a quick swap."

Mike: "But that's not what I requested!"

"And your request was denied. That didn't change."

Mike took the machine and left. I wiped the old machine and tucked it away.

A couple of weeks later, we got a shipment of the new MacBooks in but didn't tell anyone about it. Around that time, a ticket came in for new users to join the same team Mike was on.

I made sure those new users got two shiny new MacBooks, because I am that petty. After they went through their setup, they made their way to the area they worked.

A few minutes later, a ticket came in. Yes, it was from Mike.

"New employees have updated MacBooks on our team. I feel I should have one as well as a senior employee."

I shrugged.

"Request denied. Your machine is within our lifespan and still under warranty."

Copy/Paste/Close.

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

"Pressing the power button for users is now IT's responsibility"

Posted: 07 Dec 2019 07:52 AM PST

Hi, back with another story!

Wow, legitimately did not expect to still be in this job. I was so close to being out of here I could taste it - I had a soft verbal offer from a hiring manager for an information security position that, as of yesterday, HR informed me they chose to go with someone else at the last minute. Drat!

Oh well, my loss is your gain, here's a new story. Not a big drama-fest, but a groaner nonetheless.

Here we go!

Special parts are needed for several computer labs to be in compliance with federal requirements. I have to be a bit circumspect about this, but parts have been on order for weeks. They are to arrive the morning of the LAST POSSIBLE DAY we have to change over.

I have had 6 directors breathe down my neck for WEEKS about getting this done. I nearly memorized the tracking numbers at this point. After receiving the parts (and then taking them to said computer labs 7 buildings away) I informed, via email, all management that I was taking care of this VERY DIRE issue on the last possible day before compliance cutoff. Estimated 5 hours to run all necessary wiring across multiple labs.

So, picture me, on a ladder, running wiring in rafters, and hear radio chatter and "GOT HIM!" by security outside of the lab I was working in.

Yes, I was being escorted, once again, back to the head office, for a mysterious computer issue. It must be huge, apparently $site_director themselves commanded security to pull me away from this time-sensitive project.

20 minutes later, we arrive at the office in question.

$user: "Hi $pukeforest. My scanner doesn't work."

$me: presses power button, scanner starts up "try it now."

$user: skeptically feeds paper in, whiiiiirrr "Oh, that seems to have fixed it."

$me: clenching teeth "Please remember that little trick from now on."

I had a strongly-worded email in draft for $site_director, but I deleted it.

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

Do my job for me!

Posted: 08 Dec 2019 01:41 AM PST

A short one here today. At my job one of the ways users can submit tickets is via email. The first liners take it in turns to monitor the mailbox. This one such day it was me monitoring it. We got an email in from one of our users. You know that one user whose name you always see on tickets? And every time it's something stupidly simple? Yet somehow the tickets still ends up taking ages to resolve? The user with that name the entire desk knows?

Yeah it was that user.

Paraphrasing a bit she sent the following:

User: Please see the attached spreadsheet. I would like to remove the two links screenshotted below. Please remove these links without corrupting the document. Many thanks

(Yes she actually highlighted it in bold)

The user had included multiple screenshots of her selecting these links, including the dialogue box which gave the user the option to "Break Link". She had literally sent us a screenshot of her a button press away.

I replied:

Me: Hello User, please can you advise why you are unable to remove these yourself using the 'break link' button in the last screenshot?

I got the reply back:

User: I was worried about corrupting the document if I did that. Can you confirm that's safe for me to do

I... What?

So I told her she'd be fine. A couple of other things to note. The place we are contracted for uses a cloud storage system (which she had saved the document in) which saves the last 100 versions of any file stored in it. Even if she had corrupted it there would be nothing stopping her from going back to version from before she removed the links. She's also been in this position for well over a decade.

While speaking to my senior we really questioned why in 2019 we didn't treat good knowledge of IT the same way we treat a good grade in English or Mathematics when it came to filling job roles. Although I suppose if we did I could be out of a job.

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

Why does my document not scan

Posted: 07 Dec 2019 01:29 PM PST

Worked in a tech support job and had a client yell at me over the phone because she couldn't get a document to scan. When I figured out why, it took everything I had not to burst out laughing.

Background. I worked at an electronics store fixing and setting up computers for clients. Because I didn't work the front counter, I was tasked with answering the phone when calls transferred over. I was the lucky one who got this call.

Woman bought a brand new Sony Viao laptop, which at the time was probably our most expensive laptop. This was right when they added bluray readers to laptops. She explains to me she is a business owner and needs this document scanned, and sent before end of day or else.

I ask her what steps she takes. She puts the document to the scanner. Scanner is on, I asked. She hits scan, and nothing.

Ok. So, there's quite a few things it could be so I ask her to bring it all in. I agree that if I can't fix it within an hour we will refund everything without a restocking fee.

Now, the fun part.

She comes into the store with her laptop, the power cord, her document, and her attitude from the phone. But, I notice there is no scanner in sight. I figured even without the scanner, if the program as doing something odd, maybe I could sort it out. The conversation goes as follows:

Her: Are you OP from the phone? (I was the only female tech at the time, so it was pretty obvious)

Me: Yes. Let's get you to a desk with your items, and we'll get this sorted out.

Her: Good! Because I spent a lot of money in this store. I will never shop here again if you can't get it to work. I'm not an idiot! I know how these things work! And if you can't get it to work, I know you sold me a lemon and that's unacceptable.

She continued the whole way and during the whole time I was setting up her laptop. More of the same but it basically boiled down to, she might sue us for this. Alright.

Me: Alright, show me how you tried to scan it at home.

Her: I opened this! clicks the scan Selected the options like always and hit scan!

Then, I will never forget this. She held up the document. To. Her. Laptop. SCREEN.

It took every ounce of self control not to laugh at this. I knew it would only end poorly for all of us if I dare did it. My poor coworker, who was just out the corner of my eye, was losing it. He ran into the back room, knowing his outburst would reflect on me.

With an absolutely straight face, I nodded.

Me: Ok, I see what the issue is. You are missing a scanner.

Her: If I still needed that, WHY did it come with the software?

Me: It's a new feature in Windows so you don't have to spend time inserting a CD to install your scanners or printers if it's a common brand.

I went on to explain how it works, and why it works, all while maintaining my customer service face. I sold her a new all in one (printer/scanner/copier) and installed it for her. Then, scanned in the document. I also sold her an in-home training so she could learn more about her new products.

I held a straight face for an hour with this woman before I broke in the back room with my coworkers. One of the best stories from my time there.

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

Wind*wsNTplusplus

Posted: 07 Dec 2019 12:31 PM PST

TL;DR - Yay! Upgrades.

Another tale from when I was employed by XYZ Specialists. And since it's statistically likely that today is someone somewhere's birthday, I'll actually post an IT-related story to TFTS. While attempting to remove all other useful information.

[It's been quite a long time since this actually happened. I definitely remember the 'symptoms', I'm pretty d*mn clear on the OS functionality that caused them, and I'm 99% sure of the version numbers. And then I bowdlerised it for anonymity purposes. But anyone wishing to dispute the IT details can go ahead and do so in the comments.]

NewBruce stomped back into the office from the stairwell and slumped down at their desk with a despondant air.

"You'll never guess what OwnGoalIdiot had gone and done."

"Can't be worse that how they scr*wed over Oh's project last week," said someone, "That's gonna cost fifty grand to fix."

"It is. Way worse."

We should talk about OwnGoalIdiot. OwnGoalIdiot's parents should probably also talk about OwnGoalIdiot, and the eventual outcome of what I can only assume were their multiple and terrible failings in the upbringing stakes.

Many companies have an own-goal-idiot at some point. The clown who interferes in sh*t they don't understand and that they were told not to touch, inevitably causing more work for someone else, escalating costs, or the sudden loss of some previously profitable piece of business. We've all met them, the sales rep who sells the impossible, the 'tech' who disassembles calibrated equipment they don't understand to 'fix' a non-existant fault and leaves the expensive results strewn over a dozen benches, or the office manager who believes that people are best motivated when actively misinformed about what's going on, the scheduler who can't, etc. etc. The walking embodiment of accidental nuclear revenge.

Sadly, it's been my experience that such people are often employed.

Sorry, can't think what came over me there, I seem to have stopped halfway through a sentence for some reason. I'll try again.

Sadly, it's been my experience that such people are often employed in sales or customer-facing (in)capabilities, in the mistaken belief that this will somehow lessen the damage. If a position really had to be found, they should perhaps be destruct-testing the product's idiot-proofing in a padded, soundroof and locked room. Just sayin'.

Every workplace has one some time in its history, sometimes just before sliding into backruptcy, and OwnGoalIdiot was XYZ Specialist's. But they were in a class of their own. As a newly-recruited technical manager, OwnGoalIdiot training was included in my induction on the first day I was there. I don't mean I met OwnGoalIdiot, they were off causing chaos on another continent. I mean that they were a specific topic of discussion with pre-prepared slides, printed handouts and my boss and two of my new colleagues spent a good half hour telling me THE STORY of OwnGoalIdiot, summarising their past offences, emphasising that I would be sorting out some unnecessary sh*t sooner or later, and then telling me which official, unofficial and deniable resources were available to help me do that.

Everyone in the industry knew about OwnGoalIdiot, including all the regular/long-term customers. OwnGoalIdiot was employed as a senior sales rep - without portfolio - on an exceptionally f*cking generous basic package, and unfortunately they knew that there was basically zero chance they could ever be fired whatever they did, because #reasons. They could have stayed at home all day and done nothing, oh we wished it was so, but they didn't. Instead, they randomly involved themselves unasked-for in other peoples' sales/projects, f*cked them up completely, and then just wandered off to scr*w with something else. They also lied without hesitation or compunction, and often without apparent purpose, because their invulnerability meant that even blatant dishonesty had no consequencies whatsoever, someone else sorted out the mess, and OwnGoalIdiot just picked up their cheque at the end of the month.

As you can imagine, there is a LONG story as to the how and why of OwnGoalIdiot, and I"m not at liberty to tell it here. Or probably anywhere else. Because #reasons.

Back to the conversation. NewBruce is speaking again.

"OwnGoalIdiot took [customer] out to lunch last week and just randomly volunteered to *upgrade* the software spec on [massive project] from (windows) NT4 to (windows) NT5. Wrote up their own contract do it for a couple of grand, signed it with the customer in the f*cking restaurant. First we even knew about it was a week later when [branch office] got a fax from [customer] asking for confirmation it wouldn't affect delivery."

"No getting out of it?"

"No. It's basically valid in [customer]'s juristiction, and if we walk, we'll never be able to do business in [jurisdiction] again."

I need to interrupt newBruce's narative again, and talk a little bit more, and hopefully non-specifically, about XYZ Specialists. As I've mentioned before, they did specialist equipment for a particular industry, and the core range was all custom software running on custom hardware. But in more recent years they'd branched out, and also started doing control systems for similar things in our customers' related industrial activities. There might be a PC or PLC (or network of them) in the core of it, with a pile of extra hardware, some likely custom, and then software and commissioning. Not so much plug-and-play, as fly it in on a chartered transport, drag it onto site using whatever the local beasts of burden were, hook up the sensors and diesel generators, and now-you-can-play.

That kind of stuff tended to be (hideously) expensive and only got more so every time someone added a feature. [Massive project] was exactly one such, hadn't really had the wholehearted approval of the technical folks even when sales division first got the order, and was well into seven figures cost-wise. It was newBruce's problem, very definitely NOT their baby, and many months work for lot of seriously specialised people.

N*tworking and distributed control systems as concepts weren't anything like new when windows NT4 and later NT5 came out, but they were suddenly buzz-words. Everything had to use them whether it was a good idea or not. And the nature of [massive project]'s kind of system was that, since there was also this expensive hard/software just sitting out there in the middle of nowhere, people would want it to do double duty and control this activity too. And to keep an eye on that other thing. And... feature creep was definitely an issue, particularly as the hardware was often much closer to its capacity limits in those far-off days.

Even with what they'd said so far, newBruce was right to be tearing their hair out.

"But that stuff is half written, the production hardware's already in build, and NT5 isn't even released yet. It's only in Beta."

"Oh," says newBruce, "It's way worse than that."

"Go on."

A little more about [massive project] and it's ilk. Buried somewhere at the bottom of this pile of software "Honey-do's" was the core function that the thing was supposedly actually there for in the first place. What did XYZ Specialists specialise in? Controlling, in great detail, a particular kind of exothermic reaction.

If you don't happen to know what exothermic means, it's essentially just that a process gives out energy as it happens. Fire is a good example of an exothermic reaction, so are rocket engines and high explosives. Nuclear bombs are VERY exothermic indeed. On a common sense scale running nought to ten, exothermic things can range from a nice safe zero up to about fifteen million out of ten. Our stuff probably rated a solid eight when things were going nice and smoothly. That number went up if things because less smooth.

The thing with exothermic reactions, you see, is that they tend to be a bit, well, excitable. And once your reaction starts getting over excited, then they tend to start trying to escape from the boxes you were trying to keep them in. And if they escape, they can sometimes level up and make the transition into becoming an exothermic chain reaction. Chain reactions are interesting.

Define interesting?

The key to things not becoming interesting was to keep a nice close eye on them, and really understand the process. That way you can spot warning signs and hot spots before they turn into actual trouble. And I mean a close eye. You want to be checking in on things and tweaking the controls several hundred times a second. As a minimum.

These aren't things that go "bump" in the night.

These are things that go "Kerr-BOOM" as a matter of pressing urgency.

Irrespective of whether or not "Kerr-BOOM" was on your personal agenda for the next split-second.

Back to newBruce.

"(Windows) NT4 is deterministic. At least our current build (version) is. (Windows) NT5 (Beta) has interrupts."

"Go on, newBruce, you're teasing us."

IF $reader AND WorksInIT = TRUE, THEN probably skip NEXT-BIT and GOTO PRAECE

NEXT-BIT

Here's the non-IT explanation.

Everyone's heard of multi-tasking, where your computer/phone/iToaster does several things at once. Except that unless you're the USAF and currently using a massively parallel super-computer, they're basically lying to you.

[I'm excluding dedicated-function processors like graphics cards or comms chips in this, just talking about the main CPU here.]

What it actually does, is a little bit of this, and then a little bit of that, and then the other, and then back to doing 'this' again. Rinse and Repeat. From the outside it looks as though all the things are all moving along together, rather than in fits and starts, because the processor swaps between them many, many times a second. And thus, the user is fooled.

There are basically two ways of doing this :

1) Do a reasonable amount of task1, get to sensible stopping point, put everything away neatly. Move on to task2 - again, do that until some part of the task is 'done', tidy away, move onto task3, or back to task1 if there are only two. This is generally most efficient, and what real people do. For example, chop up all the onions you need, chuck them in the pan, wash you hands and start emptying the dishwasher, breaking off intermittently to stir the onions. Do as much dishwasher emptying as you have time for before touching the garlic, because you'll have to wash your hands again after that.

This, ladies and gentlemen, is cooperative multitasking. Tasks keep going until they've done their bit and 'voluntarily' release control, or a more important thing (an interrupt) needs doing and shouts them down.

2) The alternative is what happens if you're being micromanaged by a particularly psychotic boss. Clear your work area and do a little bit of task1 until boss rings the bell. Pack up task1 and put it in storage, wash your hands and unpack task2, then work on that from whatever state it's in until the stopwatch means boss can ring the bell again. Immediately pack task2 up, wash your hands and...

Welcome to preemptive multitasking.

You get the idea, not a good way for humans to do things, lots of unnecessary housekeeping to keep the tasks separate. Apply common sense and way #1 works fine. Unfortunately, computers don't have much common sense. In fact they're dumb as f*ck. But, they generally work really fast, and they will do exactly what you tell them to.

So for computer controls where anything is safety critical, or a millisecond's inattention will cause quality problems, or Kerr-BoOOM, preemptive multitasking is what you want.

Imagine trying to actually simultaneously grill food, change the baby and empty the Dys*n at the same time ("why?" doesn't matter, they just all have to be done right now. Your lifestyle choices are not my problem.). You need to look at the grill every few seconds to make sure it hasn't crisped too much, constantly go back to the baby to check it isn't in danger of rolling off the mat/table (even if you achieve nothing else while you're there.), while also running over to the cleaner as often as possible, and dealing with its incompatible kind of dirt. Cue lots and lots of hand washing, and picking things up/putting them down, you might actually spend most of your time doing that, but that's a sacrifice you have to make because there's only one of you and you can't afford to miss a trick with either the baby or the grill. Or accidentally combine the two.

(Windows) NT4 would do this if you set it up right, which is also called being 'deterministic'. The not-yet-launched NT5 theoretically scheduled itself this way, but in their wisdom M*cros*ft had added some features (interrupts) that couldn't be held down to a fixed time-table, and that meant you might not get back to the baby on schedule.

END NEXT-BIT

PRAECE

IF $reader AND LegacyNetworkAdmin =TRUE, THEN might-as-well GOTO FINALE

XYZ Specialists' standard build of NT4 was completely deterministic and could be relied upon to come back on schedule and process safety-critical control tasks whenever it was programmed to do so. So far so good. That exothermic stuff looks like it'll be staying in the box.

While NT5 was nominally 100% preemptive multitasking, at least the Beta versions we were dealing with at that point had certain kinds of interrupt that could jump the queue and make scheduled tasks wait, and those delays meant that the safety-critical control loops would be processed irregularly and have variable hysteresis and bandwidth. What's more, the irregular processing intervals meant that the loop calculations involved became more complicated (because of the odd intervals), which increased the processor overheads.

This is a bad thing if you're trying to stop a box full of exothermic from getting over excited and going Kerr-BOOM. Regularly scheduled examination of the box is your friend.

END PRAECE

FINALE

NT5 was fundamentally incompatible with the safety needs of the job. Oh, and not technically available to buy yet. And the project had already been mostly written to suit NT4. Just the extra licensing cost more than OwnGoalIdiot had charged [customer]. Cue a LOT of extra work for NewBruce. Delivery is delayed by months (with penalty payments alone that are probably more than even OwnGoalIdiot's annual salary.) and several VERY expensive specialists are contracted in to help us sort out the mess. M*cros*ft's newest product received several custom bolt-ons that amounted to a partial re-write at kernel level to make its Beta-version do the job in hand.

Total cost, to make the thing work like it was going to before OwnGoalIdiot wrote their own contract and sold [customer] a few thousand's worth of 'extras'?

Well over a million dollars.

And we didn't really want the $%&*ing job in the first place.

Even this wasn't enough to terminate OwnGoalIdiot's employment, and they just carried on as before. Serene and graceful like a Swan, with everyone else paddling like h*ll in the background.

It's all good fun until someone looses the other eye. I only lasted about another six months with XYZ Specialists Ltd, but then I still have both eyes, even if they're not what they once were.

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

Groupthink and Bad Tech Information

Posted: 07 Dec 2019 08:28 PM PST

I worked for a major OEM for 4 years, and my favorite callers were the military callers. They were used to following orders and the chain of command, so they would follow instructions to the letter. But part of their training suggested that if a problem surfaced before Windows loaded, it couldn't be a faulty driver. Logical, but incorrect. A sort of groupthink had set in. A common call type is that the hard drive(s) was/were no longer recognized - most of these systems had software RAID installed - and a common cause of this message is that the pre-OS IRST or IMSM driver had become buggy or corrupt. We would instruct them to reload the pre-OS driver and it would often solve the problem. "It happened before Windows loaded, it can't be a driver!" I heard this phrase so often that I decided to stop calling it a driver, so as I wouldn't hear the objection. I just called it "pre-OS software."

But you can never win in tech support. I instructed a non-military caller to install the pre-OS software. He said, "it's a driver!" Weary of the driver argument, I simply said "if that's what you want to call it." "That's because it's a driver! Get me your supervisor!" Collapses.

Every place I have ever worked had a bad piece of tech information inserted into training. Groupthink set in. And it was hard to convince the others that what we had been told was simply wrong.

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

Problem with storage space

Posted: 08 Dec 2019 12:08 AM PST

This morning, my neighbor called me over to fix her computer. She said that it won't allow her to save files and documents she was trying to download. I took a look at it and the C disk is almost full with only like 15 MB left. Not a big problem, I just run a disk clean up and then change the browser's file save location to disk D (which have about 43 GB left). After that, I told her everything should work now and she just need to open up D disk instead of C when she downloaded something. Lo and behold, she demands I changed everything back because she stored lots of work documents on C, I tried to explain to her but she refused to listen. In the end, I just switched back the file save location of her Goggle Chorme. Wonder how long that 3GB of space from C disk I've managed to free up will last her.

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

Breaking News

Tech Support

Sunday, December 8, 2019

TFTS Top Tales - November 2019 Tech Support

TFTS Top Tales - November 2019 Tech Support

TFTS TOP TALES - November 2019

No comments:

Post a Comment

Popular

Blog Archive

Fashion

Beauty

Travel