Forum Discussion
Understanding Windows Update Services product categories for Windows Server 2022 and Azure Stack HCI
The new Server 2022 LTSC has arrived. And it is a great release. Some customers still struggle to find their SA benefits and ISOs / licenses and RDSH licenses in VLSC, but it is officially released....
After further discussion with Artem, it is more understandable why this category.
While we agree the name is not a nice one. There are some facts that make the decision more understandable.Windows Server 2019 did not only include Windows Server 2019 but also Windows Hyper-V 2019, as well as Windows Server version 1809 (SAC). All shared the binary same patches.
So, the category name in the past was also misleading.This is the best explanation why the new name and no single category for Windows Server 2022 and a separate category for Azure Stack HCI OS 21H2.
Thank you Artem for taking the time on this debate.
p.s. if you want to learn more about Artem Pronichkin here is a nice interview and links.
I really like his blogpost on his webpage about the history and PowerShell transition of sconfig. Worth reading.
Sorry but it still looks like insane to me.
A sub-category "Windows Server 2022" within "Windows Server", for people using Windows Server but not Azure Stack HCI (so no need to download then bloat WSUS database with it).
A sub-category called "Azure Stack HCI 21H2" for people using Azure Stack 21H2 and not older versions or Windows Server 2022, same reasons.
I read Artem reasons twice, and they still make no sense to me. Maybe I'm an idiot.
A sub-category "Windows Server 2022" within "Windows Server", for people using Windows Server but not Azure Stack HCI (so no need to download then bloat WSUS database with it).
A sub-category called "Azure Stack HCI 21H2" for people using Azure Stack 21H2 and not older versions or Windows Server 2022, same reasons.
I read Artem reasons twice, and they still make no sense to me. Maybe I'm an idiot.
It is not logic for a non developer in fact. You see in the screenshot that the analogy why they chose the new name does funnily not apply for drivers 🙂
However Windows Server 2022 and Azure Stack HCI 21H2 do share the same updates. So you do not bloat your WSUS at all, it is just an awkward name, as Artem confirmed.
I am not aware if it would have been possible to assign one update to two categories in update catalog, while having one file only binary stored.
Is this understandable?
- Well from what I understand Artem isn't a developer, which make things even more akward.
Windows Server 2022 doesn't have a SAC version - just like all previous Windows Server versions except 2019. Yet it won't use the same naming convention in WSUS, nor will it follow the naming convention of SQL Server which traditionnaly shared it (SQL Server vNext won't be called "Microsoft SQL Server - database software 21H2" as far as I know).
Azure Stack HCI 21H2 share updates with Windows Server 2022 sure - for now at least. Who knows what will happen in the next ten years ? Especially considering the SaaS nature of Azure Stack, unlike Windows Server LTSC.
Same update base sure. But different products. So why not different categories ? Why complicate things ?
Why "Microsoft Server" anyway ? Why not "Windows Server" ? "Why "operating system" ? We'll get something in the future called "Server" but not being an operating system ? Or a Unix/Linux operating system ? Both at the same time ?
Sorry for the rant. WSUS products and classifications have been handled very poorly over the last years and are a total mess now. This is frustrating for us IT pros.- Alban1999, please check the twitter thread. I have brought same or similar points. They will not change it whatever it takes, this was a clear statement. It would be interesting what's happening in 3 years with the next Windows Server.
- Thanks, I'll check this. And thanks for your efforts I really do appreciate, even if it failed in the end anyway.
I wish Microsoft would discuss this with MVP and other IT Pros first, then decide on it later for this kind of change. We got Tech community blogs, forums, UserVoice, those tools exist for a reason. This is too important to be decided through Twitter.
And I just realize WSUS are automatically ordered using alphabetical, which means this product will sit right next to Microsoft Edge, instead of Windows Server forever. Sigh.