I just took over KMS from another admin that is leaving, I got the basics from him, but wanted to ask some questions to make sure I understand what’s going on here, as I have never managed a KMS server before.
We needed to add the key for server 2022, from my understanding this will also activate win11 win10 and previous versions of server and desktop. For example, “the KMS host key Windows Srv 2019 allows you to activate all previous versions of Windows, starting from Windows 7/Windows Server 2008 R2.” I would assume the same for win server 2022 standard key form VLSC?
When Guides/blogs refer to KMS host key, they are talking about the Host key one gets from the VLSC? So, if I want servers and desktops to be activated I just get the key for Windows Server 2022 standard and import that.
The commands I used was the below, is this standard procedure on how to do this? And I fell like those command is for KMS/DNS not KMS/AD.
.\cscript.exe slmgr.vbs /ipk 12345-33333-55555-ZZZZZ-XXXXX
.\cscript.exe slmgr.vbs /ato
.\cscript.exe slmgr.vbs /dlv
Mostly Followed this guide: https://theitbros.com/activate-windows-with-kms-server/
If the above is for KMS/DNS what are the commands for KMS/AD (Yes, I know I need enterprise admin). I know one can use “Volume Activation Tools” to add the Key for AD, but how does one do it from the command line? I know we use both KMS/DNS and KMS/AD, as we can find records for both.
After running the above commands my test windows server 2022 did activate after a reboot. However why do I hear some people say you need to run 5-25 clients before the KMS will activate them. For example, I would need to spin up 25 windows 2022 server before KMS would kick in?
A question about he VLSC, we are EDU So how long before Windows 11 ISO is released on there? I already see it in SCCM an servicing update…
Thanks in advance, just need some these cleared up to have a better understanding.
-AA
