Migrating KMS From 2008R2 to 2019

%3CLINGO-SUB%20id%3D%22lingo-sub-2115270%22%20slang%3D%22en-US%22%3EMigrating%20KMS%20From%202008R2%20to%202019%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2115270%22%20slang%3D%22en-US%22%3E%3CP%3EHey%20all%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20are%20starting%20an%20analysis%20phase%20of%20a%20migration%20plan%20for%20our%20KMS%20running%20on%202008%20R2%20to%20a%20new%20Windows%202019.%3CBR%20%2F%3EMy%20experience%20with%20KMS%20is%20little%20to%20none%20as%20this%20is%20the%20first%20i'm%20ever%20digging%20into%20it%2C%20so%20sry%20if%20my%20questioning%20are%20at%20a%20low%20level.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20this%20analysis%20I've%20discovered%20a%20few%20things%20that%20created%20some%20questions%20which%20I%20was%20hoping%20someone%20could%20help%20with.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%2C%20current%20licenses%20looking%20at%20VAMT%20on%20the%202008%20R2%20are%3A%3C%2FP%3E%3CP%3E%3CSTRONG%3EWindows%20Server(R)%2C%20ServerStandard%20edition%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%3CSTRONG%3EMicrosoft%20Office%202010%2C%20KMSHost%20edition%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ELooking%20at%20the%20event%20viewer%20log%20I%20found%20attempts%20from%20several%202012%20servers%20and%20W10%20clients.%3C%2FP%3E%3CP%3EThey%20all%20seem%20to%20be%20rejected%20with%20error%20code%20%3CSTRONG%3E0xC004F042%3C%2FSTRONG%3E%20which%20means%20mismatch%20according%20to%20MS%20doc%20(%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fprevious-versions%2Fwindows%2Fit-pro%2Fwindows-server-2012-R2-and-2012%2Fdn502528(v%3Dws.11)%3Fredirectedfrom%3DMSDN)%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fprevious-versions%2Fwindows%2Fit-pro%2Fwindows-server-2012-R2-and-2012%2Fdn502528(v%3Dws.11)%3Fredirectedfrom%3DMSDN)%3C%2FA%3E.%3CBR%20%2F%3E%3CBR%20%2F%3EThis%20is%20good.%20However%2C%20I%20don't%20understand%20why%20they%20even%20try%20to%20talk%20with%20the%20KMS%20server%20in%20the%20first%20place%20as%20we%20are%20running%20AD%20activation%20for%20these%20OS'.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnyone%20able%20to%20explain%20this%20behavior%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnother%20finding%20is%20that%20a%20lot%20of%20W7%20clients%20seems%20to%20get%20activated%20with%20code%200x0.%20My%20first%20assumption%20is%20that%20the%26nbsp%3BWindows%20Server(R)%2C%20ServerStandard%20edition%20license%20product%20also%20works%20for%20W7%20OS.%20When%20running%26nbsp%3B%3CSTRONG%3Ecscript%20slmgr.vbs%20%2Fdlv%20all%20%3C%2FSTRONG%3Ei%20couldn't%20see%20any%20other%20products%20being%20activated.%26nbsp%3B%3CBR%20%2F%3ECan%20anyone%20verify%20or%20confirm%20if%20that's%20correct%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMy%20last%20question%20is%2C%20I%20wanna%20figure%20out%20which%20hosts%20are%20using%20the%20licenses.%20We%20have%20some%20uncertainty%20about%20the%20use%20of%20the%20Office%202010%20license.%3C%2FP%3E%3CP%3EWhen%20running%26nbsp%3B%3CSTRONG%3Ecscript%20slmgr.vbs%20%2Fdlv%20bfe7a195-4f8f-4f0b-a622-cf13c7d16864%26nbsp%3B%3C%2FSTRONG%3Ei%20see%20a%26nbsp%3B%20whole%20lot%20of%20total%20requests%20but%20i%20don't%20know%20when%20these%20are%20from.%20Are%20there%20any%20way%20to%20see%20exactly%20which%20hosts%20are%20using%20it%20and%20also%20a%20timestamp%20from%20when%20they%20grabbed%20it%3F%20Or%20perhaps%20other%20suggestions%20of%20how%20to%20deal%20with%20this%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20in%20advance.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2115270%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EManagement%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2119853%22%20slang%3D%22en-US%22%3ERe%3A%20Migrating%20KMS%20From%202008R2%20to%202019%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2119853%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F954183%22%20target%3D%22_blank%22%3E%40Sahajin%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20don't%20think%20that's%20the%20case.%3C%2FP%3E%3CP%3EWhen%20typing%26nbsp%3B%3CSPAN%3E%3CSTRONG%3Ecscript%20slmgr.vbs%20%2Fdli%3C%2FSTRONG%3E%26nbsp%3Bit%20displays%20the%20SRV%202008%20R2%20volume%20channel%20and%20partial%20product%20key.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EThat%20should%20be%20correct.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EMy%20theory%20is%20that%20the%20license%20key%20for%2008%20R2%20also%20applies%20for%20W7%20since%20they%20get%20activated%20(Not%20able%20to%20confirm%20it%20on%20any%20MS%20docs).%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EI%20have%20looked%20through%20the%20event%20viewer%20but%20the%20only%20thing%20I%26nbsp%3Bcan%20see%20is%20weather%20the%20host%20gets%20licensed%20or%20not.%20(Event%20ID%2012290).%20%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EAre%20you%20referring%20to%20any%20other%20event%20logs%3F%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2119170%22%20slang%3D%22en-US%22%3ERe%3A%20Migrating%20KMS%20From%202008R2%20to%202019%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2119170%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F956533%22%20target%3D%22_blank%22%3E%40DenStorePingvin%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThen%20you%20have%20your%20setup%20differently%20than%20ours.%26nbsp%3B%20We%20have%20servers%20outside%20of%20AD%20that%20get%20activated%20by%20our%20KMS%20as%20well.%20So%20we%20have%20it%20setup%20for%20all%20servers%20to%20get%20activated%20by%20our%20KMS%2C%20not%20AD.%20So%20even%20with%20that%20said%20the%20license%20key%20decides%20where%20it%20looks%20to.%20Regardless%2C%20if%20you%20have%20AD%20activation.%20Read%20here%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows-server%2Fget-started%2Fkmsclientkeys%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows-server%2Fget-started%2Fkmsclientkeys%3C%2FA%3E%3C%2FP%3E%3CP%3ESeeing%20how%20you%20are%20using%20GVLK%20license%20it%20still%20requires%20a%20KMS%20server.%20Basically%20Microsoft%20is%20doing%20a%20double%20talk.%20In%20AD%20activation%20is%20states%20you%20don't%20need%20a%20KMS%20and%20requires%20a%20GVLK%2C%20but%20looking%20at%20GVLK%20it%20requires%20a%20kms.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAll%20in%20all%20it%20sounds%20like%20you%20have%20a%20server%20with%20the%20wrong%20license%20key.%20The%20only%20thing%20I%20can%20think%20of%20is%20looking%20at%20the%20event%20viewer%20to%20see%20what%20is%20trying%20to%20get%20activated%20and%20go%20change%20the%20key.%20Or%20you%20could%20check%20each%20server%20and%20make%20sure%20they%20have%20the%20same%20key.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2118725%22%20slang%3D%22en-US%22%3ERe%3A%20Migrating%20KMS%20From%202008R2%20to%202019%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2118725%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F954183%22%20target%3D%22_blank%22%3E%40Sahajin%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThat%20makes%20no%20sense%20to%20me.%20Of%20cause%20AD%20activation%20is%20related%20to%20license%3F%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fdeployment%2Fvolume-activation%2Factivate-using-active-directory-based-activation-client%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fdeployment%2Fvolume-activation%2Factivate-using-active-directory-based-activation-client%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHowever%20the%20point%20of%20mentioning%20AD%20activation%20is%2C%20that%20the%20KMS%20server%20shouldn't%20have%20license%20for%20any%20other%20things%20than%20Office%202010%20and%20Server%202008%20R2.%20That's%20why%20I'm%20wondering%20why%20we%20have%20hosts%20from%20W10%2C%202012%2C%20W7%20etc%20that%20tries%20to%20get%20a%20license%20(W7%20even%20succeeds).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20checked%20the%20event%20log.%20I%20thought%20it%20was%20clear%20in%20my%20original%20post.%20That's%20how%20I've%20gathered%20the%20error%20codes.%20The%20issue%20is%20that%20we%20have%20tons%20of%20requests%20and%20it%20would%20be%20pain%20to%20look%20through%20them%20all%20manually.%20Had%20a%20look%20at%20some%20to%20get%20an%20overview%20of%20what%20types%20of%20OS'%20are%20contacting%20this%20KMS%20server%20which%20led%20to%20these%20questions.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2117795%22%20slang%3D%22en-US%22%3ERe%3A%20Migrating%20KMS%20From%202008R2%20to%202019%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2117795%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F956533%22%20target%3D%22_blank%22%3E%40DenStorePingvin%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFirst%2C%20I%20have%20to%20say%20that%20AD%20activation%20is%20nothing%20to%20do%20with%20the%20license.%20If%20you%20are%20running%20VLA%20(Volume%20License%20Agreement)%20and%20you%20have%20your%20servers%20pointing%20to%20your%20KMS%20server%20than%20the%20license%20key%20that%20your%20servers%20use%20will%20be%20activated%20by%20your%20KMS%20server.%20Nothing%20to%20do%20with%20AD.%20On%20your%20KMS%20server%20you%20should%20have%20an%20event%20log%20just%20for%20it%2C%20this%20will%20tell%20you%20what%20serial%20is%20contacting%20the%20server.%20If%20your%20servers%20are%20using%20a%20non%20VLA%20license%20then%20they%20will%20want%20to%20contact%20Microsoft%20to%20get%20activated.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBut%2C%20I%20would%20look%20at%20the%20event%20viewer%20on%20your%20KMS%20server%20and%20you%20should%20see%20what%20is%20talking%20to%20it.%20I%20haven't%20migrated%20to%202019%20yet%2C%20its%20coming%20though%2C%20as%20we%20are%20on%202012%20R2.%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

