![]() ![]() It means that the limitation Windows 10 versions having all releases in one product category repeats with Windows 11 and you face the same problem. Why is one product category for any SAC product an unfortunate decision? Microsoft noticed hindsight putting Azure Stack HCI, which is a SaaS product - same to Windows Server version (SAC) and has a similar release schedule - in one product category was an unfortunate design decision. Windows Server version will no longer be available after version 2004. But only for the initial release.Īnother OS emerged for those with Software Assurance rights, called Windows Server version xxxxĪka Windows Server SAC, while xxxx follow the Windows 10 OS naming of YYMM so 1903 for March 2019 release - or more precisely end of development cycle (branch), as release happened sometimes later. SQL Server each release had an own category from 2000 through 2019.Īnother OS emerged called Azure Stack HCI, got it's own product category. Simple as that one category for each release: So how about Windows Server, Windows Server product like SQL Server etc? 1903 and later now includes updates for the following:ġ903, 1909, 2004, 20H2 and 21H2, where 19 aswell as 2004-21H2 share the same binary updates. With WindMicrosoft introduced "1903 and later" category which I supposed and promoted the idea to have one category for 19 as these share the binary same updates. Later, thankfully, the team added new categories per release. With the era of Windows 10 OS, which applies to Server and Client OS alike, as these are very similar to the core, this has game changed a bit.Īt first all Windows 10 versions have been assigned to "Windows 10" category. SQL Server had its own category per major release ![]() Windows Server had its own category per major release Windows Client had its own category per major release ![]() Over the past decades, naming of product categories was rather simple. So what has changed? Product Categories, naming, that one need to learn and understand.īut before we get into let us recap about the history and where we come from. Windows Admin Center support for Windows Update Services is not on the horizon either. While it possible, there is a paid solution doing this for you to make your reporting great again. Ultimately the issues with detection of WU client OS strings - since Windows Server 2016 and Windows 10 is not fixed in the WU database either. Why? The rule to not update any legacy MMCs is in place with Windows Server 2022 LTSC, so also there are no improvements or additions to any MMC consoles, Server Manager, or Active Directory Administrative Center (DSAC). An exception to this rule was an important bug in DSAC that got caught in Windows Server 2022. ![]() Technically we cannot expect anything new in WSUS? Yes, it still exists and is still needed for SMB and SMC and bigger organizations, while latter might use ConfigMgr or MEMCM or ISV solutions, where WSUS is often a needed requirement. "Hey Karl, do you speak about this legacy stuff to deploy Updates for on-premises?" What's not yet published is changes to WSUS. OPS104 Securing SMB from within and without - Microsoft Tech Community SMB Compression in Windows Server 2022 and Windows Insider - Microsoft Tech Community SMB over QUIC is now in public preview! - Microsoft Tech Community Storage Innovations in Windows Server 2022 - Microsoft Tech Community Windows Server 2022 Security Baseline - Microsoft Tech CommunityĮnabling HTTP/3 support on Windows Server 2022 - Microsoft Tech Community Unrelated to this topic, links to some key improvements of Windows Server 2022 LTSC: The Microsoft Teams have written excellent and brief blogs about the news in Storage, SMB, Security and other topics you can find on. If you fail to find it contact VLSC support via phone. Some customers still struggle to find their SA benefits and ISOs / licenses and RDSH licenses in VLSC, but it is officially released. ![]()
0 Comments
Leave a Reply. |