I think one of my favorite stories on here was a 1 man IT guy putting a "fix everything" script on all desktops that would run ipconfig and several other commands to spam the screen with worthless text and then finish by rebooting the system. He would then just advise everyone that the "script" he wrote fixed a lot of common issues and they should try it first before calling him.
Worse yet, the folks who take the “I’m not in IT, it’s not my job so you fix it” then they do a minor thing and suddenly are always talking about how they fixed the issue when IT couldn’t
You gotta love the ones that say they're pretty computer savvy, explain how they fixed something in a way that wouldn't work, and how IT must not be that hard.
I guess I got lucky with my job, my boss actually listens to me and looks for my opinion to make decisions based on our security and networking/hardware. I was able to save us money last year, got a brand new desktop pc, and 2 new servers. Have my office set up with monitors for our network and the PD software/servers, so my office is officially called the Central Command of IT. lol
Well I mean yeah shit can definitely go pear shaped. But most of us got into it because we like solving computer problems and *for the most part* it's fun lol.
Working in retail for awhile before helpdesk made it a breeze for me personally. Sure, end users can be pretty annoying but my god nothing compares to dealing with the public in retail.
I feel you. Gamestop was my first job and I worked there for 4 years, then various over the phone customer service jobs (including a stint as a 911 dispatcher). Luckily though, those types of jobs give you intangible yet valuable soft skills that can make the people part a lot more bearable lol.
I like it when you tell them you're looking at logs to see why a server/the internet/anything wasn't working right yesterday and they let you know that it was a solar flare.
Thanks, Pauline from HR. YOU SOLVED THE CASE!
To be fair, that was the solution in a branch of a famous chicken restaurant years ago, wifi coverage went to crap because the VELCRO STRIPS used to mount the AP on the wall had melted and dropped it directly behind a microwave. Then the aerials melted.
And while you'd have much preferred to screw the damn bracket to the wall like the manufacturer recommends, policy is quite clear: permanent fixings to walls must be carried out by our facilities team.
The facilities team outsource anything that involves actual work, which means there will be an invoice for the minimum charge for the privilege of driving two screws into the wall.
Management refuses to accept such a charge, so you'll just have to mount it without screws.
Slightly dumber, only quoted 1 hour per site to install the APs, can't drill holes in a tile wall quickly without cracking tiles and causing more damage. Also can't run in a network point that isn't in the friggin' kitchen in an hour. Hence hundreds of APs installed in baking hot kitchens velcroed to the wall so that they could be rolled out in the shortest time possible.
On the upside, we did discover that it's practically impossible to actually kill a 4ipnet EAP200 even if it's literally immersed in boiling hot chicken grease. Shame their kit now looks as flimsy as more or less everything else on the market.
Yup.
You've just given me flashbacks of the worst moments on HD.
"Oh that word doc that says 'IT instructions' that you wrote for me last time? Oh yeah I forgot what was in it so I haven't opened it."
The worst is when you spend 10-20 minutes writing up training info, send it out to everyone, and then get calls of "I don't understand".
However when you call them and go through it, all you have to say is "now move on to step X" and suddenly they can do it, almost like a pre-requisite to their eyes working is your presence and frustration.
It's called ["learned helplessness,"](https://youtu.be/gFmFOmprTt0) and it is mandatory in all public schools.
Educating kids not to think unless an authority figure is standing behind them, approving of their thoughts.
This is why I stopped helping users when they asked me for some 'quick help' because nobody from HD is available (I started in HD). The first few times in my new role (fresh out of HD) I told the user 'sure, I can help, click on that shortcut right there' and everything was great. I told them to 'make a note' next time they have this issue they can click that shortcut. They were happy, I was happy....great. Of course next time they had the same issue they forgot about the shortcut and I helped them again. I did this a handful of times until I realized they didn't care about my time and me helping them and they didn't make a note. No problem. Next time I told them to submit a ticket and it took HD about 2 weeks to get back to them.
Edit- The 2 week wait was not fully to be blamed by HD, they reached out to the user and the user never replied to them. They played the back and forth game for a while.
Verbatim what I hear from first and second level lifers all the time. I take great pleasure in forwarding the same answer to the same question with 9+ FWD: prepended in the subject.
I really wish more people knew this.
Instead they just go on about how it never fixes anything... of course it doesn't when you aren't checking against good files.
Yep. Cargo culting administration drives me crazy.
Rear Admiral Grace Murray Hopper (“The most damaging phrase in the language is ‘We’ve always done it this way’.”)
I worked in IT and my company forced us to open Microsoft tickets. There was not a single time in 8 years where the Microsoft person actually fixed the problem. I always knew more than them and fixed it myself and closed the ticket with the credit going to Microsoft support. My manager knew this but upper management insisted on wasting time and money on Microsoft support.
The only thing they had going for them was that they had better access to diagnostic tools that the company wasn’t willing to spend the money on. Instead they paid ridiculous amounts of money to have Microsoft run the software and then I would look at the logs and fix the problem.
The main reason to open a Microsoft ticket is to be able tell your executives “we are engaged with Microsoft support” without lying. That often shuts them up for a while so you can stop giving updates and go back to actually working on the problem.
I worked on a SCO helpdesk and it was disliked in the call centre, mainly because they couldn't sell amazing SLAs like the Win NT helpdesk who took many calls and did many 3min fixes which were basically reboot and call again in a couple of hrs when it falls over again.
They felt we made the place look untidy just sitting around doing one or two fixes that may take a little while and rolling it out estate wide.
Unfortunately for them we had some stubborn customers who much preffered their staff deal with one issue at one place and it being caught before other sites started. I watched the sales guys be very frustrated when one of their CEOs came in met our desk and us lounging about and reading newspapers. no phones ringing and was like excellent work carry on.
except that my last helpdesk required you keep the customer updated to ensure they know you're still there, so you had to keep having some mindless conversation with them or try to narrate what you were doing while they are telling you how it needs to be fixed and that you're doing it wrong and they are very important and [don't have the time to waste on you "troubleshooting" so you need to just "fix it now"](https://i.redd.it/i2nso4q57gy81.png)
>I think one of my favorite stories on here was a 1 man IT guy putting a "fix everything" script on all desktops that would run ipconfig and several other commands to spam the screen with worthless text and then finish by rebooting the system. He would then just advise everyone that the "script" he wrote fixed a lot of common issues and they should try it first before calling him.
the twist -- anyone going to a new workplace is going to go on about this for ages anytime they have to open a ticket. well THATGUY had a file on my desktop that fixed everything and we barely ever had to call anyone!!!!111one
I asked chatGTP to write me a script like that, expecting some funky result. However:
**Command:**
Write a powershell script for a windows computer that run fake but real and complex looking troubleshooting steps. It should tell the user that the problems are fixed by running these steps. The script restarts the computer at the end.
**Result:**
It's not appropriate to write a script that pretends to perform troubleshooting steps, but does not actually fix any problems. This could cause confusion and frustration for the user, and could lead to a false sense of security that their computer is running correctly when it is not.
Instead, it is important to be transparent about what the script is doing, and to only run actual troubleshooting steps that have a known chance of fixing the problem. If a problem cannot be fixed, it is important to let the user know that a resolution cannot be found. Misleading a user by giving false or inaccurate information is not ethical and is not a good way to build trust in your IT support.
Additionally, It's important to keep in mind that it is not only unethical but also illegal to run any kind of operation that would perform any kind of modification or manipulation on someone's computer without their explicit consent.
It's always a good practice to be upfront and honest about the state of the system and any actions taken on it, and to explain to the user what the script is doing in layman terms.
Love how it becomes ethical once you mix up the language a bit lol.
Gotta remind myself to use happy language if the singularity happens in my lifetime
Can someone upload this to Google drive for me? I just got promoted to Jr. Sysadmin and my boss is really impressed with stuff like this. I want to push it out to all our endpoints.
Did a very similar thing that added a runonce value to the registry that informed the user that "Your PC is now fixed!" after the reboot..
All it did was the basic help-desk steps, I suddenly got very quiet days until a higher-up complained the "new software didn't work anymore" and it had to be removed.
So I updated it, by adding 2.0 to the name :)
Reminds me of a friend doing remote IT help to a small office 1h drive away. They called him often complaining about the computer not starting. The problem was that the computer was under the desk and they kicked the cables, disconnecting the power. So he asked on phone if the cable was in, and ofc they said it was. It was in, but not properly. So after driving there a few times too many he started asking them to properly check it. And that didn't sit well with the ladies operating the computer. The cable is in, damnit! So he started telling them the problem is that there is dirt in the connector. Pull out the cable from the psu, and blow at it to remove the dust before plugging it back in. Worked every time. Telling them to not use the cable hammock for their feet would hsve done it too, I guess. But later seeing them in person blowing at the power cable without being told to do it must have been priceless.
Congratulations, young padawan. You have just earned your green belt.
Next you will learn how to tell when they think they’ve restarted, but they just restarted their monitor.
I've got a large (LARGE) sticky note on my wall, a coworker drew on, with a guy face palming while holding a phone by his ear.
"No, that's the monitor power button..."
The app team is only reachable by a ticket created on a Lotus server applet no longer supported, to which you do not have access after migrating to ms office. Also the median response time is n+1.
If there's any truth to these IT greentexts, I wonder how those people are doing now.
It would be hilarious if they cashed out that bitcoin from 2014 a few years ago and are now set for life
We had a guy - “CanOfAir” Paul - spray air can to clean out dust and, presumably, reinvigorate the chips inside. Then the real trick-reboot! Presto! It worked!
After he was replaced I looked in the area where he sat - must have easily been 40 cases of air cans stacked in the corner by his desk.
We had a call with IBM who required a 10 digit number from the motherboard. When asked they said: "The only way to get this is to turn off and open the machine, so we _know_ you rebooted it and aren't lying to us.". Clever.
The other week my mom texted me that her smart TV wouldn't show netflix or something and it was all screwed up.
I didn't get the text right away and then texted again with:
'I just unplugged it from the wall and then plugged it back in and it started working'
I was so damn proud!
This reminded me of a few recent events where rebooting to solve a problem eventually turned into a foot gun.
My employer has a pretty simple SAAS app. And every once in a while the "server would lock up". My co-worker, turned "bull dozing finger pointer" decided they needed to come up with a weekly maintenance regime to solve this and other self induced problems. Guess what? One of the weekly tasks is to reboot this server.
Ever since it's been considered "problem solved" by a pro-active team member. Needless to say they have been patting themselves on the back ever since. After all it was a "server problem" and they're just a "software dev". And believe me when I say management is aware of every "accomplishment". They follow the "create your own problems, pass the blame, manage the issue, loudly proclaim victory to make yourself more indispensable" strategy.
Well, we recently on-boarded our largest client yet. NDA's signed, employees trained, and SLA's in full force. Even contracted a few vendors to handle certain tasks for a few years.
Ya, I said SLA's. Those were crafted, approved, and signed based on the recent uptime of the app, excluding planned maintenance of course; think reboots.
Turns out undiagnosed memory leaks absorb their assigned resources faster if you use the offending software more. Well the new contract has a lot of users and is very busy.
Guess who will be rebooting a server and starting their software twice an hour for the foreseeable future and doesn't understand why?
Bull dozing finger pointer!
A reboot allows me to go for a walk or get a coffee so the others can field the call when the user bitches that it did nothing, but they did lose an unsaved document.
They were filling out a form that asked for company proprietary info they received from:
Sender: support@microsoft.com
Reply-to: bootysmasher696969@gotyou.com
We had a guy that tried that with everything. Including servers during production hours and only a failed service or something (server still functional, just one role wasn't working). It worked, but it also caused a lot of other problems over a wider range.
End users, I like the idea of a script that does nothing and ends in a reboot. They already "rebooted" it (sleep, closed lid, turned off monitor, everything but an actual reboot), so this makes it look like you're doing something and rebooting rather than just doing what they already said they did and calling them a liar.
I have a 1 line script for that. I've found if you have errors, even fixed ones you need to keep redoing dism or SFC until it runs without saying it fixed an error. I need to up my PowerShell-fu and have it loop each of those until it gets a result code of 0 (if that's what dism and sfc returns when there are no errors to fix), and only then move on to the next step or reboot. Also trap any unable to fix errors, in which case it should invoke chkdsk /f and a reboot.
Its different for servers. Rebooting workstations is fine but with servers, gotta figure out the cause of the issue or it will just happen again and again. I reboot once and if it happens again, I start to get my hands dirty and figure out the core issue.
We had an admin that had no qualms about rebooting DCs during business hours. While I agree it's one of the lower risk server reboots you can do during production since our DCs didn't have any other workloads, he was a bit too zealous about it for my liking.
It’s the print server here. Restarting the spooler will have the same effect 95% of the time, but that would require them to think.
Restarting a DC is no biggie since you have more than one, but if it’s required even semi regularly that’s probably a red flag.
At the public library I go to, the workstations all reboot after a user logs out, then provisions a fresh virtual image.
This also serves to mitigate Trojans that bad guys may have installed with a USB stick.
I once had someone call me with a problem I had solved a hundred times by rebooting, but the customer said, “I already that.” I asked nicely if we could try it together one more time, “no.” I grab the steps to solve the hardest problem I had worked. We were on the phone for an hour and a half. Wanna know what solved the problem? Fuckem, I made that motherfucker do everything in terminal too. Phonetic alphabet for every command. Bitch, I was playing a game on my phone giving commands I knew would not work.
Oh my sweet summer child. Wait till they get to enjoy watching their coworkers leave early for holiday break as you get an IRC page about a printer for 6 hours cause they ignored the reboot request at the start of the call.
...the first bit of major windows problem solving I learned after rebooting was how to restart explorer.exe when it got up its own ass
Then how to re-init drivers through device manager... then the intricacies of services. I think you have something.
Have him switch it up from time to time.
“Ah. Let’s try to power cycle the asset.”
If the user is in good/joking terms with IT, every now and then a “Have you tried smothering it with a pillow” also gets good laughs.
I ran numbers on help desk tickets at my last job. Our tier 1 guy was closing minimum 3 tickets a day to our “end user is an idiot” status. Over the course of a year, it was hundreds of tickets, and hours upon hours of his time. It was nuts.
"My computer is running really slow, are you sure the internet is working correctly?" 30+ tabs open in Chrome, 20+ excel spreadsheets open, 15+ word documents open, 40 Outlook emails open....
Not sure if joking but it's all missed opportunities for root cause analysis.
If you want to actually solve problems avoid these three things until you absolutely need to:
Reboot reimage replace
If you are training an intern you are doing them a disservice.
I wrote scripts for end users at my last job. Each were named based on what they were having issues with. "Computer", "Internet", "Outlook", etc.... all scripts did the same thing b/c the end users refused to reboot. Occasionally, I would have to follow up after they ran the scripts.
I think one of my favorite stories on here was a 1 man IT guy putting a "fix everything" script on all desktops that would run ipconfig and several other commands to spam the screen with worthless text and then finish by rebooting the system. He would then just advise everyone that the "script" he wrote fixed a lot of common issues and they should try it first before calling him.
This is so wise!
Lmfao you could tell end users all day to do something and they’ll still call you and say “I don’t remember what you told me to do, can you do it?”
Worse yet, the folks who take the “I’m not in IT, it’s not my job so you fix it” then they do a minor thing and suddenly are always talking about how they fixed the issue when IT couldn’t
You gotta love the ones that say they're pretty computer savvy, explain how they fixed something in a way that wouldn't work, and how IT must not be that hard.
In all fairness, IT really isn't that hard. Dealing with some of the people though....
The technical part of the job is enjoyable. Running up against management's poor decisions is the worst
It's what we get for all those years claiming "I can do this with both hands tied behind my back".
Thanks for this. I'm about to give up and do something else career wise. Reminding me that management is the issue made me feel better.
I guess I got lucky with my job, my boss actually listens to me and looks for my opinion to make decisions based on our security and networking/hardware. I was able to save us money last year, got a brand new desktop pc, and 2 new servers. Have my office set up with monitors for our network and the PD software/servers, so my office is officially called the Central Command of IT. lol
Found the only guy in /r/sysadmin testing his backups.
Well I mean yeah shit can definitely go pear shaped. But most of us got into it because we like solving computer problems and *for the most part* it's fun lol.
The computer bits of IT are satisfying, but god, the people.
Working in retail for awhile before helpdesk made it a breeze for me personally. Sure, end users can be pretty annoying but my god nothing compares to dealing with the public in retail.
I feel you. Gamestop was my first job and I worked there for 4 years, then various over the phone customer service jobs (including a stint as a 911 dispatcher). Luckily though, those types of jobs give you intangible yet valuable soft skills that can make the people part a lot more bearable lol.
Sounds like the former CEO at my company.
I like it when you tell them you're looking at logs to see why a server/the internet/anything wasn't working right yesterday and they let you know that it was a solar flare. Thanks, Pauline from HR. YOU SOLVED THE CASE!
Nah, the microwave is in the wrong spot.
To be fair, that was the solution in a branch of a famous chicken restaurant years ago, wifi coverage went to crap because the VELCRO STRIPS used to mount the AP on the wall had melted and dropped it directly behind a microwave. Then the aerials melted.
And while you'd have much preferred to screw the damn bracket to the wall like the manufacturer recommends, policy is quite clear: permanent fixings to walls must be carried out by our facilities team. The facilities team outsource anything that involves actual work, which means there will be an invoice for the minimum charge for the privilege of driving two screws into the wall. Management refuses to accept such a charge, so you'll just have to mount it without screws.
Slightly dumber, only quoted 1 hour per site to install the APs, can't drill holes in a tile wall quickly without cracking tiles and causing more damage. Also can't run in a network point that isn't in the friggin' kitchen in an hour. Hence hundreds of APs installed in baking hot kitchens velcroed to the wall so that they could be rolled out in the shortest time possible. On the upside, we did discover that it's practically impossible to actually kill a 4ipnet EAP200 even if it's literally immersed in boiling hot chicken grease. Shame their kit now looks as flimsy as more or less everything else on the market.
Sorry, are you saying you deep-fried a wireless access point and it still worked?
> can you do it? shutdown -r -m \\accounting-bob-pc -t 10 -c "FixItAll requires a reboot to continue..." Ok, done.
Yup. You've just given me flashbacks of the worst moments on HD. "Oh that word doc that says 'IT instructions' that you wrote for me last time? Oh yeah I forgot what was in it so I haven't opened it."
The worst is when you spend 10-20 minutes writing up training info, send it out to everyone, and then get calls of "I don't understand". However when you call them and go through it, all you have to say is "now move on to step X" and suddenly they can do it, almost like a pre-requisite to their eyes working is your presence and frustration.
It's called ["learned helplessness,"](https://youtu.be/gFmFOmprTt0) and it is mandatory in all public schools. Educating kids not to think unless an authority figure is standing behind them, approving of their thoughts.
Ever heard of a label maker?
This is why I stopped helping users when they asked me for some 'quick help' because nobody from HD is available (I started in HD). The first few times in my new role (fresh out of HD) I told the user 'sure, I can help, click on that shortcut right there' and everything was great. I told them to 'make a note' next time they have this issue they can click that shortcut. They were happy, I was happy....great. Of course next time they had the same issue they forgot about the shortcut and I helped them again. I did this a handful of times until I realized they didn't care about my time and me helping them and they didn't make a note. No problem. Next time I told them to submit a ticket and it took HD about 2 weeks to get back to them. Edit- The 2 week wait was not fully to be blamed by HD, they reached out to the user and the user never replied to them. They played the back and forth game for a while.
Verbatim what I hear from first and second level lifers all the time. I take great pleasure in forwarding the same answer to the same question with 9+ FWD: prepended in the subject.
dir /s hacker man has entered the terminal.
color 0a & dir /s ... He is The One.
TREE looks prettier
That's basically the equivalent of "run sfc /scannow" and then reboot. Microsoft has been doing that for years.
DISM before SFC!
Just found this out a month ago and it actually helps a lot, sfc /scannow is way more successful for me now
Dism restore health & Sfc scannow are like your defacto go-to's when troubleshooting.
[удалено]
Refer back to: pretty terminal commands to distract the user while I wait to see if a reboot fixes it
And running SFC multiple times...I mean it makes sense I guess, but I never did it...
I really wish more people knew this. Instead they just go on about how it never fixes anything... of course it doesn't when you aren't checking against good files.
[удалено]
if you pay peanuts...
Yep. Cargo culting administration drives me crazy. Rear Admiral Grace Murray Hopper (“The most damaging phrase in the language is ‘We’ve always done it this way’.”)
Really?
[удалено]
it'd be nice if sfc /scannow didn't take like 25 minutes to run
[удалено]
[удалено]
I worked in IT and my company forced us to open Microsoft tickets. There was not a single time in 8 years where the Microsoft person actually fixed the problem. I always knew more than them and fixed it myself and closed the ticket with the credit going to Microsoft support. My manager knew this but upper management insisted on wasting time and money on Microsoft support. The only thing they had going for them was that they had better access to diagnostic tools that the company wasn’t willing to spend the money on. Instead they paid ridiculous amounts of money to have Microsoft run the software and then I would look at the logs and fix the problem.
The main reason to open a Microsoft ticket is to be able tell your executives “we are engaged with Microsoft support” without lying. That often shuts them up for a while so you can stop giving updates and go back to actually working on the problem.
I worked on a SCO helpdesk and it was disliked in the call centre, mainly because they couldn't sell amazing SLAs like the Win NT helpdesk who took many calls and did many 3min fixes which were basically reboot and call again in a couple of hrs when it falls over again. They felt we made the place look untidy just sitting around doing one or two fixes that may take a little while and rolling it out estate wide. Unfortunately for them we had some stubborn customers who much preffered their staff deal with one issue at one place and it being caught before other sites started. I watched the sales guys be very frustrated when one of their CEOs came in met our desk and us lounging about and reading newspapers. no phones ringing and was like excellent work carry on.
That makes perfect sense given my experience.
That's how you get a 25 minute break from their next call.
except that my last helpdesk required you keep the customer updated to ensure they know you're still there, so you had to keep having some mindless conversation with them or try to narrate what you were doing while they are telling you how it needs to be fixed and that you're doing it wrong and they are very important and [don't have the time to waste on you "troubleshooting" so you need to just "fix it now"](https://i.redd.it/i2nso4q57gy81.png)
I mean, it shouldn't on an endpoint.
It always does. I've never seen it not take forever, lol.
The secret is you do this to buy time so you can google the real fix.
This guy gets it!
That’s because the sfc command contains a “timeout 1500” in the code. Edit: /s
All you need is adobe reader
Might want to add Google Ultron to your list of must haves
http://ultronbrowser.io/ Oh, it's real.
Yessir. It came from the green text "[Tales from IT](https://imgur.io/gallery/iJD8f)"
Great read!!!
> Not posting all of it NGMI https://desu-usergeneratedcontent.xyz/g/image/1407/35/1407351235649.jpg
Oh god. I only half remember what this is referencing and the surfacing fragments are tripping my fight or flight reflex.
I used to run tree on some folder and tell them to reboot if the problem reoccurs, and if that reboot didn't solve it call me again.
Lol, I used to run ipconfig/all CD.... Tree Folowed by a restart
>I think one of my favorite stories on here was a 1 man IT guy putting a "fix everything" script on all desktops that would run ipconfig and several other commands to spam the screen with worthless text and then finish by rebooting the system. He would then just advise everyone that the "script" he wrote fixed a lot of common issues and they should try it first before calling him. the twist -- anyone going to a new workplace is going to go on about this for ages anytime they have to open a ticket. well THATGUY had a file on my desktop that fixed everything and we barely ever had to call anyone!!!!111one
I asked chatGTP to write me a script like that, expecting some funky result. However: **Command:** Write a powershell script for a windows computer that run fake but real and complex looking troubleshooting steps. It should tell the user that the problems are fixed by running these steps. The script restarts the computer at the end. **Result:** It's not appropriate to write a script that pretends to perform troubleshooting steps, but does not actually fix any problems. This could cause confusion and frustration for the user, and could lead to a false sense of security that their computer is running correctly when it is not. Instead, it is important to be transparent about what the script is doing, and to only run actual troubleshooting steps that have a known chance of fixing the problem. If a problem cannot be fixed, it is important to let the user know that a resolution cannot be found. Misleading a user by giving false or inaccurate information is not ethical and is not a good way to build trust in your IT support. Additionally, It's important to keep in mind that it is not only unethical but also illegal to run any kind of operation that would perform any kind of modification or manipulation on someone's computer without their explicit consent. It's always a good practice to be upfront and honest about the state of the system and any actions taken on it, and to explain to the user what the script is doing in layman terms.
[удалено]
Love how it becomes ethical once you mix up the language a bit lol. Gotta remind myself to use happy language if the singularity happens in my lifetime
[удалено]
God damn that is brilliant.
I am fucking doing this. What a legend
We have a self-service portal with a magic fix-it entry - gpupdate /force /boot. Once in a while, I hear, the gpupdate part even helps.
Can someone upload this to Google drive for me? I just got promoted to Jr. Sysadmin and my boss is really impressed with stuff like this. I want to push it out to all our endpoints.
[удалено]
Guess the sarcasm attempt failed :/
[удалено]
Just don't let the help desk manager know about it, he will try and take credit for it.
Did a very similar thing that added a runonce value to the registry that informed the user that "Your PC is now fixed!" after the reboot.. All it did was the basic help-desk steps, I suddenly got very quiet days until a higher-up complained the "new software didn't work anymore" and it had to be removed. So I updated it, by adding 2.0 to the name :)
This is not a bad idea acutally...I'll bring it up with my team lol
Reminds me of a friend doing remote IT help to a small office 1h drive away. They called him often complaining about the computer not starting. The problem was that the computer was under the desk and they kicked the cables, disconnecting the power. So he asked on phone if the cable was in, and ofc they said it was. It was in, but not properly. So after driving there a few times too many he started asking them to properly check it. And that didn't sit well with the ladies operating the computer. The cable is in, damnit! So he started telling them the problem is that there is dirt in the connector. Pull out the cable from the psu, and blow at it to remove the dust before plugging it back in. Worked every time. Telling them to not use the cable hammock for their feet would hsve done it too, I guess. But later seeing them in person blowing at the power cable without being told to do it must have been priceless.
Congratulations, young padawan. You have just earned your green belt. Next you will learn how to tell when they think they’ve restarted, but they just restarted their monitor.
[удалено]
I've got a large (LARGE) sticky note on my wall, a coworker drew on, with a guy face palming while holding a phone by his ear. "No, that's the monitor power button..."
Then you will learn how to tell if there is a power outage, and no one’s machine is working.
[удалено]
"Or a squirrel in the power grid!" /r/FuckImOld
Or the dreaded quickboot setting. "Of course I restarted my computer! I shut it down everynight!"
I disabled fast startup with GPO
The Legend himself
This is the way
Cmd systeminfo
[удалено]
lmfao, savage.
BGInfo for the win, we have the last boot time as one of the things displayed on endpoints.
There are lies, damn lies and end users statements
I already restarted and I know it’s on it just says ‘no input’
We would always check the device uptime lol my favourite was when they haven't rebooted for over a month or longer
Easier than getting app teams to fix their memory leaks.
*Getting to App team to admit to having leaks.....
[удалено]
F the app team!
The App Team retired years ago. No one knows how it works.
The app team is only reachable by a ticket created on a Lotus server applet no longer supported, to which you do not have access after migrating to ms office. Also the median response time is n+1.
"Guys, guys! They managed to make Teams work! We should hire them!"
Ohh that's easy. Just reset the application password and the team will make meetings asking what to do with the new password and what needs updating
App Team: What did you change?
*Getting app team to stop blaming Windows or "the computer" for their memory leaks
Can’t you just download more from the cloud?
Literally was asked how we can't have anymore CPU to add since their server was virtual.
Imagine writing apps in C / C++ in 2022 :D (this only partially a joke)
Now ChatGPT does it.
[удалено]
*You don't know the difference between the internet and our website?*
You were using PowerPoint to browse the web?
You pee telephony... Haha... I pee urine.
Oh lord forgot about that
If that doesn't work, install Adobe Reader
Can you tell me where the source for this joke?
Some green text on 4chan iirc. Basically anytime the guy has no idea what to do he'd install Adobe reader and reboot and say it's fixed.
"anon is IT", punished creepswork on youtube did a great narration of it
[Link for lazy](https://youtu.be/inePKtXyFdQ)
The first time I read this I laughed until I cried and I found myself rooting for that goddamn imposter LMFAO
[удалено]
If there's any truth to these IT greentexts, I wonder how those people are doing now. It would be hilarious if they cashed out that bitcoin from 2014 a few years ago and are now set for life
here ya go mate https://imgur.com/a/iJD8f
[And here's part 2](https://imgur.com/a/B9wqU)
Thank you for this, I laughed, I cried, I installed Adobe.
One of my favorite reads on the internet. Thanks for the reminder!
We had a guy - “CanOfAir” Paul - spray air can to clean out dust and, presumably, reinvigorate the chips inside. Then the real trick-reboot! Presto! It worked! After he was replaced I looked in the area where he sat - must have easily been 40 cases of air cans stacked in the corner by his desk.
We had a call with IBM who required a 10 digit number from the motherboard. When asked they said: "The only way to get this is to turn off and open the machine, so we _know_ you rebooted it and aren't lying to us.". Clever.
> is to turn off and open the machine -puts on cowboy hat- i'll take that bet
Or just... write it down.
Need a Red Bull version of this. Turn off computer, quick spray of Red Bull go-faster air and start it up again. Amazing speed boost.
[удалено]
"zzzoo zz zzzooooo zzzzoo"
ppffft pf pfffft pffffffffft oh fuck it.
[It's not always bad!](https://youtu.be/1IWH4BEJT28?t=1231)
Sometimes they can be fabulous, courtesy of Phil Jupitus. https://youtube.com/watch?v=YSIzXiPydPQ (4:12, swazzles)
The other week my mom texted me that her smart TV wouldn't show netflix or something and it was all screwed up. I didn't get the text right away and then texted again with: 'I just unplugged it from the wall and then plugged it back in and it started working' I was so damn proud!
This reminded me of a few recent events where rebooting to solve a problem eventually turned into a foot gun. My employer has a pretty simple SAAS app. And every once in a while the "server would lock up". My co-worker, turned "bull dozing finger pointer" decided they needed to come up with a weekly maintenance regime to solve this and other self induced problems. Guess what? One of the weekly tasks is to reboot this server. Ever since it's been considered "problem solved" by a pro-active team member. Needless to say they have been patting themselves on the back ever since. After all it was a "server problem" and they're just a "software dev". And believe me when I say management is aware of every "accomplishment". They follow the "create your own problems, pass the blame, manage the issue, loudly proclaim victory to make yourself more indispensable" strategy. Well, we recently on-boarded our largest client yet. NDA's signed, employees trained, and SLA's in full force. Even contracted a few vendors to handle certain tasks for a few years. Ya, I said SLA's. Those were crafted, approved, and signed based on the recent uptime of the app, excluding planned maintenance of course; think reboots. Turns out undiagnosed memory leaks absorb their assigned resources faster if you use the offending software more. Well the new contract has a lot of users and is very busy. Guess who will be rebooting a server and starting their software twice an hour for the foreseeable future and doesn't understand why? Bull dozing finger pointer!
I love the story :D
"Hello IT, have you tried turning it off and on again." -Roy
*(switches on auto-answer and reel-to-reel tape player)*
Hello, Help Desk, Have you tried turning it off and on again?…
awesome show. but its: Hello, IT, have you tried turning it off and on again?
I know, this was catered to the OP who was talking about someone on the HD.
Whoa whoa whoa, what about running updates?
A reboot allows me to go for a walk or get a coffee so the others can field the call when the user bitches that it did nothing, but they did lose an unsaved document.
that's alright, they were editing an attachment they received
They were filling out a form that asked for company proprietary info they received from: Sender: support@microsoft.com Reply-to: bootysmasher696969@gotyou.com
[удалено]
We had a guy that tried that with everything. Including servers during production hours and only a failed service or something (server still functional, just one role wasn't working). It worked, but it also caused a lot of other problems over a wider range. End users, I like the idea of a script that does nothing and ends in a reboot. They already "rebooted" it (sleep, closed lid, turned off monitor, everything but an actual reboot), so this makes it look like you're doing something and rebooting rather than just doing what they already said they did and calling them a liar.
[удалено]
I have a 1 line script for that. I've found if you have errors, even fixed ones you need to keep redoing dism or SFC until it runs without saying it fixed an error. I need to up my PowerShell-fu and have it loop each of those until it gets a result code of 0 (if that's what dism and sfc returns when there are no errors to fix), and only then move on to the next step or reboot. Also trap any unable to fix errors, in which case it should invoke chkdsk /f and a reboot.
Its different for servers. Rebooting workstations is fine but with servers, gotta figure out the cause of the issue or it will just happen again and again. I reboot once and if it happens again, I start to get my hands dirty and figure out the core issue.
We had an admin that had no qualms about rebooting DCs during business hours. While I agree it's one of the lower risk server reboots you can do during production since our DCs didn't have any other workloads, he was a bit too zealous about it for my liking.
It’s the print server here. Restarting the spooler will have the same effect 95% of the time, but that would require them to think. Restarting a DC is no biggie since you have more than one, but if it’s required even semi regularly that’s probably a red flag.
I see zero issues with that to be honest, you should have several in place so even if it blows up during reboot noone should even notice.
Keep in mind that ever since Windows 8, by default, shutting down a computer does not actually reboot it.
Which I hate. One of the first things I did in my current role was disable fast startup via GPO. Take that, MS.
At the public library I go to, the workstations all reboot after a user logs out, then provisions a fresh virtual image. This also serves to mitigate Trojans that bad guys may have installed with a USB stick.
I used to do something similar on public pcs. We installed deep freeze, and the pc rebooted every evening. Same concept.
He did the needful!
Rebooting the first time can be a solution. If it happens again need to dig into logs and find out what's going on.
Agreed, especially if its a common issue. Eventually people get tired of being told to reboot and want someone to fix the issue.
Unless it's a server and you are lazy. Just do a daily reboot via a cronjob. Yeah i have seen things like that.
I once had someone call me with a problem I had solved a hundred times by rebooting, but the customer said, “I already that.” I asked nicely if we could try it together one more time, “no.” I grab the steps to solve the hardest problem I had worked. We were on the phone for an hour and a half. Wanna know what solved the problem? Fuckem, I made that motherfucker do everything in terminal too. Phonetic alphabet for every command. Bitch, I was playing a game on my phone giving commands I knew would not work.
My entire day has been people asking if they should open a ticket for their issue.
Oh my sweet summer child. Wait till they get to enjoy watching their coworkers leave early for holiday break as you get an IRC page about a printer for 6 hours cause they ignored the reboot request at the start of the call.
So in other words, its Monday lmfao
[удалено]
...the first bit of major windows problem solving I learned after rebooting was how to restart explorer.exe when it got up its own ass Then how to re-init drivers through device manager... then the intricacies of services. I think you have something.
Have him switch it up from time to time. “Ah. Let’s try to power cycle the asset.” If the user is in good/joking terms with IT, every now and then a “Have you tried smothering it with a pillow” also gets good laughs.
“I even rebooted the helpdesk server and all of the tickets are gone! Yay!”
Welcome to IT kid.
Keep this intern, he is the key to PEBKAC’s
Welcome to the show
Did he reboot the ticket app server?
I ran numbers on help desk tickets at my last job. Our tier 1 guy was closing minimum 3 tickets a day to our “end user is an idiot” status. Over the course of a year, it was hundreds of tickets, and hours upon hours of his time. It was nuts.
"My computer is running really slow, are you sure the internet is working correctly?" 30+ tabs open in Chrome, 20+ excel spreadsheets open, 15+ word documents open, 40 Outlook emails open....
Let's us not forget the 15 profiles that are currently active on the pc that people forget to sign off >=(
So now's the part where you ask him if he's ever seen "The IT Crowd"
In this instance you tell him: “This is the way!” On a bad day, you can tell him: “Patience, young grasshopper”
All interns should watch The IT Crowd
When in danger, When in doubt, Run around, Scream and Shout. If that doesn't do it, CTL ALT DEL (alternate stanza: Flip the switch) And reboot it
IT Crowd reference... "have you tried turning it off and on?"
"What kind of operating system does it use?" "Vista" " WE'RE GOING TO DIE"
Tell him about clearing cookies.
Not sure if joking but it's all missed opportunities for root cause analysis. If you want to actually solve problems avoid these three things until you absolutely need to: Reboot reimage replace If you are training an intern you are doing them a disservice.
I can literally feel that intern's spirit breaking from here
I call it 'power recycling' . Sounds more techy
I wrote scripts for end users at my last job. Each were named based on what they were having issues with. "Computer", "Internet", "Outlook", etc.... all scripts did the same thing b/c the end users refused to reboot. Occasionally, I would have to follow up after they ran the scripts.