none
Windows 10 KMS Requirements

Answers

  • Figured it out. This what you need to do:

    If not running a Server 2012 R2 KMS server, rebuild a fresh server.  If on Server 2012 R2 already, proceed with steps below (2008 R2 is not supported now for Windows 10)

    1.  Once on 2012 R2, install this update:  https://support.microsoft.com/en-us/kb/3058168

    2.  Go to VLS site, under licenses for your agreement (won't find it in media list yet since media isn't out til the 1st) and grab this key:  Windows Srv 2012 DataCtr/Std KMS for Windows 10

    3.  install and Activate the key from above with the SLMGR.vbs scripts like always.

    You now have a KMS server that can activate windows 10, as well as all of your existing server and desktop client OS's.  Of course if you are replacing an existing KMS server like I was, your would handle that in between steps 2 and 3 to remove the old server and switch names/IP addresses, etc.

    Thursday, July 30, 2015 2:12 PM

All replies

  • Not that I am aware of, I'm still looking as well. Glad I'm not the only one asking this question.

    ZdPav

    Wednesday, July 29, 2015 4:27 PM
  • Looking for this info as well. 
    Wednesday, July 29, 2015 4:43 PM
  • I may have found an answer. This hotfix may have been released for this exact purpose.

    https://social.technet.microsoft.com/Forums/en-US/1ada55cd-e213-4bfc-ab20-735c0e791f06/kms-2012-windows-10?forum=WinPreview2014Setup

    https://support.microsoft.com/en-us/kb/3058168

    I'm going to apply this patch and we'll see if Win10Ent will activate when I get the ISO from VLSC on Monday.

    I image, that technically, the current "king" license key for KMS is Win2012R2Ent and this KMS patch puts Windows 10 below it.


    ZdPav


    Wednesday, July 29, 2015 5:59 PM
  • I saw that patch, but I just didn't know if it would make Windows 10 "sit below" the Server 2012 R2 Datacenter KMS key we use.  Please confirm your Sever OS's still work, and let us know!  If so, this looks like the step to go.
    Wednesday, July 29, 2015 6:08 PM
  • I wonder if 2008 or 2008R2 as a KMS server is supported. 
    Wednesday, July 29, 2015 7:54 PM
  • Figured it out. This what you need to do:

    If not running a Server 2012 R2 KMS server, rebuild a fresh server.  If on Server 2012 R2 already, proceed with steps below (2008 R2 is not supported now for Windows 10)

    1.  Once on 2012 R2, install this update:  https://support.microsoft.com/en-us/kb/3058168

    2.  Go to VLS site, under licenses for your agreement (won't find it in media list yet since media isn't out til the 1st) and grab this key:  Windows Srv 2012 DataCtr/Std KMS for Windows 10

    3.  install and Activate the key from above with the SLMGR.vbs scripts like always.

    You now have a KMS server that can activate windows 10, as well as all of your existing server and desktop client OS's.  Of course if you are replacing an existing KMS server like I was, your would handle that in between steps 2 and 3 to remove the old server and switch names/IP addresses, etc.

    Thursday, July 30, 2015 2:12 PM
  • Thanks for the info on that. I am having trouble finding anything saying that 2008 R2 is not supported as a KMS host for Win10. can you sent me a link to where you read that? 
    Thursday, July 30, 2015 7:45 PM
  • Based of these KB articles, I can make an educated guess/recommendation.

    KB2885698 specifically states that it's for allowing win7(2008R2) hosts to KMS activate up to win8.1(2012R2) clients.

    KB3058168 hotfix specifically says win8(2012) and win8.1(2012R2) KMS hosts can activate future versions of windows (Win10).

    I recommend that you build a new 2012R2 KMS server. Especially since KMS is a built-in role now, and there is also a new VA service in 2012R2 that integrates with AD. You have to option to pick either KMS or VA. Details on that are here https://technet.microsoft.com/en-us/library/hh831612.aspx


    ZdPav

    Thursday, July 30, 2015 7:50 PM
  • Yeah, no 2008 R2 support if you want to do Windows 10. Office 2016 will probably have same requirement when it comes out, so mine as well rebuild on 2012 R2 now.  I had mine rebuilt and back up activating in under 25 min with a VM deployment.
    Thursday, July 30, 2015 8:14 PM
  • Excellent Advice!

    My Win10 machines are now activating against my KMS server.  I had everything in place but I just couldn't find the darn key! 



    • Edited by Joe.Robinson Thursday, July 30, 2015 8:39 PM
    • Proposed as answer by mric Thursday, October 08, 2015 4:47 PM
    Thursday, July 30, 2015 8:38 PM
  • Hi Jaybird283,

    I hope this link will be useful.

    Appendix A: KMS Client Setup Keys

    https://technet.microsoft.com/en-us/jj612867.aspx?f=255&MSPPError=-2147217396

    Best regards


    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    Friday, July 31, 2015 6:50 AM
    Moderator
  • These are the client KMS key, you need a server KMS key to activate Windows 10 client, i have searched in VLSC for the key but i cannot find it.

    Been looking here:

    
    • In VLSC - click License, then Relationship Summary.
    • Now click the License ID of your current Active license.
    • Once the page changes, click Product Keys.
    • Scroll down the list and look for "Windows Srv 2012R2 DataCtr/Std KMS for Windows 10"

    • Proposed as answer by Stuart Hudman Friday, August 07, 2015 10:27 PM
    • Unproposed as answer by Jaybird283 Wednesday, September 16, 2015 7:48 PM
    Monday, August 03, 2015 12:49 PM
  • I also could not find the Windows Srv 2012R2 DataCtr/Std KMS for Windows 10", but was looking under the wrong licence ID, as had multiple for my org,  have now located it
    Monday, August 03, 2015 2:27 PM
  • I've installed the key and Windows 10 machines are activating. This is good news.

    However, in the VAMT on Windows 2012 R2, I can't add the key as it says that the product key is invalid. So although it's working, it's not exactly as it was before. In short, you can't use the VAMT anymore.

    Anyone else noticed this?


    • Edited by agvonline Monday, August 03, 2015 2:34 PM
    Monday, August 03, 2015 2:34 PM
  • Here is more info about the error and what appears to be an upcoming patch for 2008 R2. 

    https://technet.microsoft.com/library/jj612867.aspx?f=255&MSPPError=-2147217396

    "If you are running Windows Server 2008 R2 or Windows 7, be on the lookout for an update to support using those as KMS hosts for Windows 10 clients."


    Monday, August 03, 2015 10:33 PM
  • This got me to activate Windows 10 KMS clients.  :)

    Jus to enforce what Zach said, go to:

    MVLSC

    Licenses

    Relationship Summary

    Select current agreement if you have multiple

    Then select the Product Keys sub-tab

    Scroll down to select the "Windows Srv 2012R2 DataCtr/Std KMS for Windows 10"

    Copy KMS Key

    Log into your KMS Server and open CMD as admin

    type: slmgr.vbs /ipk "KMS Product Key"

    • Edited by SenorTacos Tuesday, August 04, 2015 1:26 PM
    Tuesday, August 04, 2015 1:25 PM
  • Did you do this on a 2012 R2 host? or 2008 R2?

    Monday, August 10, 2015 7:25 PM
  • That info is in the KB3058168. It explicitly states that it is only for Windows 8, 8.1, 2012 and 2012 R2. 

    Monday, August 10, 2015 7:28 PM
  • Here is more info:

    There will be updates for KMS Servers running Windows Server 2008 R2 in October

    http://deploymentresearch.com/Research/Post/503/New-blog-post-Windows-10-As-A-Service-MVA-Jumpstart-ndash-The-OS-Deployment-Summary


    Tuesday, August 18, 2015 1:23 PM
  • Just to let you guys know. We have published an article on this - https://support.microsoft.com/en-us/kb/3086418

    Tuesday, August 18, 2015 1:48 PM
  • I really don't want to setup a new KMS host, them go though the fun of moving KMS hosted on an old server to a new host.   When will we get support for 2008 r2?

    Eric (Trying to be truly Wise by leaning form the mistakes of others, based on my success rate, I need to work harder at that.)

    Friday, August 21, 2015 7:15 PM
  • At some point in time, you are going to need to move away from your current 2008 R2 KMS server. I don't know how you have yours deployed, but it can be helpful to front your KMS server with a CNAME alias ("kms.yourdomain.com") that abstracts the actual KMS from your clients. After making sure all of your clients are going to that FQDN (via GPO or using the Volume Activation Management Tool), you are free to swap out the actual KMS at your leisure with a simple DNS change. 
    Friday, August 21, 2015 8:47 PM
  • Or, adopt ADBA and never bother with KMS again ;)

    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!)

    Saturday, August 22, 2015 12:28 AM
  • But ADBA means I have to migrate all my DC's to 2012.   Upgrading you all your DC's is easy(Sarcasm).  

    I plan to updated my DC's.  But that is a major task.   I never upgrade a DC because there is to much at risk.   I have to build new boxes,(need hardware),  and every time I deploy a new DC I can "decom" and old DC.   Yea, I can do some virtual but you still need physical DC's. 


    Eric (Trying to be truly Wise by leaning form the mistakes of others, based on my success rate, I need to work harder at that.)

    Monday, August 24, 2015 12:36 PM
  • IIRC, this won't work for Windows 7 / 2008 R2 clients. ADBA only works for Win 8 / Server 2012 and up. 

    But yes, I agree. Doing away with KMS in favor of ADBA is ideal. 

    Monday, August 24, 2015 4:04 PM
  • Remember - only Win8/2012 systems and up can take advantage of ADBA. 

    It doesn't  mean you need to upgrade your DCs to 2012 R2. You WILL need to update your AD schema to 2012, which contains the additional volume licensing attributes. So, you'll be spinning up a 2012 R2 server. But your DCs can remain 2008 R2. 

    More detail here - http://blogs.technet.com/b/amitd/archive/2014/04/19/active-directory-based-activation-in-windows-2012-windows-2012-r2.aspx

    There's no explicit need for physical DCs, although it IS a nice-to-have that can seriously save your keister in a major Hyper-V/VMware emergency. 


    • Edited by ChrisMullins Monday, August 24, 2015 4:14 PM Clarity
    Monday, August 24, 2015 4:13 PM
  • Is KMS activation of Windows 10 not supported on Windows Server 2008 R2 until the hotfix is made available in the October timeframe as per the articles below or has the stance been changed and there will not be a hotfix made available after all?

    https://technet.microsoft.com/library/jj612867.aspx “If you are running Windows Server 2008 R2 or Windows 7, be on the lookout for an update to support using those as KMS hosts for Windows 10 clients.”

    http://deploymentresearch.com/Research/Post/503/New-blog-post-Windows-10-As-A-Service-MVA-Jumpstart-ndash-The-OS-Deployment-SummaryNote: There will be updates for KMS Servers running Windows Server 2008 R2 in October…

    Monday, August 24, 2015 6:18 PM
  • So I've tried installing the hotfix to my 2012R2 server, and get the error that says this update does not apply to your server.  Yes, I made sure I downloaded the 2012r2 version of the hotfix, for 64bit, and won't let me install.  Also, tried activating the key for 2012r2/Windows 10, and said the key was invalid. Anyone else have this issue?

    Wednesday, August 26, 2015 5:09 PM
  • Hello,

    Can you open and elevated cmd prompt and run:

    systeminfo >info.txt

    Post the output of info.txt or make it available for download?


    Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Wednesday, August 26, 2015 7:00 PM
  • See below:

    OS Configuration:          Member Server
    OS Build Type:             Multiprocessor Free
    Registered Owner:          Infrastructure Services
    Registered Organization:   PSD
    Product ID:                06401-271-6983081-03296
    Original Install Date:     1/6/2015, 8:20:16 AM
    System Boot Time:          1/7/2015, 1:06:14 PM
    System Manufacturer:       VMware, Inc.
    System Model:              VMware Virtual Platform
    System Type:               x64-based PC
    Processor(s):              2 Processor(s) Installed.
                               [01]: Intel64 Family 6 Model 45 Stepping 7 GenuineIntel ~3300 Mhz
                               [02]: Intel64 Family 6 Model 45 Stepping 7 GenuineIntel ~3300 Mhz
    BIOS Version:              Phoenix Technologies LTD 6.00, 8/16/2013
    Windows Directory:         C:\Windows
    System Directory:          C:\Windows\system32
    Boot Device:               \Device\HarddiskVolume1
    System Locale:             en-us;English (United States)
    Input Locale:              en-us;English (United States)
    Time Zone:                 (UTC-07:00) Mountain Time (US & Canada)
    Total Physical Memory:     8,191 MB
    Available Physical Memory: 5,776 MB
    Virtual Memory: Max Size:  9,471 MB
    Virtual Memory: Available: 7,228 MB
    Virtual Memory: In Use:    2,243 MB
    Page File Location(s):     C:\pagefile.sys
    Domain:                    *******
    Logon Server:              \\*****
    Hotfix(s):                 40 Hotfix(s) Installed.
                               [01]: KB2862152
                               [02]: KB2868626
                               [03]: KB2876331
                               [04]: KB2883200
                               [05]: KB2884846
                               [06]: KB2887595
                               [07]: KB2892074
                               [08]: KB2893294
                               [09]: KB2894029
                               [10]: KB2894179
                               [11]: KB2898514
                               [12]: KB2898871
                               [13]: KB2900986
                               [14]: KB2901128
                               [15]: KB2903939
                               [16]: KB2904266
                               [17]: KB2909210
                               [18]: KB2911106
                               [19]: KB2912390
                               [20]: KB2913270
                               [21]: KB2913760
                               [22]: KB2914218
                               [23]: KB2916036
                               [24]: KB2919394
                               [25]: KB2922229
                               [26]: KB2925418
                               [27]: KB2928680
                               [28]: KB2931366
                               [29]: KB2939087
                               [30]: KB2961851
                               [31]: KB2961908
                               [32]: KB2962123
                               [33]: KB2973408
                               [34]: KB2973906
                               [35]: KB2975061
                               [36]: KB2975625
                               [37]: KB3004545
                               [38]: KB3012199
                               [39]: KB3021910
                               [40]: KB3054203
    Network Card(s):           1 NIC(s) Installed.
                               [01]: Intel(R) 82574L Gigabit Network Connection
                                     Connection Name: Ethernet
                                     DHCP Enabled:    No
                                     IP address(es)
                                     [01]: *******
    Hyper-V Requirements:      A hypervisor has been detected. Features required for Hyper-V will not be displayed.

    Wednesday, August 26, 2015 7:43 PM
  • @CaseyJPSD, does your server have this (and all other updates) installed?

    https://support.microsoft.com/en-au/kb/2919355


    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!)

    • Proposed as answer by CaseyJPSD Monday, August 31, 2015 4:27 PM
    • Unproposed as answer by Jaybird283 Wednesday, September 16, 2015 7:49 PM
    Wednesday, August 26, 2015 8:56 PM
  • Nope, it was missing one update, then the rest flooded through...all good now!
    Monday, August 31, 2015 4:27 PM
  • If you're not wanting to upgrade the host computer OS to 2012 I found this article, which will allow you to just upgrade the KMS key for 2012.

    https://blog.workinghardinit.work/2013/10/17/update-your-kms-service-key-to-activate-windows-server-2012-r2-and-windows-8-1/

    Wednesday, September 16, 2015 2:26 PM
  • Hello

    The update for Windows Server 2008 R2 to enable Windows 10 client KMS activations was released.

    Update that enables Windows 7 and Windows Server 2008 R2 KMS hosts to activate Windows 10

    https://support.microsoft.com/en-us/kb/3079821


    Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    • Proposed as answer by MuhammadM Wednesday, October 21, 2015 3:19 PM
    Wednesday, September 16, 2015 4:33 PM
  • Hello,

    Should customers with Windows 2008 R2 KMS servers expect the same delay in Office 2016 activation availability after it is released?

    Thanks in advance,

    Dwayne Adams

    Wednesday, September 16, 2015 5:42 PM
  • Darrell,

    Do we need apply a different key to our KMS 2008 R2 servers after applying this patch?

    Thanks,

    Dwayne Adams

    Wednesday, September 16, 2015 5:55 PM
  • Hello,

    You would need a KEY that support Windows 10 clients that can be installed on those Servers

    See this blog which identifies the key ( even though it refers to Windows Server 2012\R2 KMS hosts it's the same key)

     “Windows Srv 2012 R2 DataCtr/Std KMS for Windows 10.” is the key that would need to be installed.

    http://blogs.technet.com/b/askcore/archive/2015/09/15/windows-10-volume-activation-tips.aspx


    Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Wednesday, September 16, 2015 6:02 PM
  • Update: 2008 R2 can now activate Windows 10 clients with the hotfix below. 

    https://support.microsoft.com/en-us/kb/3079821


    • Edited by Jaybird283 Wednesday, September 16, 2015 7:44 PM Added the word "Update"
    Wednesday, September 16, 2015 7:43 PM
  • Figured it out. This what you need to do:

    If not running a Server 2012 R2 KMS server, rebuild a fresh server.  If on Server 2012 R2 already, proceed with steps below (2008 R2 is not supported now for Windows 10)

    1.  Once on 2012 R2, install this update:  https://support.microsoft.com/en-us/kb/3058168

    2.  Go to VLS site, under licenses for your agreement (won't find it in media list yet since media isn't out til the 1st) and grab this key:  Windows Srv 2012 DataCtr/Std KMS for Windows 10

    3.  install and Activate the key from above with the SLMGR.vbs scripts like always.

    You now have a KMS server that can activate windows 10, as well as all of your existing server and desktop client OS's.  Of course if you are replacing an existing KMS server like I was, your would handle that in between steps 2 and 3 to remove the old server and switch names/IP addresses, etc.

    KB2919355 is a prereq to installing 3058168.  DonPick mentions this further down the page.  This was hanging me up until I figured that out.  Thanks.
    Thursday, September 17, 2015 10:12 PM
  • I've installed the key and Windows 10 machines are activating. This is good news.

    However, in the VAMT on Windows 2012 R2, I can't add the key as it says that the product key is invalid. So although it's working, it's not exactly as it was before. In short, you can't use the VAMT anymore.

    Anyone else noticed this?


    Can't add CSVLKs for Windows 10 activation to VAMT 3.1

    https://support.microsoft.com/kb/3094354

    1.Download the hotfix from the following location:
    http://support.microsoft.com/kb/3058168/EN-US
    2.Right-click 485392_intl_x64_zip, and then choose to extract the hotfix to C:\KB3058168.

    3.Extract the contents of the update by using the following command:
    expand c:\KB3058168\Windows8.1-KB3058168-x64.msu -f:* C:\KB3058168\

    4.Extract the contents of Windows8.1-KB3058168-x64.cab using the following command:
    expand c:\KB3058168\Windows8.1-KB3058168-x64.cab -f:pkeyconfig-csvlk.xrm-ms c:\KB3058168

    5.Copy C:\KB3058168\x86_microsoft-windows-s..nent-sku-csvlk-pack_31bf3856ad364e35_6.3.9600.17815_none_bd26b4f34d049716\pkeyconfig-csvlk.xrm-ms to the following location:
    C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\VAMT3\pkconfig

    6.Restart VAMT.


    Don

    Saturday, September 26, 2015 12:37 AM
  • Yes, they did release but it doesn't work at all. I have been working on it for a couple of days and it doesn't work. Do you know if this actually works? is there any trick to  make it work?

    Thanks,

    Lucy

    Wednesday, September 30, 2015 4:11 PM
  • Hello Lucy,

    What doesn't work?  There are multiple scenarios mentioned in the thread, they all work.

    So what the details of what you are attempting and what errors are you seeing?

    VAMT issue?

    Windows Server 2012 R2 as the KMS Host?

    Windows Server 2008 R2 as the KMS host?

    What is not working? 

    Is the update not installing?

    Is the product key not installing? 

    Are the KMS host clients not activating


    Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Wednesday, September 30, 2015 4:18 PM
  • Hello Darrell,

    Thank for your prompt answer. I have a Windows 2008 R2 SP1 server and I installed the patch and still I cannot get the Windows 10 KMS key installed on the KMS server to activate Windows 10 machines. I received the message  "On a computer running Microsoft Windows non-core edition, run 'slui.exe 0x2a 0xC00rF015' to display the error test. 
    Error: 0xC004F015".

    SO, in short, the Key product is not installing.

    Any help is very appreciated.

    Thanks,

    Lucy

    Wednesday, September 30, 2015 8:17 PM
  • Hello Darrell,

    Thank for your prompt answer. I have a Windows 2008 R2 SP1 server and I installed the patch and still I cannot get the Windows 10 KMS key installed on the KMS server to activate Windows 10 machines. I received the message  "On a computer running Microsoft Windows non-core edition, run 'slui.exe 0x2a 0xC00rF015' to display the error test. 
    Error: 0xC004F015".

    SO, in short, the Key product is not installing.

    Any help is very appreciated.

    Thanks,

    Lucy

    @Lucy, are you attempting to install the KMShost key for Win10 or WS2012R2+Win10. Only the WS2012R2+Win10 key will succeed if the KMShost OS is WS2008R2.
    The relevant update package for WS2008R2 is https://support.microsoft.com/en-us/kb/3079821

    Don

    Wednesday, September 30, 2015 8:54 PM
  • Hello Don,

    I am attempting to install KMS Host key for Win10. I already added the KMS host key for Win 2012 R2 a long time ago on the KMS server. How do I get the WS2012R2+Win10 key? I can get into our Volumen License account.

    Please help.

    Thanks,

    Lucy

    Wednesday, September 30, 2015 9:29 PM
  • Hello Don,

    I am attempting to install KMS Host key for Win10. I already added the KMS host key for Win 2012 R2 a long time ago on the KMS server. How do I get the WS2012R2+Win10 key? I can get into our Volumen License account.

    Please help.

    Thanks,

    Lucy


    [to find your WS2012R2 KMS Host product key suitable for issuing activations to Windows 10

    Logon to the MSFT VLSC Website www.microsoft.com/licensing/servicecenter

       Relationship Summary

        pick your Active Licensing ID

           Product Keys

            Windows Srv 2012R2 DataCtr/Std KMS for Windows 10

    If you cannot find your key, it might be because your VL agreement requires you to request a key from Microsoft, or, your agreement might be expired.

    More:

    http://blogs.technet.com/b/askcore/archive/2015/09/15/windows-10-volume-activation-tips.aspx

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


    Don


    • Edited by DonPick Thursday, October 01, 2015 8:43 AM
    Thursday, October 01, 2015 8:40 AM
  • Hi Lucy,



    You need to check: 

    In VLSC - click License, then Relationship Summary.
    Now click the License ID of your current Active license.
    Once the page changes, click Product Keys.
    Scroll down the list and look for "Windows Srv 2012R2 DataCtr/Std KMS for Windows 10"


    If you do not see it you need to contact license support https://www.microsoft.com/licensing/servicecenter/Help/Contact.aspx

    They can activate themselves by phone, and it should appear within a couple of minutes (at least it did for me)
    Thursday, October 01, 2015 8:40 AM
  • Thank you very much, Don!! It worked!! I really appreciated your help.

    Have a blessed day,

    Lucy :-)


    Thursday, October 01, 2015 2:54 PM
  • Thank you very much ReMark. It worked!

    Lucy :-)

    Thursday, October 01, 2015 2:54 PM
  • Although obvious in retrospect, for those doing an offline activation it's necessary to use the Volume Activation Tools to do a phone activation with this key to finish the process. I found it interesting that even after doing this and confirming that Windows 10 activations were processing correctly, adding the product key to the Volume Activation Management Tool still produced the error 'The specified product key is invalid...'. Since this doesn't affect functionality this is just a bit of trivia.

    Jim Riekse

    Wednesday, October 28, 2015 2:41 PM
  • Hello,

    The workaround for that is in this article for the key to be recognized.

    3094354                Can't add CSVLKs for Windows 10 activation to VAMT 3.1

    http://support.microsoft.com/kb/3094354/EN-US


    Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Wednesday, October 28, 2015 4:38 PM
  • Hi, I have configured a KMS server on Server 2012 for Windows 10 clients; I am working on configuring another KMS server in the environment but in a different geographical location/region. I had configured VA services role and installed the patch. When I tried to activate, I am getting the error 0x80072EFD. Also, this breaks the server 2012 activation on the server-meaning post the execution of slmgr /ato after (successful completion of slmgr /ipk "Volume License key for Server 2012 for Windows 10", the windows activation on the server 2012 in which I am working says "Windows is not activated". Not sure where the issue is? I had repeated the steps I had done for the previous server.

    Appreciate your advice in this regard.

    Thanks

    Friday, November 27, 2015 9:15 AM
  • Hi, I have configured a KMS server on Server 2012 for Windows 10 clients; I am working on configuring another KMS server in the environment but in a different geographical location/region. I had configured VA services role and installed the patch. When I tried to activate, I am getting the error 0x80072EFD. Also, this breaks the server 2012 activation on the server-meaning post the execution of slmgr /ato after (successful completion of slmgr /ipk "Volume License key for Server 2012 for Windows 10", the windows activation on the server 2012 in which I am working says "Windows is not activated". Not sure where the issue is? I had repeated the steps I had done for the previous server.

    Appreciate your advice in this regard.

    Thanks

    When you install a different product key for Windows (which is exactly what implementing KMShost is doing), this displaces/removes the existing product key for Windows. This "breaks" the activation of that previous product key. You must activate again, which activates the newly installed product key, and returns the Windows license to "Activated/Licensed" status.

    80072EFD = http communication failed.
    This suggests that your Windows KMShost cannot contact Microsoft.com due to a networking or routing or proxy or firewall configuration problem.


    Don [doesn't work for MSFT, and they're probably glad about that ;]

    Friday, November 27, 2015 10:27 PM
  • 2008 R2 is supported as a KMS host to activate Windows 10 clients.

    https://support.microsoft.com/en-us/kb/3079821


    If its worth doing, its worth doing right. Just try getting the CFO to pay for that though...

    Friday, January 15, 2016 10:11 PM
  • Hello,

    Following [Ananthsub], with the dedicated patch for Windows 8.1 to support Windows 10 clients, I have installed my Windows 10 KMS Key, and oops the one for Windows 8.1 clients has gone.

    I will follow the instructions given by [DonPick], and keep you updated on this.

    Info: Office 2013 and Office 2016 have cohabitated directly without any tricks after install the Office 2016 pack suite for KMS. I hopped Microsoft could anticipate the same behaviour for Windows client. It's always the same when you start migrating a compagny: both Windows and office different versions are used simultaneously.

    Pascal.

    Monday, February 08, 2016 5:31 PM
  • Hello,

    I confirm that installing the Windows 10 KMS Key as the effect to un-license the Windows 8.1 KMS Key.

    My KMS host is running on top of a Windows 8.1 + KMS Patch to support Windows 10.

    I'm gonna open a Microsoft case for this.

    Update : the Microsoft case is open. In the meantime I've found an interesting requirement table in techNet: https://technet.microsoft.com/en-us/library/dn502537.aspx

    Pascal.

    • Edited by Pascal HENRY Wednesday, February 10, 2016 2:03 PM
    Wednesday, February 10, 2016 10:29 AM
  • Hello,

    I confirm that installing the Windows 10 KMS Key as the effect to un-license the Windows 8.1 KMS Key.

    My KMS host is running on top of a Windows 8.1 + KMS Patch to support Windows 10.

    I'm gonna open a Microsoft case for this.

    Update : the Microsoft case is open. In the meantime I've found an interesting requirement table in techNet: https://technet.microsoft.com/en-us/library/dn502537.aspx

    Pascal.

    Windows can only have a single product key at any one time. Regardless of the role of the computer (KMShost or KMSclient or MAKclient or OEM or Retail or Server or Workstation), there can only be a single Windows product key resident. So, if you have a Windows product key "installed", and you then try to "install" a pkey, if the pkey is acceptable for the situation (matches the Windows product currently installed) this will displace/remove the previous pkey.

    Office pkeys are different, because Office products "sit on top of" the Windows OS.

    Additionally, for the KMShost scenario, the KMShost function/feature is enabled by the use of a particular type of Windows pkey. This KMShost pkey performs two functions;

    (1) it is the pkey for the Windows OS of the KMShost itself, and so must suit that purpose
    (2) it is the pkey for the KMShost feature/function

    So, the KMShost pkey must correctly match/suit the OS of the KMShost computer itself, and also suit the purpose for the KMSclients it will service.

    For the office KMShost service, this leverages the underlying Windows OS SPP engine on the KMShost.

    What have you raised the support case for? Which particular issue/question does it seek to resolve?


    Don [doesn't work for MSFT, and they're probably glad about that ;]

    Wednesday, February 10, 2016 8:13 PM
  • Hi [Don],

    Thanks for your reply. What you describe makes perfect sense.The question I raised as a Microsoft case is:

    Issue installing 2 Product Keys (W10 and W8.1) on a Windows 8.1 KMS host.

    I have since then performed many troubleshooting with the TS engineer, but with no luck.

    He checked that the specific KB was installed an advised today to install the KMS pkey Win 10 on my Windows 8.1 (??) and see if this can activate a Windows 10 client. According to what you said, this pkey won't even install on my Windows 8.1 KMS "Server".

    I'm gonna check this and keep you informed.

    Wouldn't it be easier to build a fresh Win10 KMS host, where I could "install" the KMShost pkey Win10 (to activate at the same time the KMS host and also Win 10 clients) ?

    But in this situation, what about my remaining Windows 8.1 computer, that needs to still be activated while in the migration process to Win 10.

    According to https://technet.microsoft.com/en-us/library/mt297923(v=vs.85).aspx the Win10 KMShost pkey should also activate previous Windows versions.

    I'll also try this scenario and give feedback.

    Regards,

    pascal.


    • Edited by Pascal HENRY Wednesday, February 17, 2016 1:04 PM Typos.
    Wednesday, February 17, 2016 1:02 PM
  • Hi [Don],

    Thanks for your reply. What you describe makes perfect sense.The question I raised as a Microsoft case is:

    Issue installing 2 Product Keys (W10 and W8.1) on a Windows 8.1 KMS host.

    I have since then performed many troubleshooting with the TS engineer, but with no luck.

    He checked that the specific KB was installed an advised today to install the KMS pkey Win 10 on my Windows 8.1 (??) and see if this can activate a Windows 10 client. According to what you said, this pkey won't even install on my Windows 8.1 KMS "Server".

    I'm gonna check this and keep you informed.

    Well, I'm not sure why it took the engineer so long to conclude that - it's fully documented publically, and always has been so, for about 8 years. And, it's also (hopefully clearly) illustrated in the wiki article I created, which is referenced in this discussion few times.

    Don [doesn't work for MSFT, and they're probably glad about that ;]

    Wednesday, February 17, 2016 8:50 PM
  • Hi,

    Even after reading the Wiki page, it's still somehow unclear for me :-(

    My existing situation is this one :

    my KMS Host is a Windows 8.1 Virtual Machine with activated following KMS Product keys (CSVLK):

    - Windows 8.1 Enterprise
    - Office Pro plus 2013

    Everything is ok, to activate all my computers in the compagny (Win8.1 + Office 2013).

    We transisition to Windows 10 + Office 2016.

    So I installed on my KMS Host the following packages in order to support both Win10 and the new office version:

    - Microsoft Office 2016 Volume License Pack  (https://www.microsoft.com/en-us/download/details.aspx?id=49164)

    - Update: activate Windows 10 from Windows 8 or Windows 8.1, and Windows Server 2012 or Windows Server 2012 R2 KMS hosts (https://support.microsoft.com/en-us/kb/3058168)

    Then I installed (slmgr /ipk + /ato) my KMS product key for Office 2016 : no issue. My Office 2016 clients are artivated by the KMS Host.

    Then I installed my KMS product key for Win10 : The Windows 10 KMS key was "Licensed" but my Windows 8.1 KMS key was declared as:

    This license is not in use.
    License Status: Unlicensed

    So I though, that not having the Windows 8.1 key marked as "licensed" would prevent my existing Windows 8.1 client to be activated.

    I did make thge test (slmgr /ato) and the existing Windows 8.1 client are still activated and my new Windows 10 client are also activated.

    Summary : Win 10 KMS pkey can activate Win 8.1 and Win 10 clients.

    I hope my trial and errors are correct.

    Regards,

    pascal.

    I

    Thursday, February 18, 2016 5:40 PM
  • Hi,

    Even after reading the Wiki page, it's still somehow unclear for me :-(

    My existing situation is this one :

    my KMS Host is a Windows 8.1 Virtual Machine with activated following KMS Product keys (CSVLK):

    - Windows 8.1 Enterprise
    - Office Pro plus 2013

    Everything is ok, to activate all my computers in the compagny (Win8.1 + Office 2013).

    We transisition to Windows 10 + Office 2016.

    So I installed on my KMS Host the following packages in order to support both Win10 and the new office version:

    - Microsoft Office 2016 Volume License Pack  (https://www.microsoft.com/en-us/download/details.aspx?id=49164)

    - Update: activate Windows 10 from Windows 8 or Windows 8.1, and Windows Server 2012 or Windows Server 2012 R2 KMS hosts (https://support.microsoft.com/en-us/kb/3058168)

    Then I installed (slmgr /ipk + /ato) my KMS product key for Office 2016 : no issue. My Office 2016 clients are artivated by the KMS Host.

    Then I installed my KMS product key for Win10 : The Windows 10 KMS key was "Licensed" but my Windows 8.1 KMS key was declared as:

    This license is not in use.
    License Status: Unlicensed

    So I though, that not having the Windows 8.1 key marked as "licensed" would prevent my existing Windows 8.1 client to be activated.

    I did make thge test (slmgr /ato) and the existing Windows 8.1 client are still activated and my new Windows 10 client are also activated.

    Summary : Win 10 KMS pkey can activate Win 8.1 and Win 10 clients.

    I hope my trial and errors are correct.

    Yes, your scenario is correct/expected/normal, and, it looks to me, that your configuration is now completed successfully.

    A Windows machine can only have a single Windows pkey "installed" at any one time. This means, any existing pkey will be removed/displaced, if you "install" a different pkey. That is why the KMShost pkey *must* be suitable for both purposes (purpose #1=license Windows on that machine, plus, purpose #2=act as KMShost)


    Don [doesn't work for MSFT, and they're probably glad about that ;]

    • Proposed as answer by Pascal HENRY Friday, February 19, 2016 9:15 AM
    Thursday, February 18, 2016 7:53 PM
  • Thank you! Thank you! Thank you!  This worked a treat.  The key was reported invalid but after installing the KB2919355 set of updates and a reboot I was able to upgrade the key with success :)

    Incidentally, Microsoft are no longer publishing the Windows 10 KMS Host key by default - you have to contact them in order to get them to release to your VLSC.

    Thursday, February 25, 2016 9:41 AM
  • Hello Phil,

    That depends on the type of Volume License Agreement as to whether it's published by default or not.


    Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Thursday, February 25, 2016 7:53 PM
  • Incidentally, Microsoft are no longer publishing the Windows 10 KMS Host key by default - you have to contact them in order to get them to release to your VLSC.

    It depends on the type of VL agreement you have. "smaller" agreements, you have to request it. Larger agreements just get it anyways.

    Don [doesn't work for MSFT, and they're probably glad about that ;]

    Thursday, February 25, 2016 8:10 PM