KMS activation

[zag]

Forgive my n00b question but how do I use the KMS key to activate windows 7?

 

I'm running windows 2003 standard on my domain.

[Psymon]

open cmd.

 

Type slmgr for the list of commands you can perform.

 

Just opening mine and i will type the commands needed to install and activate a KMS key with DNS advertising enabled.

 

Si

 

edit: jsut read Server 2003, will find you a link to install.

[Psymon]

KMS Service V1.2 (Windows 7, Server 2008 etc...)

An update is available that installs Key Management Service (KMS) 1.2 for Windows Server 2003 Service Pack 1 (SP1) and for later versions of Windows Server 2003

 

Install this then launch CMD.

 

Type slmgr for a list of commands.

 

slmgr -ipk PRODUCTKEYGOESHERE (Use the KMS key from MVLS)

slmgr -ato (Activates the KMS key)

slmgr -sdns (Enable DNS publishing of a _SRV record for the KMS)

 

slmgr -dli (display license information)

 

When you install the clients for Windows7, Windows Vista, Server08, do not type any product keys into the image. The default key that is on the disk will auth with the KMS.

 

KMS keys are for the service

MAK keys are manual activations

Key pre-installed on the MVLS disc will automatically work.

 

KMS will not work until 25 (i think) clients auth with it. The message when you click "Activate windows now" will say "You have not reached the required amount of clients" or something along those lines.

 

Hope this helps.

Si

 

PS - little guide i wrote a while back - http://www.edugeek.net/forums/windows-server-2008/22736-vista-wds-key-management-service-kms.html

Edited August 18, 2009 by Psymon

[powdarrmonkey]

Note: you don't activate Windows directly, you install the server service somewhere and activate that, then Windows picks it up from your DNS infrastructure and works some magic itself.

[leco]

Thanks for the explanation Si, this is something that I have always meant to ask but never got around to. I have been manually inserting the licence key on each installation prior to this

[Zer0kbps]

if the kms service is running on a windows 2008 box it requires only a minimum of 5 activations to work.

 

 

On another note, does anyone know what sort of dns srv records are created?

[SYNACK]

On another note, does anyone know what sort of dns srv records are created?

 

SVR records

KMS Auto Discovery

 

vlmcs._tcp.. 3600 IN SRV 0 100 1688 kms1.oit.ncsu.edu.

_vlmcs._tcp.. 3600 IN SRV 0 100 1688 kms.ncsu.edu.

 

 

The individual parts of the records mean the following:

• Service name: vlmcs (this is what Microsoft decided to call it)
  
• Protocol: TCP
  
• Domain in which service is to be available:
  
• Time-to-live: 3600 seconds (recommended by Microsoft)
  
• Record type: SRV
  
• DNS priority: 0
  
• DNS weight: 100
  
• Service port number: 1688
  
• Hostname: kms1.oit.ncsu.edu, kms.ncsu.edu
  

 

For example, if your workstations are registered in the mydept.cop.ncsu.edu DNS domain, you will need to request that the following be appended to the mydept.cop.ncsu.edu domain:

 

_vlmcs._tcp.mydept.cop.ncsu.edu. 3600 IN SRV 0 100 1688 kms1.oit.ncsu.edu.

_vlmcs._tcp.mydept.cop.ncsu.edu. 3600 IN SRV 0 100 1688 kms.ncsu.edu.

 

You cannot simply configure a parent DNS domain with the KMS information and have computers registered in child domains automatically locate the service. Each DNS domain must be configured individually. If you only had appended the cop.ncsu.edu domain, computers in the mydept.cop.ncsu.edu domain would not be able to automatically locate the KMS service.

Edited August 18, 2009 by SYNACK

[mitchell1981]

Hi,

 

I've been messing around with KMS and I've set up 6 servers on Windows Server 2008 R2 using the appropriate KMS key from MVLS. I also have a key for Windows 7 on MVLS, but when I go to install the key into the KMS server it suggests that the exisiting key will be replaced. If this is the case how can I install both keys on the server or do I not need to?

 

Perhaps I need to run a seperate server for Windows 7?

[Psymon]

You will have 4 KMS keys in your Volume Licensing website.

1 - Win Srv 2008 R2 Data Ctr/Itan KMS C

2 - Windows Server 2008R2 Std/Ent KMS B

3 - Windows Web Srv 2008R2 KMS A

4 - Win 7 - KMS

Works like the hierarchy above, keys can activate their peers and below, none of the class above.

