KMS Client Keys

We just rolled out 1200 Windows 8 Pro workstations in our environment. Our image was scripted with KMS client setup key NG4HW-VH26C-733KW-K6F98-J8CK4. The workstations are activating with no problem for our internal KMS Volume License Activation server.
They are renewing the activation every 120 days. However, when I go to one of the clients to look to see if windows is activated, it shows a license expiration date of 10-7-2014. I am seeing this in Computer>Properties>Windows Activation>View Details
in Windows Activation. Are all our workstations going to expire and stop working?

"KMS activations are valid for 180 days—the activation validity interval. To remain activated, KMS client computers must renew their activation by connecting to the KMS host at least once every 180 days. By default, KMS client computers
attempt to renew their activation every seven days. If KMS activation fails , the client will retry every two hours. After a client computer’s activation is renewed, the activation validity interval begins again."
Ref:
Understanding KMS
Carey Frisch

Similar Messages

Setting KMS client key in MDT

where exactly in MDT, Windows KMS client key should be entered?
Thx.
--- When you hit a wrong note its the next note that makes it good or bad. --- Miles Davis

Short answer is you really don't need to:
https://social.technet.microsoft.com/Forums/en-US/c9691329-702e-42e1-9593-c8c06618ff0f/mdt-2010-kms-activation?forum=mdt
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

KMS client activation failed, but got server response?

