Discussion in 'Windows 10' started by LiteOS, May 19, 2021.
@luzea - He is referring to the Windows 10 Enterprise LTSC 2022 SKU, not the Server one.
When it is published, the thread will be made.
- post deleted. the title of the post actually was cut off half way on mobile so i only read Windows 2022 and thought he was referring to Windows Server 2022.
How did you delete your post?
Last thing I heard was that it will be released with 2021H2 but will only be supported for 5 years.
EnterpriseS (5 years support) did not get new licenses/keys so far (21382), maybe it will be separate from Server 2022 and IoTEnterpriseS (10 years support)
It has always been the desktop version of the server, which means same kernel/build version.
So I don't see why 21382 would have much to do with EnterpriseS.
Are we certain that there will be a Windows 10 LTSC 2022?
If it is so, then it will be released without much testing as a cut down version of the Server 2022, currently build 20344 and very close to be something like what the recent IP was for 21H1, which was made final after adding few more language pack versions.
I was about to ask the same question. Only the powerful has that privilege lol
@luzea must have it
Everybody lost the ability to delete their own posts after the big hack a few years ago, you can ask to get the option back.
I lost that ability with the change to XenForo. I often write stupid things, so, being able to delete my own posts would be a big plus for me.
As to the LTSB/LTSC matter, MS has not added Volume 2016 and Volume 2019 to the Server 2022 KMS license, yet. They may be up to something with the licenses in LTSB/C releases.
I'm aware mate. I witnessed all the conundrum turmoil.
Are you serious?
Get it back to me only?
Please @Yen bring me back the power to obliterate
You need to login to view this posts content.
@abbodi1406 @Carlos Detweiller
Thank for clarifying. If this is the case, it is indeed unusual.
Microsoft might try to force people to activate using Active Directory but this leaves standalone machines not covered.
Standalone machines can still use token-based activation, IIRC. Or activation by phone.
It is about KMS activation and lower version servers being activated by a Windows Server 2022 legit KMS host with a KMS host activation key installed on it.
Token based (MAK, retail) and phone activation are different mechanisms and they are available outside of the KMS activation or Active Directory activation mechanisms.
For clarification, a KMS host is activated with a separate key which is like a retail or MAK key, but for this specific purpose which is KMS host. When a KMS host is activated, it becomes a master KMS server for the KMS clients which is able to activate KMS clients which have to be minimum 5 server clients or 25 workstation (Windows 7, 8.x or 10) clients. Otherwise the KMS host is not functional. This refers to the official implementation only using a specific KMS host key for activation.
Note: The limit of minimum 25 clients applies to the Office KMS implementation as well.
There are separate activation keys for KMS host for servers, workstations or Office.
It is confusing but it is all explained in the Microsoft official documentation published few years ago.
I know all that. The CSVLK for the Server 2022 KMS Host license (which is the highest and has always included all older clients too) does contain neither LTSB 2016 nor LTSC 2019, at least so far. Makes no sense, even for MS. Should they really abolish KMS for these older LTSB/C clients, there are some alternative activation methods like HwID, that's all I said.
However, it could also be possible they want to streamline the LTSB/C license and include all of them into Windows Volume 2015 (or go with a completely new Windows Volume LTSC one). A new LTSC will come out every 3 years, and soon there would be an abundance of different LTSC KMS IDs they had to support, in addition to the Server ones.
I see the KMS Host ID like another type of HWID. It functions like MAK or Retail activation keys in reality, activating specific machines. So I don't know how much overhead it adds as the number of KMS Hosts is relatively small when compared to the other HWID clients.