KMS Not Automaticall Activating

[richie19rich77 0]

Hi Everyone,

 

I had to rebuild our server running KMS, since the rebuild clients are not automatically activating. Pretty basic install, server OS is Windows Server Standard 2008 R2, activated using VL Windows Server 2008 R2 KMS key, enabled firewall for KMS, and checked that the DNS VLMCS record had been created.

 

So what is happening is that the client does not automaticall change from MAK to KMS, I have to manually run "/ipk FJ82H-XT6CR-J8D7P-XQJJ2-GPDD4" using the microsoft KMS key to change it. Then I have to manually specify the KMS server using the "/skms" command. If I do all this and the count is 25 it will activate.

 

Client

 

Microsoft ® Windows Script Host Version 5.8
Copyright © Microsoft Corporation. All rights reserved.

Software licensing service version: 6.1.7601.17514

Name: Windows® 7, Professional edition
Description: Windows Operating System - Windows® 7, VOLUME_MAK channel
Activation ID: 9abf5984-9c16-46f2-ad1e-7fe15931a8dd
Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
Extended PID: 55041-00172-007-174153-03-1033-7601.0000-1542014
Installation ID: 004132561416519403578295156233172955014925186024976125
Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88338
Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88339
Use License URL: http://go.microsoft.com/fwlink/?LinkID=88341
Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88340
Partial Product Key: VJ6Y3
License Status: Licensed
Remaining Windows rearm count: 2
Trusted time: 17/03/2015 09:45:28

 

 

NSLOOKUP from Client

 

C:\Windows\system32>nslookup -type=srv _vlmcs._tcp.xxx.xxx.xx
Server: qehdc1.xxx.xxx.xx
Address: 192.168.111.9

_vlmcs._tcp.xxx.xxx.xx SRV service location:
priority = 0
weight = 0
port = 1688
svr hostname = qehwsus1.xxx.xxx.xx
qehwsus1.xxx.xxx.xx internet address = 192.168.111.13

 

 

Server

Copyright © 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>cscript slmgr.vbs /dlv
Microsoft ® Windows Script Host Version 5.8
Copyright © Microsoft Corporation. All rights reserved.

Software licensing service version: 6.1.7601.17514

Name: Windows Server®, ServerStandard edition
Description: Windows Operating System - Windows Server®, VOLUME_KMS_R2_B chann
el
Activation ID: c99b641f-c4ea-4e63-bec3-5ed2ccd0f357
Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
Extended PID: 55041-00168-313-762504-03-2057-7601.0000-0752015
Installation ID: 014925801852060651446993734576005235317582513131186852
Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88342
Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88343
Use License URL: http://go.microsoft.com/fwlink/?LinkID=88345
Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88344
Partial Product Key: FBG9V
License Status: Licensed
Remaining Windows rearm count: 2
Trusted time: 17/03/2015 09:42:32

Key Management Service is enabled on this machine
Current count: 6
Listening on Port: 1688
DNS publishing enabled
KMS priority: Normal

Key Management Service cumulative requests received from clients
Total requests received: 29
Failed requests received: 0
Requests with License Status Unlicensed: 0
Requests with License Status Licensed: 3
Requests with License Status Initial grace period: 14
Requests with License Status License expired or Hardware out of tolerance: 0

Requests with License Status Non-genuine grace period: 0
Requests with License Status Notification: 12

 

 

I am now at a loss, any ideas where I have gone wrong?

 

Thanks

[charles 0]

All your windows 7 clients must have a KMS key. (https://technet.microsoft.com/en-us/library/jj612867.aspx) They will not automatically revert to KMS if you have already activated windows 7 with a MAK key.

[richie19rich77 0]

I have not activated using MAK, these are PC's imaged via ZEN (SYSPREPED). Like I said they do activate if I manually run "/IPK" with the Windows KMS key.

 

So this will always be a manual (Or Scripted) process of running the IPK command? When I first build my KMS server before the server crashed; I didn't have to change from MAK to KMS, they would automatically detect the KMS server and activate.

 

Thanks

[charles 0]

Client

 

Microsoft ® Windows Script Host Version 5.8
Copyright © Microsoft Corporation. All rights reserved.

Software licensing service version: 6.1.7601.17514

Name: Windows® 7, Professional edition
Description: Windows Operating System - Windows® 7, VOLUME_MAK channel
Activation ID: 9abf5984-9c16-46f2-ad1e-7fe15931a8dd
Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
Extended PID: 55041-00172-007-174153-03-1033-7601.0000-1542014
Installation ID: 004132561416519403578295156233172955014925186024976125
Processor Certificate URL: http://go.microsoft....k/?LinkID=88338
Machine Certificate URL: http://go.microsoft....k/?LinkID=88339
Use License URL: http://go.microsoft....k/?LinkID=88341
Product Key Certificate URL: http://go.microsoft....k/?LinkID=88340
Partial Product Key: VJ6Y3
License Status: Licensed
Remaining Windows rearm count: 2
Trusted time: 17/03/2015 09:45:28

 

Are you injecting a MAK product key while syspreping?

 

It should read: Description: Windows Operating System - Windows® 7, VOLUME_KMSCLIENT channel

 

And then it would work as expected...

 

Change the key with the /IPK command and then /ato and it should register with no problems.

[richie19rich77 0]

Ok thanks, I will check. We have moved from SCCM to ZEN so maybe when syspreping the image we put it in by mistake.

[richie19rich77 0]

Thank you for your help, I re-checked ZEN and there was a spelling mistake specifying KMS server name, this would explain why it stopped working when we moved from SCCM to ZEN (ENGL).

[kweathe 1]

A great tool with KMS is the Volume Activation Management Tool or VAMT.

• You can remotely (through WMI) Change MAK to KMS Client Keys
• You can also initiate activations for both Windows and Office.
• Keep track of Licensing.

 

https://technet.microsoft.com/en-us/library/ff686876.aspx