locked
KMS product key verification problems RRS feed

  • Question

  • Hey guys,

    I hope this is the correct forum, but I have a 2008 R2 KMS server on a 2008 R2 domain.  I have installed .Net Framework 4.5.1 on it with VAMT(Volume Activation Management Tool).  The KMS server has always worried me because the information and reporting has always been pretty horrifc. I can look through the logs and see activation requests being processed, but cannot tell what for.  Also, VAMT only shows license for Windows Server(not sure what version) and Office 2010(not sure if Standard or Enterprise).  I do not see anything for Windows 7, which seems weird, but cannot remember if I ever added that in or how we are doing it with the few thousand clients we have.  Would love to be able to tell if Win7 is/is not going through KMS, as I think it is.  Looked through this-http://technet.microsoft.com/en-us/library/ee939272 , but the KMS/VAMT tools seem very poor and always worry me.  Hopefully I am just missing something.

    1.  I am trying to add a KMS key from the MS Volume Licensing Center for Office 2013 Pro Plus with SP1 and it takes 10 minutes and comes back and says "The Product Key you entered is not supported.  Check the Key and try again.   If you have verified that the product key is correct, you may need to update this version of VAMT"

    I am positive the key is correct and a KMS key.  It takes so long, it seems like a timeout more than anything else.  Entered it with no hypen as described in this article-http://technet.microsoft.com/en-us/library/ff686878.aspx  Thought it might be some firewall issue, but I am making a direct connection and firewall guy says he sees no traffic even coming off the server.   Any ideas on this?  Should I try to add the key differently and see if that works, without verification?  Should I try a different KMS key for verification only?

    Thanks,

    Dan 


    Dan Heim

    Friday, August 22, 2014 10:07 PM

