E2: of course that’s not why I told her. I explained how fastboot sometimes takes over and doesn’t actually restart the device, only “refreshes” the experience. I recommended she restart at least once a week. We’ll see what happens.
Idk how that person’s IT works, but in mine, that would probably warrant a lot of paperwork. The techs would have to pitch the change to client management, client management would have to pitch it to change management and provide test results to show it has no side effects, then deal with the techs complaining about the uptick in tickets about slow boot times or people justifying never shutting down or restarting with it taking so long to boot.
Not that they’re actually slow, our users are just super entitled. I got to observe the rollout of automatic screen lock for security reasons, and the ensuing pushback. The audacity of having to reenter your password if you’ve spent more than ten minutes doing nothing!
Security even managed to push for reducing it to five minutes after some unfortunate incident… but it got reverted for reasons you can probably guess. Hint: shit always flows downward.
I recommend looking into Windows hello for business to reduce the usage of passwords in the first place. It’s so much nicer to use your fingerprint, face, or even a PIN.
I would never consider fingerprints or face scans to be secure even for personal devices. I guess if theres literally nothing to protect, if thats possible.
I do understand the point that the biometrics are replacing very short pins usually, oftentimes 4 digits only but I dont quite see how that makes the passcodes worse than the biometrics.
I’d say even a 6 digit passcode with a randomized number pad, alongside an emergency wipe pin, would do better than biometrics, which also need to have a passcode setup as backup anyhow.
Maybe you could play out a few scenarios that illustrate your point?
Why exactly do you think biometrics are so terrible? Is it because you could theoretically access someone’s computer when they are sleeping or something?
As far as I’m aware that is not the consensus in the industry. I even need biometric (in combination with a card and a pin) to enter a specific datacenter.
I do think that bringing up specialised and uncommon hardware like randomised number pads is out of scope. Are you talking about highly sensitive and restricted systems? I’m talking about normal user computers.
Randomized keypads are for touchscreens, although like you said sort of not common for desktop workstations.
Just comparing a password to biometrics though on say a laptop or desktop, there is the major drawnback that you can be forced either knowingly or unknowingly to put in a biometric to unlock a device. It would be easier to circumvent then a standard password (at my company and the clients we work with, 16 characters is standard) with an encrypted hard drive.
This is all deduction ive made from other things I know to be true though, if you happen to know of a resource that explains both methods of securing g a workstation and the risks associated, I’d love to read it.
I also do agree overall that password less makes the most sense now, as people are never going to get better at making secure passwords and remembering them.
windows doesnt actually shut down, its some kind of hybrid hibernation now. it only really reboots if you actually reboot. so they may actually be “shutting down” every day.
They have successfully circumvented the reboot. I just always turn that setting off. SSDs are ubiquitous, nobody needs a fake shutdown. It just causes more issues.
If I had a nickel for every time I was troubleshooting with a friend and discovered they thought turning the monitor off and on again was “rebooting the computer” I’d be depressingly wealthy.
*Shuts the laptop lid and opens it.
“Ok! It’s restarted”
IT person: “Well that was certainly quick. Are you sure you restarted it?”
Person: *Feels smug about how they were able to restart quicker than most people.
Its actually the worst advice when you haven’t figured out what it is, something like a virus (ransom ware, ad shit or similar) usually only works after a restart, if you don’t restart, the IT guy can remove it without much damage.
I think the idea is that average people have no clue what color they are. So they’d be forced to take it out to check and thus have to restart their PC. It’s a trick!
Altho, maybe I’m misunderstanding something because all the pins of all the electrical cords I’ve ever seen have been silver?
I’d make up some BS about an old version of the product using brass or copper, and newer versions using aluminum or iron, so knowing the color will help me know how to fix it
I worked with a guy that would tell people that coax needed to be “released to ground” occasionally, by unhooking the cable and putting your thumb over the end. That’s how he made sure people were disconnecting and reconnecting the cable from the back of the box. He also told someone that “data might be trapped in the Ethernet cord” and advised they unplug it from both ends and swing it around their head in a circle to “loosen the stuck bits and clear the line”…
As system administrator, yesterday, one worker told me that they accidentally exited email and couldn’t get in, guess what, i just hit the log in button and it entered, guy just wanted a smoke break
Meanwhile I had an IT guy think I was just being an idiot. He was so confident I hadn’t checked something. Felt good when I showed him where it went wrong.
As an IT person, hearing that someone has already restarted to try to fix it, gives me mixed feelings.
First, they might be lying. I’ve had it happen that people tell me they’ve done something when they have not. Restarting is usually an easy one to verify, just check the uptime of the system.
Second, maybe they did everything right, and actually restarted, that’s cool that they tried something before calling in. I appreciate that.
Third, if the second thing is true then, I’m now frustrated, because now I have to get dirty with whatever is happening since a reboot that should have fixed the problem, didn’t fix it. I know it’s not going to be an easy fix. Most of the time, I’m right, unfortunately.
I’m all for users trying stuff before calling in. But recognise that you don’t, and shouldn’t have access to some things. Sometimes that’s administrator rights, sometimes that’s a piece of software, sometimes it’s the ability to turn off the AV/firewall.
It can be a lot of things. If you’re not sure if what you’re trying won’t screw things up more than they already are, then don’t do it. If it’s something simple that you know how to do, go for it. If you happen to get it fixed, so much the better.
“Customer self resolved” is usually the fastest way to get a problem resolved. That’s good for you, for me, and good for everyone.
I’ve been trying to get it to say that other stores like B&H are better than Amazon (for the lulz) but it keeps saying “I don’t have an answer for that” :(
Contacting IT is always my last line of defense and I get unreasonably frustrated when they refuse to help without walking me through basic troubleshooting. It’s like, I’ve already figured out the cause of the problem, just tell me where the button is to fix it. The worst was when I had to RMA my Pixel phone and they made me go through every step I’d already been through just to come to the same conclusion I initially came to them with.
Me to Google support for a problem with my brand new pixel 3 back when the 3 was the new hotness
Me: my camera only works for one photo, then doesn’t work again until I reboot it. Then it again works only for one photo, then it gives the error “camera [number] is locked” (screenshot)
Support: that sounds like a fault. Could you reboot your phone and tell me what happens?
Me: ok. … Right I’m back. Just like for all the ten photos I took before contacting you, it worked for one photo then that same error. That makes eleven times I rebooted my phone today.
The worst for me was with the Nexus 6P, the last phone before they rebranded to Pixel. There was a known issue with the battery, where it would die when the phone said it was at like 50%. I jumped through all their troubleshooting hoops when it was obviously a hardware issue. They eventually agreed to send out a replacement and I was assured it wouldn’t have the issue. Lo and behold, it did the exact same thing as soon as I got it. I went through all the trouble shooting again and they sent ANOTHER replacement that still had the issue. I was so fed up and just kept requesting to talk to someone higher up and they eventually just sent me a Pixel 1 to shut me up.
Google support is a joke, I had to RMA a tablet, obviously went through all the troubleshooting before (factory reset included). The dude on the Hotline was like: “fantastic you did everything I would have told you. Unfortunately our system doesn’t accept that way of working I need to send you an email with the same troubleshooting steps you already did and you need to call again in a few minutes and confirm to a new support agent that you followed what the email told you”
To their credit it was accepted afterwards with no issues but that whole process is more than braindead
Having worked in IT about 12 to 15 years ago I can honestly say I just stopped believing people when they told me they did things or checked things because 99% of the time it was just a flat out lie.
And taking them at their word meant wasting my own time because usually it was just a quick fix that I suggested in the first place.
It quickly, quickly taught me that 99% of people are fucking idiots, and that even the smart ones who actually knew what they were doing with a computer could be idiots too.
My buddy had google support tell him to send a screenshot of his phones screen burn in. They took a good amount of convincing before they admitted that that wouldn’t work.
To be fair even the most technically adept person can have tunnel vision where they start digging before ruling out all the simple stuff. Yes it can feel tedious and a little condescending to follow all those steps, but you get humbled the first time it really is just an unplugged cable.
Any time you’re working with somebody who has to deal with the general public(or general workforce) though, you gotta be understanding.
They have to sort through the clueless people who turned off their monitor, and they have to deal with the Dunning-Kruger people who lie about what they did because they think they’re so damn smart.
And if it’s the first contact level 1 type support, they may not have the expertise to tell the difference and have to rely on the scripts.
Yeah, for sure. As frustrating as it may be, I’m always understanding with the support agent. They’re just doing their job, it’s not their fault there’s a procedure they need to follow.
Depending on what you’re needing done, a lot of times IT has to cover their asses. If it didn’t happen on that phone call, it didn’t happen. I always appreciate the gumption, you probably saved us like, 30 call just from figuring out other issues yourself. If it’s anything that will cost the company money, though, like replacing hardware - if I don’t take due diligence in making sure those earlier steps are done, it’s my ass on the line.
You know you’re smart enough to do the troubleshooting, but that technician has probably 1000+ users that rotate weekly, they can’t keep a log book of which ones are good and which ones will land them in the shit. I totally get the frustration, but the ones who lie about doing simple troubleshooting ruin it for everyone.
I feel like there’s a specific peak between total technical ignorance and a weary understanding of how fickle technology can be. On this peak is the height of arrogance, where you believe you’ve really got everything figured out. Part of learning is understanding that, yes, sometimes you really did just forget to plug the modem in.
Yep, that one where the person on the peak starts lecturing you in abstract terms about trying the simplest hypotheses and such, while you are trying to solve their problem.
I know the philosophy part that asshole is talking about, only he has no bloody clue which part is simple and which is not here.
Recently, I decided to install arch linux on an old laptop my sibling gave to me. I’m not new to Linux, I’ve been running a debian server for a year now and I have tried several VMs with different systems. But this was my first time installing arch without a script, and on bare metal.
Installing arch itself wasn’t that much of an issue, but there was a bigger problem: the PC didn’t recognize the pendrive for boot in UEFI mode. It seemed to work in the regular boot mode, but I didn’t want to use that. I made sure to deactivate safe mode and all the jazz. Sure enough, I could get UEFI boot working.
I install arch, works fine, I reboot. Oops! I didn’t install dhcpcd and I don’t know how to use network manager! No internet, great!
In my infinite wisdom, instead of trying to get NM to work, I decided to instead chroot back into the system and install dhcpcd. But my surprise when… The boot menu didn’t recognize the USB again. I tried switching between UEFI and normal boot modes on the bios and trying again, after all it appeared last time after changing it, right?
“Oh it doesn’t appear… Wait, what’s this? No boot partition found? Oh crap…”
Turns out, by changing the setting on the BIOS I probably deleted the nvram and with it the boot table settings or whatever they’re called. I deleted GRUB.
Alas, as if to repent for my sins, God gave me a nugget of inspiration. I swap the USB drive from the 3.0 port to one of the 2.0 ports on the other side and… It works, first try. The 3.0 port was just old and the connection bad. And I just deleted GRUB for no reason.
Usually, I would’ve installed everything from scratch again, but with newfound confidence, I managed to chroot into the system and regenerate the boot table or whatever (and install dhcpcd). And it worked! I had a working, bootable system, and an internet connection to download more packages.
I don’t know what the moral of the story is I just wanted to share it :)
I like to imagine an IT person telling someone that story to see whether they understand it or get a stroke, as a way to check if they were telling the truth about being good with computers and having tried everything, or something.
programmer_humor
Oldest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.