DataCentre / Itanium can activate all servers and clients including other Itanium / Datacentre installs.

Standard / Enterprise can activate other Standard / Enterprise Servers, Web Server installs and all clients, but not any keys above it (Just Datacentre / Itanium)

Web Srv can activate other web servers, and clients, but not Std / Enterprise / Datacentre

Win7 can activate other clients only, no servers.

 

Your best bet is to install 1 KMS server with the Datacentre KMS key, job done then can activate everything in the school.

 

Hope this helps,

Si

[mitchell1981]

Thanks that makes it all a bit clearer. Fortunately that is more or less what I have done. Might start experimenting with a Windows 7 client then!

[zag]

Hmm I tried SLMGR -IPK OURWINDOWS7KMSKEY

 

but get the software license service reported that the product key is invalid

 

Am I doing something wrong? I just copy and pasted the KMS key from the website.

 

EDIT: Never-mind, I just found the "request MAK key" button on the licensing website, Problem solved

[roty80]

Hmm I tried SLMGR -IPK OURWINDOWS7KMSKEY

 

but get the software license service reported that the product key is invalid

 

Am I doing something wrong? I just copy and pasted the KMS key from the website.

 

EDIT: Never-mind, I just found the "request MAK key" button on the licensing website, Problem solved

 

Exactly the same thing happened to us, validation error 0xC004F050 and when we run slui.exe it says the product key is invalid.

 

We have been using KMS to licence Vista since it came out and not had a problem.

 

We have installed the update (KB968912) for KMS on our Windows 2008 server this morning.

 

Emailed Microsoft Volume Licencing asking if they know why it would say it wasn't a valid key, no response yet. Definately the KMS key off our licence agreement.

 

Any ideas?

[roty80]

Problem solved

 

Microsoft replied to us telling us just request MAK keys but last night on MVLS our KMS keys changed. Windows 7 is just KMS, Vista and the different versions of Server 2008 are either KMS A, KMS B or KMS C. Looks like microsoft changed the machines you can run KMS on last night:

 

KMS can be hosted on Windows 7 or Windows Server 2003 R2 -> activates 7 and Vista

KMS_A can be hosted on Web Server 2008 -> activates Vista, 7, Web Server 2008 and HPC Server 2008

KMS_B can be hosted on Server 2008 Standard -> etc

KMS_C can be hosted on Server 2008 Enterprise -> etc

 

So our KMS key for Windows 7 will only work on a Windows 7 PC or Server 2003 R2 machine.

 

Setup a Windows 7 PC and put entered:

cscript c:\windows\system32\slmgr.vbs /ipk ****-****-****-**** (where * is key)

 

This morning all machines say they are activated.

 

Looks like for 2008 R2 we will have to setup a Server 2008 R1 Enterprise machine to activate it.

Edited August 27, 2009 by roty80
correction

[zag]

Sucks you have to have 2003 R2 to use this

[mitchell1981]

Can I ask how, people plan to test Windows 7 without having to set up 25 machines?

 

I would like to test it on a couple of machines in a classroom before going for a whole classroom, but as soon as I join them to the domain, they immediately lose their 30 day grace period and start popping up all sorts of warnings about my software not being genuine.

 

My KMS server is all set up and working, but I don't really want to install on 25 machines yet.

 

What are others doing?

[ces973]

Can I ask how, people plan to test Windows 7 without having to set up 25 machines?

 

I would like to test it on a couple of machines in a classroom before going for a whole classroom, but as soon as I join them to the domain, they immediately lose their 30 day grace period and start popping up all sorts of warnings about my software not being genuine.

 

My KMS server is all set up and working, but I don't really want to install on 25 machines yet.

 

What are others doing?

 

I just requested MAK keys until we get 25+ machines in. I have a KMS server up and running with our 7 KMS key, but there is no way we're going to have 25 Win7 machines in anytime soon.

[ranj]

I have a sneaking feeling I haven't fully understood our volume activation works with 7 and 2008 but after reading some detailed articles realise we may have a problem in the near future. We are a schools agreement customer and have begun using Windows 2008 and Windows 7 on our network.

 

After running some commands on the KMS server (nslookup -type=srv _vlmcs._tcp) I was quite surprised to hear that we have already 6 KMS hosts installed and registered in DNS and AD including a 7 test machine in the office as well as our production 2008 servers.

 

So the question is how have we get 6 KMS installations?

 