I've been using KMS for several years. Generally there are no problems with KMS, but I have a single machine that is refusing to activate, and I cannot determine why. I've been doing extensive web searching but I'm not finding anything useful.
Windows 7 Pro client is using the Windows 7 Pro KMS client key GPDD4 as usual.
KMS Server is in Windows 2008 R2
The event log says the client is getting a response from KMS server (see below).
============================
Server: slmgr /dlv
Name: Windows Server(R), ServerStandard edition
Description: Windows Operating System - Windows Server(R), VOLUME_KMS_R2_B channel
Partial Product Key: 7GCM2
License Status: Licensed
Key Management Service is enabled on this machine
Current count: 50
Listening on Port: 1688
DNS publishing enabled
KMS priority: Normal
Key Management Service cumulative requests received from clients
Total requests received: 444
Failed requests received: 297
Requests with License Status Unlicensed: 0
Requests with License Status Licensed: 86
Requests with License Status Initial grace period: 12
Requests with License Status License expired or Hardware out of tolerance: 2
Requests with License Status Non-genuine grace period: 0
Requests with License Status Notification: 47
===============================
Client ability to find KMS Server:
C:\Users\foo>nslookup -type=srv _vlmcs._tcp
Server: UnKnown
Address: 172.20.0.8
_vlmcs._tcp.XXXXXXXXXXXX SRV service location:
priority = 0
weight = 0
port = 1688
svr hostname = dc3.XXXXXXXXXXX
dc3.XXXXXXXXX internet address = 172.20.0.11
===============================
Client: slmgr /dlv
Microsoft (R) Windows Script Host Version 5.8
Copyright (C) Microsoft Corporation. All rights reserved.
Software licensing service version: 6.1.7601.17514
Name: Windows(R) 7, Professional edition
Description: Windows Operating System - Windows(R) 7, VOLUME_KMSCLIENT channel
Activation ID: b92e9980-b9d5-4821-9c94-140f632f6312
Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
Extended PID: 00371-00170-868-000000-03-1033-7601.0000-2092014
Installation ID: 011751536521019726056115618440708701492313365893152065
Partial Product Key: GPDD4
License Status: Initial grace period
Time remaining: 43200 minute(s) (30 day(s))
Remaining Windows rearm count: 1
Trusted time: 7/28/2014 9:36:41 AM
Please use slmgr.vbs /ato to activate and update KMS client information in order to update values.
=========================
Client: slmgr /ato
Microsoft (R) Windows Script Host Version 5.8
Copyright (C) Microsoft Corporation. All rights reserved.
Activating Windows(R) 7, Professional edition (b92e9980-b9d5-4821-9c94-140f632f6312) ...
Error: Product activation failed.
=========================
Client: Application Event log
Security-SPP Event ID 12288
The client has sent an activation request to the key management service machine.
Info:
0x00000000, 0x00000000, dc3.XXXXXXXXXX:1688, 637b796e-5348-4ce1-b0b5-4d750e9d471e, 2014/07/28 14:43, 0, 2, 43200, b92e9980-b9d5-4821-9c94-140f632f6312, 25
Security-SPP Event ID 12289
The client has processed an activation response from the key management service machine.
Info:
0x00000000, 0x00000000, 1, 0, 50, 120, 10080, 2014/07/28 14:43
Security-SPP Event ID 1033
These policies are being excluded since they are only defined with override-only attribute.
Policy Names=(IIS-W3SVC-MaxConcurrentRequests) (Microsoft.Windows.Smc-Enabled) (Shell-InBoxGames-FreeCell-EnableGame) (Shell-InBoxGames-Hearts-EnableGame) (Shell-InBoxGames-Minesweeper-EnableGame) (Shell-InBoxGames-PurblePlace-EnableGame) (Shell-InBoxGames-Shanghai-EnableGame)
(Shell-InBoxGames-Solitaire-EnableGame) (Shell-InBoxGames-SpiderSolitaire-EnableGame) (Shell-MultiplayerInboxGames-Backgammon-EnableGame) (Shell-MultiplayerInboxGames-Checkers-EnableGame) (Shell-MultiplayerInboxGames-Spades-EnableGame) (Shell-PremiumInBoxGames-Chess-EnableGame)
(Telnet-Client-EnableTelnetClient) (Telnet-Server-EnableTelnetServer) (TiffIFilterLicensing-EnableTiffIFilter) (WindowsAnytimeUpgrade-CanUpgrade)
App Id=55c92734-d682-4d71-983e-d6ec3f16059f
Sku Id=b92e9980-b9d5-4821-9c94-140f632f6312
Security-SPP Event ID 1003
The Software Protection service has completed licensing status check.
Application Id=55c92734-d682-4d71-983e-d6ec3f16059f
Licensing Status=
1: 4de78642-0f7f-4b61-9392-8add86d70ae8, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
2: 50e329f7-a5fa-46b2-85fd-f224e5da7764, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
3: 5a79ecd8-d33f-406c-a619-7785899b5d59, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
4: 770bc271-8dc1-467d-b574-73cbacbeccd1, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
5: 90a61a0d-0b76-4bf1-a8b8-89061855a4c9, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
6: 92f9d22a-65f5-49a7-90fe-06491b4fc379, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
7: 9abf5984-9c16-46f2-ad1e-7fe15931a8dd, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
8: 9ccffaf9-86a2-414e-b031-b2f777720e90, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
9: b92e9980-b9d5-4821-9c94-140f632f6312, 1, 0 [(0 [0xC004E003, 0, 0], [( 1 0x80070057 30 0 msft:rm/algorithm/volume/1.0 0x00000000 0)(?)( 1 0x80070057 30 0 msft:rm/algorithm/volume/1.0 0x00000000 0)(?)(?)(?)])(1 )(2 [0x00000000, 0, 1], [(?)( 5 0x00000000 30
43200)( 1 0x00000000 0 0 msft:rm/algorithm/flags/1.0 0x00000000 0)(?)(?)(?)])]
10: c1027486-8ae8-4633-9cf9-9658ed80504d, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
11: c1e88de3-96c4-4563-ad7d-775f65b1e670, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
12: c33001fc-5e9c-4f27-8c05-e0154adb0db4, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
13: cf3c5b35-35ff-4c95-9bbd-a188e47ad14c, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
14: cff07cac-7534-4cc3-b3f3-99e1a0aa3c20, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
15: d188820a-cb63-4bad-a9a2-40b843ee23b7, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
16: d8e04254-f9a5-4729-ae86-886de6aa907c, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
17: da22eadd-46dc-4056-a287-f5041c852470, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
18: e120e868-3df2-464a-95a0-b52fa5ada4bf, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
19: e838d943-63ed-4a0b-9fb1-47152908acc9, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
20: 4a8149bb-7d61-49f4-8822-82c7bf88d64b, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
21: afd5f68f-b70f-4000-a21d-28dbc8be8b07, 1, 0 [(0 [0xC004F014, 0, 0], [(?)(?)(?)(?)(?)(?)])(1 )(2 )]
Security-SPP Event ID 1003
The Software Protection service has completed licensing status check.
Application Id=55c92734-d682-4d71-983e-d6ec3f16059f
Licensing Status=
1: b92e9980-b9d5-4821-9c94-140f632f6312, 1, 1 [(0 [0xC004E003, 0, 0], [( 1 0x80070057 30 0 msft:rm/algorithm/volume/1.0 0x00000000 0)(?)( 1 0x80070057 30 0 msft:rm/algorithm/volume/1.0 0x00000000 0)(?)(?)(?)])(1 )(2 [0x00000000, 0, 1], [(?)( 5 0x00000000 30
43200)( 1 0x00000000 0 0 msft:rm/algorithm/flags/1.0 0x00000000 0)(?)(?)(?)])]
============================
Client MGA output:
Diagnostic Report (1.9.0027.0):
Windows Validation Data-->
Validation Code: 0
Cached Online Validation Code: N/A, hr = 0xc004f012
Windows Product Key: *****-*****-J8D7P-XQJJ2-GPDD4
Windows Product Key Hash: xgsndMkYdJsYmUng0qIJ/thx+HI=
Windows Product ID: 00371-868-0000007-85411
Windows Product ID Type: 1
Windows License Type: KMS Client
Windows OS version: 6.1.7601.2.00010100.1.0.048
ID: {5A310AE8-BFD2-49F1-A8BF-688D339981E8}(3)
Is Admin: Yes
TestCab: 0x0
LegitcheckControl ActiveX: N/A, hr = 0x80070002
Signed By: N/A, hr = 0x80070002
Product Name: Windows 7 Professional
Architecture: 0x00000009
Build lab: 7601.win7sp1_gdr.140303-2144
TTS Error:
Validation Diagnostic:
Resolution Status: N/A
Vista WgaER Data-->
ThreatID(s): N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002
Windows XP Notifications Data-->
Cached Result: N/A, hr = 0x80070002
File Exists: No
Version: N/A, hr = 0x80070002
WgaTray.exe Signed By: N/A, hr = 0x80070002
WgaLogon.dll Signed By: N/A, hr = 0x80070002
OGA Notifications Data-->
Cached Result: N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002
OGAExec.exe Signed By: N/A, hr = 0x80070002
OGAAddin.dll Signed By: N/A, hr = 0x80070002
OGA Data-->
Office Status: 100 Genuine
Microsoft Office Professional Plus 2007 - 100 Genuine
OGA Version: N/A, 0x80070002
Signed By: N/A, hr = 0x80070002
Office Diagnostics: 025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3_E2AD56EA-765-d003_E2AD56EA-766-0_E2AD56EA-134-80004005_E2AD56EA-765-b01a_E2AD56EA-766-0_E2AD56EA-148-80004005_16E0B333-89-80004005_B4D0AA8B-1029-80004005
Browser Data-->
Proxy settings: N/A
User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
Default Browser: C:\Program Files\Internet Explorer\iexplore.exe
Download signed ActiveX controls: Prompt
Download unsigned ActiveX controls: Disabled
Run ActiveX controls and plug-ins: Allowed
Initialize and script ActiveX controls not marked as safe: Disabled
Allow scripting of Internet Explorer Webbrowser control: Disabled
Active scripting: Allowed
Script ActiveX controls marked as safe for scripting: Allowed
File Scan Data-->
Other data-->
Office Details: <GenuineResults><MachineData><UGUID>{5A310AE8-BFD2-49F1-A8BF-688D339981E8}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010100.1.0.048</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-GPDD4</PKey><PID>00371-868-0000007-85411</PID><PIDType>1</PIDType><SID>S-1-5-21-3521851180-3244512111-2218252725</SID><SYSTEM><Manufacturer>Dell
Inc.</Manufacturer><Model>Inspiron 546 </Model></SYSTEM><BIOS><Manufacturer>Dell Inc.</Manufacturer><Version>A09</Version><SMBIOSVersion major="2" minor="5"/><Date>20090808000000.000000+000</Date></BIOS><HWID>095F3D07018400F6</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Central
Standard Time(GMT-06:00)</TimeZone><iJoin>1</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>DELL </OEMID><OEMTableID>FX09
</OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{90120000-0011-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft
Office Professional Plus 2007</Name><Ver>12</Ver><Val>1208E0A87E81D86</Val><Hash>FlQRxKwAwaRad03SQZkKxNggIRU=</Hash><Pid>89409-707-0082056-65245</Pid><PidType>14</PidType></Product></Products><Applications><App
Id="15" Version="12" Result="100"/><App Id="16" Version="12" Result="100"/><App Id="18" Version="12" Result="100"/><App Id="19" Version="12"
Result="100"/><App Id="1A" Version="12" Result="100"/><App Id="1B" Version="12" Result="100"/><App Id="44" Version="12" Result="100"/></Applications></Office></Software></GenuineResults>
Spsys.log Content: 0x80070002
Licensing Data-->
Software licensing service version: 6.1.7601.17514
Name: Windows(R) 7, Professional edition
Description: Windows Operating System - Windows(R) 7, VOLUME_KMSCLIENT channel
Activation ID: b92e9980-b9d5-4821-9c94-140f632f6312
Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
Extended PID: 00371-00170-868-000000-03-1033-7601.0000-2092014
Installation ID: 011751536521019726056115618440708701492313365893152065
Partial Product Key: GPDD4
License Status: Initial grace period
Time remaining: 43200 minute(s) (30 day(s))
Remaining Windows rearm count: 1
Trusted time: 7/28/2014 9:31:36 AM
Please use slmgr.vbs /ato to activate and update KMS client information in order to update values.
Windows Activation Technologies-->
HrOffline: 0x00000000
HrOnline: 0xC004C533
HealthStatus: 0x0000000000000000
Event Time Stamp: 6:23:2014 07:16
ActiveX: Registered, Version: 7.1.7600.16395
Admin Service: Registered, Version: 7.1.7600.16395
HealthStatus Bitmask Output:
HWID Data-->
HWID Hash Current: MgAAAAEABAABAAEAAAACAAAAAQABAAEAJJRe04hAjl+cEVTyEDPMabbK6kXsLQilArQ=
OEM Activation 1.0 Data-->
N/A
OEM Activation 2.0 Data-->
BIOS valid for OA 2.0: no, invalid Windows marker
Windows marker version: N/A
OEMID and OEMTableID Consistent: N/A
BIOS Information:
ACPI Table Name OEMID Value
OEMTableID Value
APIC DELL
FX09
FACP DELL
FX09
HPET DELL
OEMHPET
MCFG DELL
OEMMCFG
SLIC DELL
FX09
OSFR DELL
FX09
OEMB DELL
FX09
SSDT A M I
POWERNOW
================================
Windows 7 Pro was installed on this machine using Microsoft's volume activation media, and is a standard image applied via Windows Deployment Services to some 200 other computers with no problems.
We also use a variety of surplus/off-lease machines, usually Dell brand, never with any activation problems.

It's a Dell Inspiron desktop. Apparently a "for the home" system? Yet it was bought with Win 7 Pro OEM installed, and so I had hoped I could roll it into the KMS easily. Tried updating the BIOS but still acts the same.
How can a "home edition" BIOS that's incompatible with KMS come with Win 7 Pro OEM?
Oddly, we have several Dell XPS systems that are using KMS just fine. Those are almost exclusively marketed as "power gamer" systems for home use. I should see if there's some way to figure out which specific Dell products do this so they can be avoided.
Fortunately it seems Windows 7 Pro edition software does not care if I use the OEM key from the sticker, so I typed that in and it activated.
(Great, one weird machine that has to be treated specially from everything else we've got.)
Probably a question for Dell to answer. For whatever reason, Dell have not performed all the necessary OEM Activation (OA) configuration tasks on this machine, perhaps due to their manufacturing/marketing strategy for this model, or perhaps due to a defective
configuration pass in the factory. Perhaps the mainboard in this machine was repaired or replaced at some stage, and wasn't correctly re-configured. Only Dell can resolve the missing marker, since it requires OEM tools.
Activating using the COA sticker product key, doesn't depend on the marker being present.
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!)

Cannot install KMS key in VAMT for KMS clients

Dear Sir / Madam,
I have some technical problems about setup the KMS host and KMS clients.
OS of the KMS host: Windows Server 2012 Standard
OS of the KMS client: Windows 7 Professional (32bit)
Question 1:
I want to use KMS host server to handle KMS keys and activations for KMS clients. Which type of KMS key need to install in KMS host ?
Would I need to install Windows 7 Professional KMS key or
Windows Server 2012 Standard KMS key in the Volume Activation Management Tool (VAMT) ?
Question 2:
I found that I cannot installed the Windows 7 Professional KMS key in the Volume Activation Management Tool (VAMT), it pop-up an error message said that the KMS key invalid. How can I fix the problem?
Thanks for your help!

Hi Siu Wai,
You can also follow these steps:
1. Select a computer that you want to be your KMS host:
2. Install Windows Server.
3. At cmd prompt type the following:
Slmgr.vbs /ipk <your KMS KEY from MVLS>
The /ipk installs your MVLS key. Note if you need to change your key. For example change from a KMS_B to KMS_C key you must restart the Software Licensing service.
4. At cmd prompt type the following:
Slmgr.vbs /ato
The /ato activates the KMS host with Microsoft. You must activate the KMS host.
5. Restart the Software Licensing service.
6. Install the KMS client computers by using volume license media. You should not be prompted for cdkey during installation
7. By default these KMS client computers will query DNS and locate your KMS host and activate
KMS Client Setup Keys
To reset computers to be KMS clients type the following at elevated command prompt:
Slmgr.vbs /ipk xxxxx-xxxxx-xxxxx-xxxxx-xxxxx
Where xxxxx-xxxxx-xxxxx-xxxxx-xxxxx is the generic VL key from the following link.
http://technet.microsoft.com/en-us/library/ee355153.aspx#EFAA
Refer to:
Is it possibile to host multiple KMS Keys
on a single KMS server?
If there is anything else regarding this issue, please feel free to post back.
Best Regards,
Anna Wang
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Certain KMS clients won't activate

Hello,
I work at a Community College where we have somewhere around 400 computers throughout the building. Up until this summer, we have been using MAK keys for our activation. However, to make our image deployment process easier, we have just deployed a KMS server
to handle our activation.
Our labs are slowly replaced over time, so pretty much each computer lab has PCs that were purchased in different years. I mention this because all of our newer batches of PCs have been activating just fine using KMS, but one style of PC which is a little
older fails while using slmgr /ato with no specific error. It just says
failed with an error, or something like that. No error codes or descriptive message. I also see no errors in the event viewer.
Our KMS server is running 2008 R2 Enterprise with a KMS host key. I know this is the right key as like I said, our newer PCs are activating just fine. I'll post a screen capture of the /dli output on our KMS server once
my account on here will let me. The current count is at 50 (the max it will display), it's status is licensed, and it's using a VOLUME_KMS_R2_B_channel key.
Our Clients are all Windows 7 Professional, and I am using one of the
generic KMS Windows 7 Pro keys with the slmgr /ipk command on those. Again, I know that's right because most of our PCs activated with it just fine. However, when running slmgr /ato on the failing clients I get that generic error.
Now our PCs are created via an image deployment, but I made sure to use the
/generalize option for sysprep. I have also verified that all other PCs created by this image have unique CMIDs or whatever the term is. I have even done a
fresh install from a CD on the PCs in question with the same result.
I have made sure windows firewall is off on these PCs, I moved one physical PC to a different area in our network to rule out some kind of network trouble, and verified several times that
DNS is hosting the KMS properly using nslookup.
We are all at a loss here, and I would appreciate any advice or suggestions on what else might be going on here.

Hello,
As I said in my original post, the PC I am currently testing is a fresh install from a CD in order to rule out any duplicate CMIDs. I am also able to telnet to the KMS server from the machine n question over port 1688. Just to rule it out,
I manually set the KMS server using slmgr /skms <hostname>:<port>. I still get the same error.
As for events 12288 and 12289, there are none under the application logs. The only event I see is under Applications and Services Logs > Key Management Services,
12290 which has a response of 0x0, indicating the request was successful. Still getting the error.
I have also determined that it is one specific set of hardware that is having the issue. We have around 60 of these PCs all the same model and they are the only ones having this error. And as I said in my first post, these boxes are spread
across almost our entire network, and I have verified that other PCs in the same subnets work just fine.

How to activate Windows 8.1 on a Windows 2008 R2 KMS server when I don't have Windows 2012 R2 kms host key

I only have windows 8.1 kms host key but I can't add a client OS kms key to Windows 2008 R2 kms server. And I don't have Windows 2012 R2 license either. Is there any way I can activate Windows 8.1 using my existing kms server? Thanks.

I would like a yes no clarification answer. So does this mean that EVEN WITH THE PATCH. My Server 2012 Standard edition that currently hosts KMS VA for clients running Win7, Win 8, Office15, Server 2008, Server 2012. Will not be able to host windows 8.1?
I will have to install 8.1 and use as a host?
if you have a KMShost product key for WS2012R2, you can patch a down=level Server and be fine.
(the OP didn't renew SA or otherwise has no KMShost pkey for WS2012R2)
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!)
I'm having similar issues and have a similar question that doesn't seem to be answered:
My KMS server is Windows 2008 R2 (Also is my domain controller). I want to activate Windows 2012 R2 and Windows 8.1 machines off this KMS server. I can install the 2012 R2 key just fine but receive error 0xC004F015 (The Software Licensing Service reported
that the license is not installed) when I try to install my 8.1 KMS key.
What I'm gathering from this thread is that I have to set up a Windows 8.1 host and set it up to be a KMS server exclusively for activating Windows 8.1. Is this correct? If so, Microsoft needs to fix that. I have a SERVER for activations for a reason: it
is a server, not a client. If I am mis-understanding, how do I get my Windows 2008 R2 server to accept the Windows 8.1 KMS key for activating 8.1 clients?
Thanks!
You don't need Windows 8.1 KMS key. Your 2012 R2 KMS key will be able to activate your Windows 8.1 machines. So your current set up is fine, no need to set up another Windows 8.1 KMS host.
My problem is I don't have 2012 R2 KMS key as I didn't buy any Windows 2012 R2 license. So I can't use 2012 R2 KMS key to activate my Windows 8.1.
Oh that's interesting. I guess I need to play around more because my 8.1 test machine isn't activating. I'll start a new thread for that if needed. Sorry for the confusion.

Windows 8.1 Ente. KMS client

Hi,
I need to download windows 8.1 enterprise KMS client. Is it available to download?
Win 8.1 Evaluation available on TechNet is retail channel.
N.A.Malik

EDIT: Not for public download. If you have an MSDN or TechNet subscription, you may have access to the VL channel product in your subscriber downloads. It's also available from VLSC if you have a VL agreement.
As per
http://technet.microsoft.com/en-us/evalcenter/hh699156.aspx?ocid=wc-tn-wctc upgrade/conversion from evaluation to retail/full license is not supported.
You *might* be able to change the product key of the evaluation license to a KMSclient, but I would think this would be blocked, or, would leave the evaluation timer in place.
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!)

