I can't even
-
@gjacobse said in I can't even:
Users who can't do a proper shut down or restart of their computer. And then complaining that it's dog in winter slow.
Uptime was 22days (not the worst I've seen). Disk and Memory were at 100% usage before restart.....
We go from 22days to
47:13:50:12
-
@notverypunny said in I can't even:
With the W10 fast-boot / hybrid shutdown
I alway disabled that piece of shit functionality.
-
@jaredbusch said in I can't even:
@notverypunny said in I can't even:
With the W10 fast-boot / hybrid shutdown
I alway disabled that piece of shit functionality.
GPO'd that out of our network and suddenly a noticible chunk of stupid issues just stopped.
-
@nadnerb said in I can't even:
suddenly a noticible chunk of stupid issues just stopped.
Had the same thing happened when I added a 4am reboot to all users systems on Monday mornings.
-
@jaredbusch said in I can't even:
@nadnerb said in I can't even:
suddenly a noticible chunk of stupid issues just stopped.
Had the same thing happened when I added a 4am reboot to all users systems on Monday mornings.
I would like to add that. But so many of our staff won't be on network, on at that time. Nearly 85% of the PCs are laptops...
ETA:
That and a force kick from the Citrix and RDS servers at 1am daily. -
@gjacobse said in I can't even:
Users who can't do a proper shut down or restart of their computer. And then complaining that it's dog in winter slow.
Uptime was 22days (not the worst I've seen). Disk and Memory were at 100% usage before restart.....
This isn't always a user's fault.
F'n MS doesn't always do a full shutdown... in fact by default choosing shutdown does a fast shutdown... choosing reboot supposedly always does a full shutdown memory clear reboot whatever.. and windows resets the clock.
-
@dashrender said in I can't even:
@gjacobse said in I can't even:
Users who can't do a proper shut down or restart of their computer. And then complaining that it's dog in winter slow.
Uptime was 22days (not the worst I've seen). Disk and Memory were at 100% usage before restart.....
This isn't always a user's fault.
F'n MS doesn't always do a full shutdown... in fact by default choosing shutdown does a fast shutdown... choosing reboot supposedly always does a full shutdown memory clear reboot whatever.. and windows resets the clock.
I never, ever shut down anything. I either hibernate or reboot. Mostly hibernate, and reboot when not given the choice (updates). So for me, I don't care what shutdown does.
-
@obsolesce said in I can't even:
@dashrender said in I can't even:
@gjacobse said in I can't even:
Users who can't do a proper shut down or restart of their computer. And then complaining that it's dog in winter slow.
Uptime was 22days (not the worst I've seen). Disk and Memory were at 100% usage before restart.....
This isn't always a user's fault.
F'n MS doesn't always do a full shutdown... in fact by default choosing shutdown does a fast shutdown... choosing reboot supposedly always does a full shutdown memory clear reboot whatever.. and windows resets the clock.
I never, ever shut down anything. I either hibernate or reboot. Mostly hibernate, and reboot when not given the choice (updates). So for me, I don't care what shutdown does.
yeah - well users CLAIM that they choose reboot - yet when I look at how long since last reboot and it says 10+ days... something seems fishy.
-
Oh for FFS -
An alert has been fired on local host DOMAIN\COMPUTER regarding user myuser. A suspicious powershell script has been found in C:\Users\myuser\Desktop\Teams_ODfB.ps1. Please let us know if this is legitimate.This is the script
Start-Process -File "$($env:USERProfile)\AppData\Local\Microsoft\Teams\Update.exe" -ArgumentList '--processStart "Teams.exe"' Start-Process -FilePath "$env:LOCALAPPDATA\Microsoft\OneDrive\OneDrive.exe" -ArgumentList "/background"Which only starts Teams and ODfB.... Like.. JFC -
-
@gjacobse said in I can't even:
Oh for FFS -
An alert has been fired on local host DOMAIN\COMPUTER regarding user myuser. A suspicious powershell script has been found in C:\Users\myuser\Desktop\Teams_ODfB.ps1. Please let us know if this is legitimate.This is the script
Start-Process -File "$($env:USERProfile)\AppData\Local\Microsoft\Teams\Update.exe" -ArgumentList '--processStart "Teams.exe"' Start-Process -FilePath "$env:LOCALAPPDATA\Microsoft\OneDrive\OneDrive.exe" -ArgumentList "/background"Which only starts Teams and ODfB.... Like.. JFC -
Hey we don't know what it does we're just script kiddies out here, tell us if this is kosher, thanks!
-
oh FFS People!
Ah you don't unstand why your computer doesn't work right...
-
Taking from a previous post I made about a certain piece of equipment, I've just learned that the equipment must run Windows 7... because of course it does for legacy hardware.
-
@dustinb3403 said in I can't even:
Taking from a previous post I made about a certain piece of equipment, I've just learned that the equipment must run Windows 7... because of course it does for legacy hardware.
(Nuclear Eye Roll)
So know that pain. State Unemployment app was like that for scanning... Pain ITA. -
@gjacobse said in I can't even:
@dustinb3403 said in I can't even:
Taking from a previous post I made about a certain piece of equipment, I've just learned that the equipment must run Windows 7... because of course it does for legacy hardware.
(Nuclear Eye Roll)
So know that pain. State Unemployment app was like that for scanning... Pain ITA.I see your state unemployment app and raise you old-ass manufacturing equipment.... XP + serial ports... luckily it didn't fall to me to try to convince it to work on something newer, but still. one of the other guys was trying to get virtualized XP to talk nice to the gear with serial pass-through from vbox and couldn't convince things to play ball
-
@notverypunny said in I can't even:
@gjacobse said in I can't even:
@dustinb3403 said in I can't even:
Taking from a previous post I made about a certain piece of equipment, I've just learned that the equipment must run Windows 7... because of course it does for legacy hardware.
(Nuclear Eye Roll)
So know that pain. State Unemployment app was like that for scanning... Pain ITA.I see your state unemployment app and raise you old-ass manufacturing equipment.... XP + serial ports... luckily it didn't fall to me to try to convince it to work on something newer, but still. one of the other guys was trying to get virtualized XP to talk nice to the gear with serial pass-through from vbox and couldn't convince things to play ball
Yup
You win -
Oh FFS - Printers..... Toner.
-
@gjacobse said in I can't even:
Oh FFS - Printers..... Toner.
oh yeah... I just love those....
But hey.. I pass it along to management - who SHOULD know the salary difference between us and how simple it is to change out a toner... but, beyond that I just swap them...
I probably spend 50% or more of my day being bench....
-
@dashrender said in I can't even:
@gjacobse said in I can't even:
Oh FFS - Printers..... Toner.
oh yeah... I just love those....
But hey.. I pass it along to management - who SHOULD know the salary difference between us and how simple it is to change out a toner... but, beyond that I just swap them...
I probably spend 50% or more of my day being bench....
It's a mentality I would like to drive in.... but It was a process I knew about coming in - easy wins on the ticket count that certain others just didn't seem to care about. They'd ignore them routinely and part of the End User Frustration Factor (EUFF - is not a real term...) that I am working on reversing.
This a case of; Unknown printer of same model needed toner, but no known location. Checked printer, ok on toner, oh - here's the one that DOES need toner. Now the one that was fine is reporting it needs it... (eyeroll). And of course - IT URGENT!! Ugh,.. Print on the one down the hall,.. it's only 30-45 feet away.....
-
-
@jaredbusch said in I can't even:
You just made me log in for the first time in nearly a year just to thumbs down that assclown.
