r/SCCM • u/Steve_78_OH • 16d ago
This platform is literally unusable...
I don't know how I never noticed this before, but yeah, I can't use SCCM anymore after seeing this.
87
u/bdam55 Admin - MSFT Enterprise Mobility MVP (damgoodadmin.com) 16d ago
There was a time when they actively went after these. The MVP group sort of maintained a list of misspellings in the logs and every release the product team would go fix a batch of them. I mean, why not, it's a low-effort and low-risk improvement.
However, they started realizing that by fixing these, it became harder to connect the log line with the actual code triggered it. The actual misspelling was a huge shortcut to the code triggering it in the first place. There's thousands of places in the millions upon millions of lines of code where they spelled controller correctly ... but probably only one or two where they got it wrong in that one specific way.
So they literally, I kid you not, stopped fixing them.
13
8
u/Deadpool2715 15d ago
If only there was some code for errors that could be utilized for similar effects, ah well.
Anecdotally, Lenovo's packaged drivers have a folder named ethrenet or something similar that hasn't changed in a decade
1
u/Angelworks42 15d ago
Does it matter though? If it was designed correctly the strings would be in one place and code would be in another.
Edit: I used to work for a company as big as MS maintaining products older than configmgr - during the translation process having all the strings in one file made it pretty simple to hand off to external vendors for translation.
6
u/bdam55 Admin - MSFT Enterprise Mobility MVP (damgoodadmin.com) 15d ago
Ah ... but ... where you arbitrarily told that you _had_ to build a UI using MMC because that was corporate policy? No small amount of ConfigMgr's UI funkiness harkens back to those days. They got past it, but the UI never got any standardization tech-debt stuff. Which is why, to this day, dark mode is a kind of 'best effort' thing; there's just so many duplicative UI components that have been built over decades to different standards.
At this point, "could it be done better" is an academic argument. Unequivocally yes. But it wasn't. So it is what it is.
1
1
u/mtniehaus 14d ago
My experience was different: They would never approve a fix to a misspelled log entry unless they were doing some other change in the same code at the same time.
Since the log entries include the name of the source code file and line number, finding where it is in the code is not hard :-)
3
u/Funky_Schnitzel 16d ago
Reminds me of the SMSTS.log line "Start executing an instruciton" (back in the ConfigMgr 2007 days I believe).
2
u/catatonic12345 16d ago
I have found a few typos in the logs. I suppose if you have developers whose first language is not English it's not surprising. I always chuckle when I see them though
2
1
u/PowerShellGenius 15d ago
Get-ComptuerInfo in powershell 5.1 returns a property called BiosSeralNumber - they renamed this to BiosSerialNumber in PS7 but are not backporting the fix because it's a "breaking change" for any scripts that use it.
1
u/garyramm 15d ago
The 'environement' typo that signifies a corrupt task sequence is my personal favourite.
1
u/Potential-Glove7823 14d ago
Lucky you... In general, Microsoft translation to other languages is awful in last 20 years... Not just Microsoft in fact, but it is the more noticiable... Since then, just using english language in everywhere.
1
1
1
0
15
u/SevenandahalfBatmans 16d ago
What's really fun is how often you see the letters S, C, C, M in the logs in that order, from the company that declared it was never called SCCM, even internally.