Hey all,

 

We are starting an analysis phase of a migration plan for our KMS running on 2008 R2 to a new Windows 2019.
My experience with KMS is little to none as this is the first i'm ever digging into it, so sry if my questioning are at a low level.

 

In this analysis I've discovered a few things that created some questions which I was hoping someone could help with.

 

So, current licenses looking at VAMT on the 2008 R2 are:

Windows Server(R), ServerStandard edition

Microsoft Office 2010, KMSHost edition

 

Looking at the event viewer log I found attempts from several 2012 servers and W10 clients.

They all seem to be rejected with error code 0xC004F042 which means mismatch according to MS doc (https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/dn....

This is good. However, I don't understand why they even try to talk with the KMS server in the first place as we are running AD activation for these OS'.

 

Anyone able to explain this behavior?

 

Another finding is that a lot of W7 clients seems to get activated with code 0x0. My first assumption is that the Windows Server(R), ServerStandard edition license product also works for W7 OS. When running cscript slmgr.vbs /dlv all i couldn't see any other products being activated. 
Can anyone verify or confirm if that's correct?

 

My last question is, I wanna figure out which hosts are using the licenses. We have some uncertainty about the use of the Office 2010 license.

When running cscript slmgr.vbs /dlv bfe7a195-4f8f-4f0b-a622-cf13c7d16864 i see a  whole lot of total requests but i don't know when these are from. Are there any way to see exactly which hosts are using it and also a timestamp from when they grabbed it? Or perhaps other suggestions of how to deal with this?

 

Thanks in advance.

 

 

4 Replies

@DenStorePingvin 

First, I have to say that AD activation is nothing to do with the license. If you are running VLA (Volume License Agreement) and you have your servers pointing to your KMS server than the license key that your servers use will be activated by your KMS server. Nothing to do with AD. On your KMS server you should have an event log just for it, this will tell you what serial is contacting the server. If your servers are using a non VLA license then they will want to contact Microsoft to get activated.

 

But, I would look at the event viewer on your KMS server and you should see what is talking to it. I haven't migrated to 2019 yet, its coming though, as we are on 2012 R2.

@Sahajin 

That makes no sense to me. Of cause AD activation is related to license? https://docs.microsoft.com/en-us/windows/deployment/volume-activation/activate-using-active-director...

 

However the point of mentioning AD activation is, that the KMS server shouldn't have license for any other things than Office 2010 and Server 2008 R2. That's why I'm wondering why we have hosts from W10, 2012, W7 etc that tries to get a license (W7 even succeeds).

 

I have checked the event log. I thought it was clear in my original post. That's how I've gathered the error codes. The issue is that we have tons of requests and it would be pain to look through them all manually. Had a look at some to get an overview of what types of OS' are contacting this KMS server which led to these questions.

@DenStorePingvin 

Then you have your setup differently than ours.  We have servers outside of AD that get activated by our KMS as well. So we have it setup for all servers to get activated by our KMS, not AD. So even with that said the license key decides where it looks to. Regardless, if you have AD activation. Read here

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

Seeing how you are using GVLK license it still requires a KMS server. Basically Microsoft is doing a double talk. In AD activation is states you don't need a KMS and requires a GVLK, but looking at GVLK it requires a kms. 

 

All in all it sounds like you have a server with the wrong license key. The only thing I can think of is looking at the event viewer to see what is trying to get activated and go change the key. Or you could check each server and make sure they have the same key.

@Sahajin 

I don't think that's the case.

When typing cscript slmgr.vbs /dli it displays the SRV 2008 R2 volume channel and partial product key.

That should be correct.

 

My theory is that the license key for 08 R2 also applies for W7 since they get activated (Not able to confirm it on any MS docs).

 

I have looked through the event viewer but the only thing I can see is weather the host gets licensed or not. (Event ID 12290).

 

Are you referring to any other event logs?