Can i Host the KMS Server in the Server which is a KMS client of other KMS Server

Hi,
Is it Possiblei can Host the KMS Server in the Server(2012 R2) which is a KMS client of other KMS Server..?
If yes ... Do i need to do any special configuration for that or normal Host configuration is enough..?
Thanks
Balaji K

Hi Sir,
"The KMS service does not require a dedicated server. The KMS service can be co-hosted with other services, such as Active Directory® Domain Services (AD DS) domain controllers and read-only domain controllers (RODCs).
KMS hosts can also run on physical computers or virtual machines that are running any supported Windows operating system, including Windows Server 2003. Although a KMS host that is running Windows Server 2008 R2 can activate any Windows operating
system that supports Volume Activation, a KMS host that is running Windows 7 can activate only computers running Windows 7 and Windows Vista."
Based on this ,it should work .
If you want to activate a windows server please enable KMS on a server .
"By default, client computers connect to the KMS host for activation by using anonymous RPCs through TCP port 1688. (You can change the default port.) After establishing a TCP session with the KMS host, the client sends a single request packet.
The KMS host responds with the activation count. If the count meets or exceeds the activation threshold for that operating system, the client is activated and the session is closed. The KMS client uses this same process for renewal requests. The communication
each way is 250 bytes."
https://technet.microsoft.com/en-us/library/ff793434.aspx
Also you can change it if that port is used by other service :
https://technet.microsoft.com/en-us/library/ff793407.aspx?f=255&MSPPError=-2147217396
Best Regards,
Elton Ji
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected] .

