When IT upgrades your instrument computer to W11
from Midnitte@beehaw.org to science_memes@mander.xyz on 11 Apr 16:37
https://beehaw.org/post/19384708
from Midnitte@beehaw.org to science_memes@mander.xyz on 11 Apr 16:37
https://beehaw.org/post/19384708
…and it turns out the vendor software isn’t just magically compatible
threaded - newest
Bad IT.
I remain thankful that Win11 is fussy about what it will install on. It needs at least:
Nixing any one of these will prevent an automatic upgrade, regardless of what group policy etc is in place. On a bunch of new Win10 builds from a while ago, I set them up as CSM/MBR and turned off the TPM in BIOS. Absolutely no chance of surprises there, even if I accidentally mark a machine for upgrade.
My network is small though, < 50 clients. When the bullet must be bit, I have the time to add the client to the ‘will upgrade’ AD group & go over things with the user(s). Then run through converting MBR to GPT, switching to UEFI and enabling the TPM again.
After that it takes care of itself and pulls down a load of QoL fixes post-upgrade.
I don’t think you’re the first nor will you be the last to be smacked with a driveby install that fucks up your equipment, sadly :(
Oh this was a deliberate upgrade - they just didn’t bother to ask/check if it was ok to just spontaneously do… 😞
That’s even worse. A an almost literal in-house driveby. It’s not bloody hard to see potential problems.
There’s a reason our PCB pick’n’place machines run Windows XP. And why that ‘Y2K compliant’ lathe over there is rocking '98. And why that tyre balancing machine at the shop over the road is in the same boat.
<img alt="" src="https://lemmy.zip/pictrs/image/b5d24fcd-b440-4878-b686-2cd6b433f2a3.webp">
Lmao too real.
Microsoft forced win11 on customers… we had 100+ pc’s upgrade on their own… gave f all about group policies.
Happy to not be a part of endpoint management team and to not care if my work pc is on wi10, win11 or anything else… I need a browser, an ide and a terminal to do my work
Same boat here.