Answers

  • Hi Dan,

    for KMShost, if your KMShost is running WS2008R2, the KMShost product key which you "install" performs two functions.
    a) activates the Windows license for the WS2008R2 itself
    b) enables the KMShost function on your WS2008R2 so that it will receive, process and issue activation requests for KMSclients

    WS2008R2 KMShost will issue activations for Win7 KMSclients without any further configuration on your part, as long as you have sufficient KMSclients (25 clients) in contact with the KMShost. If your KMShost runs WS2008R2 you cannot install a Win7 KMShost pkey and there is no need to do so.

    If you wish to use KMSclient of newer Windows versions (e.g. Win8.0 or Win8.1, or WS2012 or WS2012R2) you will need to install an update on your KMShost and also install the relevant (later) KMShost product key.

    http://social.technet.microsoft.com/wiki/contents/articles/22510.volume-activation-kms-mak-adba-avma.aspx

    For Office KMShost/KMSclients, you can co-host the Office KMShost feature on the same KMShost you use for Windows KMSclients.

    To do so, you will need to install the relevant Office KMShost product key on your KMShost server (after installing the relevant Office KMShost "pack" update. Note that the Office KMShost product key is installed "alongside" the Windows product key.
    You can check on your KMShost, which product keys/licenses are installed on it, by using:
    cscript slmgr.vbs /dlv all > c:\slmgrout.txt
    This will show you which product keys/licenses are installed, and the status of each.

    For analysing the KMSclient <-> KMShost <-> KMSclient requests/responses, I find these articles helpful:

    http://technet.microsoft.com/en-us/library/ee939272.aspx

    http://technet.microsoft.com/en-us/library/cc303695.aspx#_KMS_Events_Logged

    What I do, is export the events from the event log of the KMShost, as a tab-delimited-text file, then I clean up the output file using Notepad++, and load it up with Excel.

    Each event, shows the "Activation ID" (which equates to the product for which the event applies) - there is an activation ID for each product type/version (e.g. Office ProPlus2010, Office Standard2010, Visio Pro2010, each has a specific Activation ID)

    e.g.
    ae2ee509-1b34-41c0-acb7-6d4650168915 Windows 7 Enterprise
    1cb6d605-11b3-4e14-bb30-da91c8e3983a Windows 7 EnterpriseN
    b92e9980-b9d5-4821-9c94-140f632f6312 Windows 7 Professional
    54a09a0d-d57b-4c10-8b69-a842d6590ad5 Windows 7 ProfessionalN
    cfd8ff08-c0d7-452b-9f60-ef5c70c32094 Windows Vista Enterprise
    d4f54950-26f2-4fb4-ba21-ffab16afcade Windows Vista EnterpriseN
    4f3d1606-3fea-4c01-be3c-8d671c401e3b Windows Vista Business
    2c682dc2-8b68-4f63-a165-ae291d4cf138 Windows Vista BusinessN
    df133ff7-bf14-4f95-afe3-7b48e7e331ef Office Project Pro 2010
    5dc7bf61-5ec9-4996-9ccb-df806a2d0efe Office Project Standard 2010
    b50c4f75-599b-43e8-8dcd-1081a7967241 Office Publisher 2010
    92236105-bb67-494f-94c7-7f7a607929bd Office Visio Premium 2010
    e558389c-83c3-4b29-adfe-5e4d7f46c358 Office Visio Pro 2010
    9ed833ff-4f92-4f36-b370-8683a4f13275 Office Visio Standard 2010
    2d0882e7-a4e7-423b-8ccc-70d91e0158b1 Office Word 2010
    6f327760-8c5c-417c-9b61-836a98287e0c Office Professional Plus 2010
    9da2a678-fb6b-4e67-ab84-60dd6a9c819a Office Standard 2010
    6ee7622c-18d8-4005-9fb7-92db644a279b Office Access 2013
    f7461d52-7c2b-43b2-8744-ea958e0bd09a Office Excel 2013
    a30b8040-d68a-423f-b0b5-9ce292ea5a8f Office InfoPath 2013
    1b9f11e3-c85c-4e1b-bb29-879ad2c909e3 Office Lync 2013
    dc981c6b-fc8e-420f-aa43-f8f33e5c0923 Office Mondo 2013
    efe1f3e6-aea2-4144-a208-32aa872b6545 Office OneNote 2013
    771c3afa-50c5-443f-b151-ff2546d863a0 Office OutLook 2013
    8c762649-97d1-4953-ad27-b7e2c25b972e Office PowerPoint 2013
    4a5d124a-e620-44ba-b6ff-658961b33b9a Office Project Pro 2013
    427a28d1-d17c-4abf-b717-32c780ba6f07 Office Project Standard 2013
    00c79ff1-6850-443d-bf61-71cde0de305f Office Publisher 2013
    b13afb38-cd79-4ae5-9f7f-eed058d750ca Office Visio Standard 2013
    e13ac10e-75d0-4aff-a0cd-764982cf541c Office Visio Pro 2013
    d9f5b1c6-5386-495a-88f9-9ad6b41ac9b3 Office Word 2013
    b322da9c-a2e2-4058-9e4e-f59a6970bd69 Office Professional Plus 2013
    b13afb38-cd79-4ae5-9f7f-eed058d750ca Office Standard 2013

    (I managed to find a partial list of these Activation ID's across several web searches of non-MSFT sites, and, surveyed my own KMS events to build the rest)

    [NB: I don't use VAMT at all, in my enterprise. VAMT gives me nothing I need, that I don't already have. VAMT is useful if you need to deal with MAK or a combination of MAK/KMS. I only use KMS in my enterprise]


    Don
    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
    This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)




    • Edited by DonPick Saturday, August 23, 2014 12:19 AM
    • Marked as answer by Alex Lv Tuesday, September 2, 2014 1:36 AM
    Saturday, August 23, 2014 12:15 AM

All replies

  • Hi Dan,

    for KMShost, if your KMShost is running WS2008R2, the KMShost product key which you "install" performs two functions.
    a) activates the Windows license for the WS2008R2 itself
    b) enables the KMShost function on your WS2008R2 so that it will receive, process and issue activation requests for KMSclients

    WS2008R2 KMShost will issue activations for Win7 KMSclients without any further configuration on your part, as long as you have sufficient KMSclients (25 clients) in contact with the KMShost. If your KMShost runs WS2008R2 you cannot install a Win7 KMShost pkey and there is no need to do so.

    If you wish to use KMSclient of newer Windows versions (e.g. Win8.0 or Win8.1, or WS2012 or WS2012R2) you will need to install an update on your KMShost and also install the relevant (later) KMShost product key.

    http://social.technet.microsoft.com/wiki/contents/articles/22510.volume-activation-kms-mak-adba-avma.aspx

    For Office KMShost/KMSclients, you can co-host the Office KMShost feature on the same KMShost you use for Windows KMSclients.

    To do so, you will need to install the relevant Office KMShost product key on your KMShost server (after installing the relevant Office KMShost "pack" update. Note that the Office KMShost product key is installed "alongside" the Windows product key.
    You can check on your KMShost, which product keys/licenses are installed on it, by using:
    cscript slmgr.vbs /dlv all > c:\slmgrout.txt
    This will show you which product keys/licenses are installed, and the status of each.

    For analysing the KMSclient <-> KMShost <-> KMSclient requests/responses, I find these articles helpful:

    http://technet.microsoft.com/en-us/library/ee939272.aspx

    http://technet.microsoft.com/en-us/library/cc303695.aspx#_KMS_Events_Logged

    What I do, is export the events from the event log of the KMShost, as a tab-delimited-text file, then I clean up the output file using Notepad++, and load it up with Excel.

    Each event, shows the "Activation ID" (which equates to the product for which the event applies) - there is an activation ID for each product type/version (e.g. Office ProPlus2010, Office Standard2010, Visio Pro2010, each has a specific Activation ID)

    e.g.
    ae2ee509-1b34-41c0-acb7-6d4650168915 Windows 7 Enterprise
    1cb6d605-11b3-4e14-bb30-da91c8e3983a Windows 7 EnterpriseN
    b92e9980-b9d5-4821-9c94-140f632f6312 Windows 7 Professional
    54a09a0d-d57b-4c10-8b69-a842d6590ad5 Windows 7 ProfessionalN
    cfd8ff08-c0d7-452b-9f60-ef5c70c32094 Windows Vista Enterprise
    d4f54950-26f2-4fb4-ba21-ffab16afcade Windows Vista EnterpriseN
    4f3d1606-3fea-4c01-be3c-8d671c401e3b Windows Vista Business
    2c682dc2-8b68-4f63-a165-ae291d4cf138 Windows Vista BusinessN
    df133ff7-bf14-4f95-afe3-7b48e7e331ef Office Project Pro 2010
    5dc7bf61-5ec9-4996-9ccb-df806a2d0efe Office Project Standard 2010
    b50c4f75-599b-43e8-8dcd-1081a7967241 Office Publisher 2010
    92236105-bb67-494f-94c7-7f7a607929bd Office Visio Premium 2010
    e558389c-83c3-4b29-adfe-5e4d7f46c358 Office Visio Pro 2010
    9ed833ff-4f92-4f36-b370-8683a4f13275 Office Visio Standard 2010
    2d0882e7-a4e7-423b-8ccc-70d91e0158b1 Office Word 2010
    6f327760-8c5c-417c-9b61-836a98287e0c Office Professional Plus 2010
    9da2a678-fb6b-4e67-ab84-60dd6a9c819a Office Standard 2010
    6ee7622c-18d8-4005-9fb7-92db644a279b Office Access 2013
    f7461d52-7c2b-43b2-8744-ea958e0bd09a Office Excel 2013
    a30b8040-d68a-423f-b0b5-9ce292ea5a8f Office InfoPath 2013
    1b9f11e3-c85c-4e1b-bb29-879ad2c909e3 Office Lync 2013
    dc981c6b-fc8e-420f-aa43-f8f33e5c0923 Office Mondo 2013
    efe1f3e6-aea2-4144-a208-32aa872b6545 Office OneNote 2013
    771c3afa-50c5-443f-b151-ff2546d863a0 Office OutLook 2013
    8c762649-97d1-4953-ad27-b7e2c25b972e Office PowerPoint 2013
    4a5d124a-e620-44ba-b6ff-658961b33b9a Office Project Pro 2013
    427a28d1-d17c-4abf-b717-32c780ba6f07 Office Project Standard 2013
    00c79ff1-6850-443d-bf61-71cde0de305f Office Publisher 2013
    b13afb38-cd79-4ae5-9f7f-eed058d750ca Office Visio Standard 2013
    e13ac10e-75d0-4aff-a0cd-764982cf541c Office Visio Pro 2013
    d9f5b1c6-5386-495a-88f9-9ad6b41ac9b3 Office Word 2013
    b322da9c-a2e2-4058-9e4e-f59a6970bd69 Office Professional Plus 2013
    b13afb38-cd79-4ae5-9f7f-eed058d750ca Office Standard 2013

    (I managed to find a partial list of these Activation ID's across several web searches of non-MSFT sites, and, surveyed my own KMS events to build the rest)

    [NB: I don't use VAMT at all, in my enterprise. VAMT gives me nothing I need, that I don't already have. VAMT is useful if you need to deal with MAK or a combination of MAK/KMS. I only use KMS in my enterprise]


    Don
    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
    This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)




    • Edited by DonPick Saturday, August 23, 2014 12:19 AM
    • Marked as answer by Alex Lv Tuesday, September 2, 2014 1:36 AM
    Saturday, August 23, 2014 12:15 AM
  • I was out on vacation last week and have not had time to review everything, but this is really helpful.  I did figure out that I can verify other MS KMS keys, but unable to verify the KMS keys for either Office 2013 Professional Plus or Office 2013 standard.  I pulled them directly off the MVLS site.  I will go through everything in this article because I am sure this is something simple.

    Dan Heim

    Thursday, September 4, 2014 6:06 PM