Windows 7 KMS client activation error

hi,
Windows 7 KMS client activation error
Any known issue?
Thanks

This problem occurs if the KMS server does not find a valid Windows marker in the ACPI_SLIC table in the computer's BIOS program. This problem occurs for one of the following reasons.
Cause 1
You purchased a computer that has a qualifying Windows operating system installed. However, the Windows marker in the ACPI_SLIC table is corrupted.
Cause 2
You purchased a computer that does not have a qualifying Windows operating system installed. In this case, the Windows marker is not present in the ACPI_SLIC table.

KMS Client activation not working.

We recently moved our KMSHost to a new server. Changed the DNS SVR record and all. All of the Windows 7 clients have moved over fine, but most of our newer Server 2012 R2 Servers are stuck on the old server information.
I have tried slmgr /skms and it will change the “KMS machine name from DNS”(shown with the slmgr /dlv command) but not the KMS machine IP address:”. If I run slmgr /ckms it will just put back in the wrong machine name from DNS.
I have a second server in almost the same state except it lists nothing and setting the host and trying to activate I can see it query the svr record, its shown if I display the DNS, but it errors out.
In both servers if I run slmgr /ato I get the following error.
Error: 0xC004F074 The Software Licensing Service reported that the computer could not be activated. No Key Management Service (KMS) could be contacted. Please see the Application Event Log for additional information.
Any idea on how to fix this problem?
Thanks Chris