When we first received the keys of the volume licensing page we only used the KMS Key. At that time nobody knew what “KMS” meant. Since it was that and the MAK key we got, we thought as the MAK key had a countup (i.e. 0/500) we all thought it would be better to activate via KMS. Well, you really can use the KMS key to activate 7/2008. So, some of us in the office used this key for our 7 test installations as well as 2008 production servers. I was a bit more cautious and used a technet key.

 

However, the question is, when will we realise if we have a problem at all? In the case described above the problem hasn't hit us yet but I am a bit concerned especially as we have begun looking at Windows 7 test deployments. We haven't deployed it yet, so it is not a big problem. But reading the docs confirmed some worries I had about Windows Volume Activation 2.0.

 

Can someone confirm if this is correct? If I am able to remove all KMS hosts from AD. We have a 2008 datacenter license and KMS key. If I use this key when recreating a new KMS host, am I right in saying that this key will automatically activate any windows client and server. So when we create an image of a machine we do not have to insert whilst setting it up? Is this correct

 

I am confused!

[Psymon]

I have a sneaking feeling I haven't fully understood our volume activation works with 7 and 2008 but after reading some detailed articles realise we may have a problem in the near future. We are a schools agreement customer and have begun using Windows 2008 and Windows 7 on our network.

 

After running some commands on the KMS server (nslookup -type=srv _vlmcs._tcp) I was quite surprised to hear that we have already 6 KMS hosts installed and registered in DNS and AD including a 7 test machine in the office as well as our production 2008 servers.

 

Get the KMS server you want up and running On the machiens you do not want KMS run the command slmgr -upk to remove the KMS key from these servers. Running slmgr -ato after this should allow them to activate with the KMS server you want to use.

 

I think you might even be able to change the "weight" and "priority" of these DNS records in order to force the machines to use your preferred KMS server.

 

So the question is how have we get 6 KMS installations?

 

Using KMS key to activate them. Should either use MAK, or have a KMS server set up internally before running slmgr -ato manually.

 

However, the question is, when will we realise if we have a problem at all? In the case described above the problem hasn't hit us yet but I am a bit concerned especially as we have begun looking at Windows 7 test deployments. We haven't deployed it yet, so it is not a big problem. But reading the docs confirmed some worries I had about Windows Volume Activation 2.0.

 

As long as all of the KMS servers are functioning you will not realise there is a problem, as providing they all have 25 clients registered on them for activation, they are live and communicating with Microsoft. Providing you used the same KMS key on all machines, they can total the amount of queries from each KMS Server using your KMS Product Key.

 

Can someone confirm if this is correct? If I am able to remove all KMS hosts from AD. We have a 2008 datacenter license and KMS key. If I use this key when recreating a new KMS host, am I right in saying that this key will automatically activate any windows client and server. So when we create an image of a machine we do not have to insert whilst setting it up? Is this correct

 

You said ealirer in the post they your production servers are using this key, removing them from AD would not be a good idea You are correct, Data centre is the highest class of key available, and will authorise all servers and clients. Finallly, you do not need to insert a product key into any images / installations if you have a KMS server.

 

I am confused!

 

Hope this helped

 

Simon

Edited February 8, 2010 by Psymon

[mrbios]

Have i done this right?

 

I have a server which is running as the KMS Host with VAMT installed, i've added the MAK keys into it so i can activate PCs with that until we have 25 PCs available

 

I've added the DNS Srv record which appears to be working (tested with nslookup)

 

I have an unattend key file for WDS and for the Windows 7 image....

 

