MicrosoftAs of 20220210 this comment's original post has been shadowbanned.
20220720 3 times as of now. Replacing stuff with [bad word] now.
It will be reposted every time this happens, tracking the mods abuse.
- - -
Want to hear the [bad word] reality?
WSUS sucks. It sucks soooo [bad word] hard.
How can an OS update like a cumul take 10+ minutes on current hardware? And then STILL take quite a while to finish while booting.
We barely have any devices >3y age, and even the most current ones (Lenovo L15 G2 AMD) will take ages.
Why? Because the [bad word] procedure basically ignores the blazing fast disk and a single [bad word] thread is used to do whatever it is the patch wants to do.
Add hundreds of MB of patch size on top of that and everyone with a [bad word] internet line is [bad word].
How would you even expect these machines to be patched in time?
How do you expect their "experience" with a degraded internet line (dl of patch data hogs the bits) is during the dl?
How much productivity do you think they have when an already subpar line is being clogged by a [bad word] update mechanism?
Then, the uninstall of said patches.
"Uninstall updates" gets you to this [bad word] W95 menu that has been bugged as long as I am [bad word] using Windows.
Bunch of stuff always missing. Sorting doesn't work as a normal person with a brain would expect it to. System sometimes even clearly lies to you with InstalledOn data.
wusa silent has been dead for ages, I finally had to figure out a PS way that can actually use the KB number because you simply take your time after having [bad word] VPN for so [bad word] many people.
Nothing gets tested since you killed your QA department.
[bad word] your telemetry. No seriously. What do you think it will tell you?
A bug isn't measured by statistics, it's measured by a goddamn skilled technician realizing if it is relevant or not.
VPN unsuccessful after patch X? Oh well just a little more telemetry data in that regard, if you even track that.
Access doesn't open a shared DB file? As if you would even telemetry that.
lsass cycle, HyperV, ReFs...tell me how you noticed that with telemetry? Do at least the first two not trigger some kind of results where someone would take a look? If not, how [bad word] hard do you suck at coding telemetry? Is "telemetry" maybe a "ping `telhome.microsoft.com with a specific data size every X minutes" and nothing more?
[bad word]-fix-rollouts: It's amazing how far off you can be from an everyday admin's needs.
Access megabug: Kill off the thing with an auto-rollout. Meeeh, they can apply the fix manually if it isn't O365 (fix = manual patch download).
VPN megabug: Kill off the thing with an auto-rollout. Meeeh, they can apply the fix manually (fix = optional update).
And you can't figure out why people hate you? Are you [bad word] serious?
Now to one other commenter.
When I read [bad word] like this I seriously could go bonkers.
WHICH MEANS YOU HAVE A GODDAMN MEGA ULTRA HARDCORE RESPONSIBILITY!
YOU KILLED SO MANY HOURS IN OUR COMPANY ALONE IN DEC AND JANUARY!!
It's time you can get sued for clearly negligent testing. 100% serious here.
You won't learn it any other way, this is clear.
You are currently just as bad as Blizzard is after having been [bad word] by corporate [bad word] from Activision.
Just that one is "just" affecting the gaming world and the other is the foundation for the whole [bad word] global workforce.
Are you seriously trying to tell anyone that the recent [bad word] are "edge cases"? [uh, sarcasm which we could ban, uhhhh]
Without a QA team proper enough for the scale of MS it definitely is.
The downplay of this alone 😂😂😂😂 clown.
How about we talk about RDPs losing printers on every logon because [bad word] customers? (no we are not debugging this here, the policies are fine, you can find many people with this exact issue)
How about we talk about clearly functional equipment like Brother label printers being converted to e-waste just cause you couldn't be bothered to accept that nobody cares for signed drivers.
How about we talk about print server just selecting WSD for me when I want to map a new printer, because "we know better"? (port first then printer, yes, great success).
How about we talk about the endless series of testing required to get printing working properly for everyone? Oh this month it's the PCL4 driver, next month it's PCL6, now it's not working with either, now it's....I have zero trust in the whole printing subsystem by now. I bet it's from the NT era.
I could go on for ages with mega widespread [bad word] that never gets fixed.
Telemetry isn't the answer.
Properly testing your [bad word] again is!!