Check that your new KMS is correctly loaded with the relevant updates and pkeys - you can get the 4F074 error, when a KMSclient machine locates a KMShost but the located KMShost doesn't have the correct updates/pkeys to service the request.
Use "cscript slmgr.vbs /dli all > kmsout.txt" to dump out the current status of your KMShost.
Which pkey is licensed/active? What OS is your KMShost running?
If you KMShost OS is WS2008R2, you need to apply updates and the WS2012R2 KMShost pkey to it, or it will not service requests from WS2012R2 KMSclients.
http://social.technet.microsoft.com/wiki/contents/articles/22510.volume-activation-kms-mak-adba-avma.aspx
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!)

Multiple KMS host keys

I have installed Windows Server 2012 R2 with Volume Activation Services service role.
I would like to install several KMS keys on this server (keys for windows 8.1, windows 8, windows 7, server 2012 R2, server 2012, server 2008, Office 2013, Office 2010,...).
Will that work correctly ?
thanks..

I have installed Windows Server 2012 R2 with Volume Activation Services service role.
I would like to install several KMS keys on this server (keys for windows 8.1,8,7, server 2012 R2, 2012,2008, Office 2013, Office 2010,...).
Will that work correctly ?
thanks..
You cannot install more than a single Windows product key on a system. You must choose the "highest" product/version KMShost pkey.
You must install any needed patches/updates that are pre-requisite, then install that Windows pkey.
Windows KMShost pkeys will activate all KMSclients at the same product/version *and* below.
For Office KMShost, you must install the relevant patch/update for each Office KMS pack, and also install each Office KMShost pkey.
This wiki article I wrote may be helpful:
http://social.technet.microsoft.com/wiki/contents/articles/22510.volume-activation-kms-mak-adba-avma.aspx
If your KMShost machine is WS2012R2, and you want to issue activations for WS2012R2 and all possible KMSclients (Windows KMSclients
and Office KMSclients):
Install the WS2012R2 KMShost pkey (no patches/updates are needed, because WS2012R2 is the latest release).
Install the Office2010 KMShost patch/update/pack, and, the Office2010 KMShost pkey.
Install the Office2013 KMShost patch/update/pack, and, the Office20103 KMShost pkey.
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!)