Do i want to remove the CD Key altogether from the Windows7 Unattendfile? What do i do when it asks for the CDKey upon initial startup (can't remember if you can just click next and do it later?)

 

Is there anything else i have to make sure if removed/set in the unattend file for this to work properly?

[ranj]

Get the KMS server you want up and running On the machiens you do not want KMS run the command slmgr -upk to remove the KMS key from these servers. Running slmgr -ato after this should allow them to activate with the KMS server you want to use.

 

 

I noticed when I removed one of the servers it complained a bit that it wasn't activated and then it activated itself.

 

Is there a way I can check on a client whether it's activated properly.

 

I tried running slmgr -dlv but the current count was still set to 0 and total requests received was also 0. So not sure if it has worked.

 

I also noticed that we have entered a KMS B channel Key on the KMS host. As we also have datacenter I would like to use this key instead as it will activate near all OS's. Is there a way I can change this on the KMS host?

 

Thanks

[Psymon]

Have i done this right?

 

I have a server which is running as the KMS Host with VAMT installed, i've added the MAK keys into it so i can activate PCs with that until we have 25 PCs available

 

I've added the DNS Srv record which appears to be working (tested with nslookup)

 

I have an unattend key file for WDS and for the Windows 7 image....

 

Do i want to remove the CD Key altogether from the Windows7 Unattendfile? What do i do when it asks for the CDKey upon initial startup (can't remember if you can just click next and do it later?)

 

Is there anything else i have to make sure if removed/set in the unattend file for this to work properly?

 

Shouldnt need to use VAMT. As long as you can get 25 clients to connect to your KMS server you will not have to worry. We have our unnatended file set up in such a manner that is does not prmopt for a CD key.

 

You should have no product key in your unnatended install script, as by default the images have KMS Client keys. Onlu use an MAK if you expect the machines to be off site for 6+ month stints.

 

Simon

[Psymon]

I noticed when I removed one of the servers it complained a bit that it wasn't activated and then it activated itself.

 

Is there a way I can check on a client whether it's activated properly.

 

I tried running slmgr -dlv but the current count was still set to 0 and total requests received was also 0. So not sure if it has worked.

 

I also noticed that we have entered a KMS B channel Key on the KMS host. As we also have datacenter I would like to use this key instead as it will activate near all OS's. Is there a way I can change this on the KMS host?

 

Thanks

 

"SLMGR -DLI" should state

Name : OS Name Here, Edition Here
Description : Windows Operating System - OS Name, VOLUME_KMSCLIENT channel
Partial Product Key : 2V3X8
License Status : Licensed
Volume Activation Expiration : xxxxx minute(s) (xxx day(s))

Key Management Service Client Information
  Client Machine ID (CMID) xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
  KMS Machine name from DNS : SERVER-NAME.Domain.name:1688
  KMS Machine Extended PID:
xxxxx-xxxxx-xxx-xxxxxx-xx-xxxx-xxxx.xxxx-xxxxxxx
  Activation Interval : xxx Minutes
  Renewal Interval : xxxxx Minutes

 

This tells you that that you are not inserting a product key, the product is activated, and the server it has activated with.

 

If it states anything other than KMSCLIENT you are putting a key in at some point.

 

Simon

[ranj]

"SLMGR -DLI" should state

Name : OS Name Here, Edition Here
Description : Windows Operating System - OS Name, VOLUME_KMSCLIENT channel
Partial Product Key : 2V3X8
License Status : Licensed
Volume Activation Expiration : xxxxx minute(s) (xxx day(s))

Key Management Service Client Information
  Client Machine ID (CMID) xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
  KMS Machine name from DNS : SERVER-NAME.Domain.name:1688
  KMS Machine Extended PID:
xxxxx-xxxxx-xxx-xxxxxx-xx-xxxx-xxxx.xxxx-xxxxxxx
  Activation Interval : xxx Minutes
  Renewal Interval : xxxxx Minutes

 

This tells you that that you are not inserting a product key, the product is activated, and the server it has activated with.

 

If it states anything other than KMSCLIENT you are putting a key in at some point.

 

Simon

 

Ok thats really odd. I have run this on 2 machines (1 windows 2008 R2 and the other was 1 windows 7 pro machine and get the following long message from windows script host:

 

Talk about the Key management service is enabled on this machine

Current count: 1

DNS publishing enabled

KMS priority : Normal

 

It seems to me that this machine is still acting as a KMS host, I am sure I followed the instruction above on one of the posts where it said

 

"On the machiens you do not want KMS run the command slmgr -upk to remove the KMS key from these servers. Running slmgr -ato after this should allow them to activate with the KMS server you want to use"

 

I ran these commands one after another but dont think its worked.

 

Any advice would be greatly appreciated.

Edited February 9, 2010 by ranj
Doesn't attach

[ranj]

First of all Major thanks to a fellow edugeek member "psymon" for helping me over the phone with this KMS issue.

 

We have now managed to get it working so we have 1 KMS server and all of our windows 7 and 2008/R2 clients can talk to the KMS server. We have checked to see they are communicating to the kms server by typing the slmgr -dli command.

 

When looking at the servers, it still says "this copy of windows is not genuine". On a server which says this message, if I run slmgr -dli it seems to communicating with the KMS server because it comes up with the correct KMS machine name. and the license status is licensed.

 

Is this because I have less than 25 clients registered on the KMS server?

 

Thanks