Forum Discussion

kwester-ebbinghaus-business's avatar
kwester-ebbinghaus-business
Iron Contributor
Sep 09, 2021
Solved

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....
management
Windows Server
  • kwester-ebbinghaus-business's avatar
    kwester-ebbinghaus-business
    Sep 10, 2021

    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.

thx1200's avatar
thx1200
Bronze Contributor
Dec 02, 2021
I just have to say that feature-freezing the MMCs is a really bad idea. As can be seen in this post, but in many other areas. WAC is great *for some things* but it's also terribly slow and some operations that take seconds in the MMC take minutes in WAC. It's just not ready for primetime. It should not have been pushed as a final replacement product until it reach feature parity with the MMC consoles.
kwester-ebbinghaus-business's avatar
kwester-ebbinghaus-business
Iron Contributor
Dec 02, 2021
on the other hand, allowing MMC to develop (they are not error free and feature complete and do not support any new features of OSes) this said gap might even increase, what do you think about this thx1200?
  • thx1200's avatar
    thx1200
    Bronze Contributor
    Dec 02, 2021

    kwester-ebbinghaus-business MS should not deploy a new management tool until its feature complete and a smooth experience.  Having no new features in MMC and then a terrible experience in WAC is terrible for users/admins because you split your time between two tools.

     

    So they should co-develop them both until the new one is ready.

Resources