Deactivating KMS client license on vm workstation

I have a client that is working in a vmware environment, recently I have been receiving calls from users reporting their Office Pro Plus 2010 states it's not activated. They are using a KMS host/client environment, I believe the problem is they have
gotten to their limit as far as their licenses are concerned. I've already installed VAMT on their KMS host but when I try checking the available licenses there it says <not available>. I know I have about 20 vmware workstations that are
not being used nor will be used in this environment that I need to deactivate the Office license. I have a few questions:
1) How do I find out how many licenses they have available?
2) Other than disconnecting the client and waiting 180 days for license to drop, is there a way to deactivate the Office license from the client?

KMShost/KMSclient scenarios, have no upper limit to the number of KMSclients - KMS does not regulate the maximum number of KMSclients, so, I doubt this is the cause of your symptom.
KMShost does not track the number of clients, so it cannot apply an "available quantity=xyz" concept at all.
If a computer has Office installed, then it must hold a licensing/entitlement to do so. The status of the activation upon that computer is irrelevant from a licensing compliance perspective.
If KMSclient computers are becoming "unactivated", you will need to determine if they ever actually were activated (it's common that this occurs where clients were activated when installed but never successfully renew activation, so they are in constant
state of countdown from 180days).
You should check that the client computers are configured correctly, can discover/locate the KMShost, can connect to the KMShost, and get obtain an activation request/response sequence from the KMShost.
Check the client event logs as a starting point.
You can check the KMShost event logs to see if client traffic (requests/responses) are occurring.
VAMT is not capable of determining "how many KMSclient licenses are in use vs. available", since VAMT is dumb and merely collects information from the target computers and/or MS webservers. VAMT only knows what it can collect from client computers, and it
has no available method to collect "available KMSclient licenses" from a KMShost, because the KMShost does itself not hold that information.
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!)

