MicrosoftI have some questions on this very helpful article:
1. How / where can one download the enablement package MSU. Is this possible? Eventually why not?
2. With the great success of enablement packages since 1903 will WSUS offer them preferably?
What happens if a device group has approved the upgrade "ESD" and an enablement package.
3. The issue wroot and ajc196 discuss about WSUS OS version detection becomes more crucial every year.
The WAM PowerShell, paid and worth it subscription, offered by AJtek is able to fix this issue, and all other shortcomings with WSUS you can have from optimizing to database and cleanup etc.
Why WSUS team claims this OS version detection issue is by design, based on the wuengine while it is technically possible to fix using the OS build which is also part of the WSUS data we have.
Microsoft pleas to use WuFB which is great but limited by OS version.
It cannot manage old OS, it causes extra costs for reporting.
Server and Clients are managed in entire different scopes, including reporting.
Even Server 2016 is recognized as Windows 10.0
When Server 2022 LTSC is released I suspect that even this won't be recognized correctly.
4. Reports on twitter state that 21H1 still reports itself as OS Version 2009, only winver is not.
It would be expected it reports as 2103 or better 21H1 (even 2009 should report as 20H2).
Why the missing consistency?
Aside from WSUS this is another reporting issue.
https://twitter.com/SMSagentTrevor/status/1394869259742896130?s=19
Thank you Lurie to take it to an internal level. I wish this can be improved.
Microsoft should keep in mind that all the little things make it more difficult for SMB and even bigger customers as they don't usually read your overall great blogs and then are faced with problems and wish back older servicing models. I don't. Really don't.
Yet passion to details are important, imho.
