2019 KMS keys only activate Windows 8.1/Server 2012 & newer

[computer_expert]

Something to watch out for if you still use Windows 7 or Server 2008/2008R2.

 

https://docs.microsoft.com/en-us/windows-server/get-started-19/activation-19

[k-strider]

right the bottom one is my new 2019 DC key and the top is 2019 LTSC KMS key the middle ones are 2016 and office 2016... do i need to remove the older ones reading the doc in theory i just need the 2019 DC key... but weirdly it shows up as WS12_R2_channel

anyone else see it like this? my KMS is AD based running on 2012R2

[robyholmes]

So if understand right:

 

If you have a 2019 Server, don't put KMS on it if you still have Windows 7 or Server 2008 R2. You'll need to MAK licence your 2019 servers until the time comes you've got rid of W7 or WS2008R2?

[3s-gtech]

Or if you only have limited numbers of 7/2008/R2 machines you could shift those to MAK, as it means you can then retire KMS and use ADA alone.

[k-strider]

we already have to MAK windows 7 as our number is around 5 and fell below the 25 required for KMS.... i'm just a bit confused about the name of my new 2019 KMS keys compared to my 2016 names.

[kennysarmy]

we already have to MAK windows 7 as our number is around 5 and fell below the 25 required for KMS.... i'm just a bit confused about the name of my new 2019 KMS keys compared to my 2016 names.

 

So how does that work with the 25 no. requirement ?

 

We've all but migrated to Windows 10 across the site and next week when I pull 24 laptops running Windows 7 out of Science and replace them with 24 new devices running Windows 10 we'll only have about 18 Windows 7 devices left, all laptops.

 

Will they immediately start to complain about not being activated? How long will it take KMS to realise there are less than 25?

[Arthur]

Will they immediately start to complain about not being activated? How long will it take KMS to realise there are less than 25?

 

https://docs.microsoft.com/en-us/windows/deployment/volume-activation/activate-windows-10-clients-vamt

 

To track the activation threshold, the KMS host keeps a record of the KMS clients that request activation. The KMS host gives each KMS client a client ID designation, and the KMS host saves each client ID in a table. By default, each activation request remains in the table for up to 30 days. When a client renews its activation, the cached client ID is removed from the table, a new record is created, and the 30 day period begins again. If a KMS client computer does not renew its activation within 30 days, the KMS host removes the corresponding client ID from the table and reduces the activation count by one. However, the KMS host only caches twice the number of client IDs that are required to meet the activation threshold. Therefore, only the 50 most recent client IDs are kept in the table, and a client ID could be removed much sooner than 30 days. The total size of the cache is set by the type of client computer that is attempting to activate. If a KMS host receives activation requests only from servers, the cache will hold only 10 client IDs (twice the required 5). If a client computer running Windows 10 contacts that KMS host, KMS increases the cache size to 50 to accommodate the higher threshold. KMS never reduces the cache size.