VAMT showing KMS generic key as MAK...HUH? WHY?!

I have this computer with a Generic VLK (KBKQT-2NMXY-JJWGP....) for Office Standard 2013 which can, i'm assuming, only be gotten through a KMS host. However, when I check it using the Volume Activation Management Tools it shows "Office 15, OfficeStandardVL_MAK
edition"....what gives? Is this some kind of glitch or something else is amiss here? This is happening for a few of our machines that the previous IT tech installed Office. Oh and the Product Key Type reads as Retail instead of MAK.

Hi,
To check the activation type and status of Office, take Office 2010 for example:
Open an administrative level command prompt.
Navigate to the Office14 folder:
32bit Office on 64bit OS – “cd \Program Files (x86)\Microsoft Office\Office14”
32bit Office on 32bit OS and 64bit Office on 64bit OS – “cd \Program Files\Microsoft Office\Office14”
Execute “cscript ospp.vbs /dstatus”
Look at “LICENSE NAME” for license type and “LICENSE STATUS” for activation status
If Office is KMS activated you will see “KMS_Client edition” in the license name field:
If Office is KMS activated you will see “KMS_Client edition” in the license name field.
If Office is MAK activated you will see “MAK edition” in the license name field.
If Office is Retail activated you will see “Retail edition” in the license name field.
After the steps above you should know the actual activation type.
Or an easy way, ask the previous IT person if you have his contact information.
Regards,
Melon Chen
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.

Kms keys

Hello,
We have a customer that has installed a kms host key on 6 servers, so now they have 6 KMS hosts running. They have contacted us because they realize they have done something wrong. I am new to kms and have been reading on technet for serveral hours now, but still some thing are unclear to me
If I understand correctly deployment of kms should be simple and straightforward
The easiest way (read to support the most kms clients) is to install a 2008 R2 server with a 2008 R2 host key. This will support vista, 7, 2003, 2008 and 2008R2 kms systems and enable them to activate. Is this correct ?
I install a windows vista machine or windows 7 machine using a volume license product key. After installation the activation will occur automatically against the kms host and no extra manual steps are needed. I do not need to install/add a kms client key on the vista or windows 7 machine. Is this correct ?
Can i deactivate systems that were actived directly (before deployment of the kms host) with Microsoft and reactivate them with the kms host ?
s it possible to uninstall a kms host and thus making it a regular kms client (to reduce the number of kms hosts from 6 to 2) ?
Thanks in advance
Kind Regards
Stijn Delen

Regarding this question:
Question 1: "I install a windows vista machine or windows 7 machine using a volume license product key. After installation the activation will occur automatically against the kms host and no extra manual steps are needed. I do not need to
install/add a kms client key on the vista or windows 7 machine. Is this correct ?"
Answer: Yes, if your KMS host is set up properly, no extra steps are needed, they will activate automatically.
Question 2: "Can i deactivate systems that were activated directly (before deployment of the kms host) with Microsoft and reactivate them with the kms host ?"
Answer: You should not need to deactivate any systems. If they were activated with a MAK key, they're good forever...whether the KMS overrides the MAK, I don't know, but they can exist together peacefully. We have a mix in our environment of pcs we've
deployed using MAK keys (when we were first getting started) and pcs contacting our KMS server (pcs we've deployed more recently).

App-V 5.0 Sequencing Office 2010 - Cannot verify the License for this Application KMS

Hey Guys,
i already found some Topics about my Problem, but None of the Solutions i have found, help in my case. I hope someone can help...
I Sequenced Office 2010 Professional Plus x86 on an App-V 5.0 Sequencer Client (x64) and streamed it to Windows 7 x64 and Windows Server 2012. While i was sequencing, i followed the Articles at
http://blogs.technet.com/b/office_resource_kit/archive/2011/06/15/sequencing-office-2010-for-app-v-part-1-considerations.aspx and also used the Parameter:
msiexec/i OffVirt.msi ADDLOCAL=Click2runMapi,Click2runOWSSupp,Click2runWDS,OSpp,OSpp_Core PROPLUS=1
In the sequencing Process anything ist working fine, i can start Word, Excel... and Office is activated. When i publish the Application and stream to the Client or RDS, i get the Error message in the Screenshot.
I also tried to create a new Package and type in the KMS Client Key directly to Office, didnt work. In a third Sequencing Process (also new Sequence) i tried with an another Script what i have found: msiexec /i OffVirt.msi PROPLUS=1 KMSSERVICENAME=”SERVERNAME”
KMSSERVICEPORT=1688
Please help!!
Best regards

I am having this same exact issue; however, I have done everything in the App-V 5.0 Sequencing document, and I have enabled Set-AppVClientConfiguration -EnablePackageScripts 1.
The sequencer is on a Win 7 32-bit machine, so I used the following:
msiexec
/i OffVirt.msi ADDLOCAL=OSpp,OSpp_Core PROPLUS=1
KMS is registered in DNS, so I shouldn't have to specify KMS.
As soon as I start Office on a machine, setup screen comes up briefly, and then I see the:
"Microsoft Office cannot verify the license for this application. A repair attempt failed or was canceled by the user. The application will now shut down."
I would use the package accelerator; however, it's a new Pro Plus 2010 build, and it says 12 files are missing from the install (files like the actual OffVirt.msi and manifest files).
This is getting a little frustrating, as I've already tried the package 4 different times. I also tried this version:
msiexec/i OffVirt.msi ADDLOCAL=Click2runMapi,Click2runOWSSupp,Click2runWDS,OSpp,OSpp_Core PROPLUS=1
I am also using the latest SP2 client, Sequencer, and then the AppV 5.0 SP1 server is using the latest hotfix 4 which was released in April 2014.

KMS Client Keys

Similar Messages

Maybe you are looking for