Volume Licensing and Activation error

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hello,

I am having an issue activating a computer to my KMS server. The current
count on the server is 35 computers, but this particular computer will not
activate. It is telling me that the product key is in use.

background information: this computer had the OS reloaded onto it as a
result of someone messing it and rendering it unusable. As a result the OS
(Vista Business) was reloaded and ever since this change I have been getting
the error that the key is already in use and that a new key needs to be
inserted. The KMS server seems in order other computers in the domain are
contacting it and the SRV entry seems to be ok on our Domain controllers.

To be on the safe side i would also like to know where exactly the SRV entry
should be at and how can i determine if that particular TCP port is also
being blocked. Currrently i am using the default port of 1688.
 
Hello Joe,
It sounds like the wrong key was used on that machine and that it is trying
to activate against the Microsoft Servers rather than against the KMS
server.
Open an elevated cmd prompt:
Run slmgr -dli
It should say something similar to this if it's a kms client machine:
Description: Windows Operating System - Vista, VOLUME_KMSCLIENT channel

Thanks,
Darrell Gorter[MSFT]

This posting is provided "AS IS" with no warranties, and confers no rights
--------------------
|>Thread-Topic: Volume Licensing and Activation error
|>thread-index: AceX0d4Nnmju/t1GSeaWRKBrVYsMPg==
|>X-WBNR-Posting-Host: 67.67.39.128
|>From: =?Utf-8?B?Sm9lVC10ZWNo?= <[email protected]>
|>Subject: Volume Licensing and Activation error
|>Date: Wed, 16 May 2007 08:50:03 -0700
|>Lines: 16
|>Message-ID: <[email protected]>
|>MIME-Version: 1.0
|>Content-Type: text/plain;
|> charset="Utf-8"
|>Content-Transfer-Encoding: 7bit
|>X-Newsreader: Microsoft CDO for Windows 2000
|>Content-Class: urn:content-classes:message
|>Importance: normal
|>Priority: normal
|>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2826
|>Newsgroups: microsoft.public.windows.vista.general
|>Path: TK2MSFTNGHUB02.phx.gbl
|>Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.vista.general:102271
|>NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
|>X-Tomcat-NG: microsoft.public.windows.vista.general
|>
|>Hello,
|>
|>I am having an issue activating a computer to my KMS server. The current
|>count on the server is 35 computers, but this particular computer will
not
|>activate. It is telling me that the product key is in use.
|>
|>background information: this computer had the OS reloaded onto it as a
|>result of someone messing it and rendering it unusable. As a result the
OS
|>(Vista Business) was reloaded and ever since this change I have been
getting
|>the error that the key is already in use and that a new key needs to be
|>inserted. The KMS server seems in order other computers in the domain are
|>contacting it and the SRV entry seems to be ok on our Domain controllers.

|>
|>To be on the safe side i would also like to know where exactly the SRV
entry
|>should be at and how can i determine if that particular TCP port is also
|>being blocked. Currrently i am using the default port of 1688.
|>
 
Yes it does say something like that. the problem is that we already have a
KMS server. Let me ask you this the key we were given is for KMS and we have
attempted it on other machines. I did notice that if you do not enter a key
during the setup "as volume activation does not require a key to be entered
at that time" it is suppose to grab it from the PID.txt file found in the
sources folder on the dvd. Well there is key specified there that does not
match the one we were given could this have anything to do with it.

We have already done 35 other machines and all this are contacting and
activating with the server with out problems. This is the first issue we
have experience with KMS activation.
 
Hello Joe,
The KMS key you were given is for KMS server machines, so you only install
that KMS key on machines that you want to running as a KMS server.
that key is limited to 6 activations, so if you used that key 6 times, you
already have 6 KMS server machines setup.
These machine activate against the Microsoft Activaton Server, not against
the KMS server machine,
I doubt you need another KMS server since you only have 35 machines. One
is all that can be used in that situation.

What you probably need to do is change the product key back to the key that
is in the PID.txt
open an elevated cmd prompt.
Run slmgr -ipk xxxxxx-xxxxxx-xxxxxx-xxxxxx-xxxxxx with the product key from
the pid.txt file.
This changes the product key back so that the machine will then become a
KMS_Client again and talk to the KMS server

Then attempt the activation of the product key.
Thanks,
Darrell Gorter[MSFT]

This posting is provided "AS IS" with no warranties, and confers no rights
--------------------
|>Thread-Topic: Volume Licensing and Activation error
|>thread-index: AceX6OlwrN1wFnsYTIiJFCtMaWOv5Q==
|>X-WBNR-Posting-Host: 67.67.39.128
|>From: =?Utf-8?B?Sm9lVC10ZWNo?= <[email protected]>
|>References: <[email protected]>
<DlozCb#[email protected]>
|>Subject: RE: Volume Licensing and Activation error
|>Date: Wed, 16 May 2007 11:35:00 -0700
|>Lines: 26
|>Message-ID: <[email protected]>
|>MIME-Version: 1.0
|>Content-Type: text/plain;
|> charset="Utf-8"
|>Content-Transfer-Encoding: 7bit
|>X-Newsreader: Microsoft CDO for Windows 2000
|>Content-Class: urn:content-classes:message
|>Importance: normal
|>Priority: normal
|>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2826
|>Newsgroups: microsoft.public.windows.vista.general
|>Path: TK2MSFTNGHUB02.phx.gbl
|>Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.vista.general:102359
|>NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
|>X-Tomcat-NG: microsoft.public.windows.vista.general
|>
|>Yes it does say something like that. the problem is that we already have
a
|>KMS server. Let me ask you this the key we were given is for KMS and we
have
|>attempted it on other machines. I did notice that if you do not enter a
key
|>during the setup "as volume activation does not require a key to be
entered
|>at that time" it is suppose to grab it from the PID.txt file found in
the
|>sources folder on the dvd. Well there is key specified there that does
not
|>match the one we were given could this have anything to do with it.
|>
|>We have already done 35 other machines and all this are contacting and
|>activating with the server with out problems. This is the first issue we
|>have experience with KMS activation.
|>
|>""Darrell Gorter[MSFT]"" wrote:
|>
|>> Hello Joe,
|>> It sounds like the wrong key was used on that machine and that it is
trying
|>> to activate against the Microsoft Servers rather than against the KMS
|>> server.
|>> Open an elevated cmd prompt:
|>> Run slmgr -dli
|>> It should say something similar to this if it's a kms client machine:
|>> Description: Windows Operating System - Vista, VOLUME_KMSCLIENT channel
|>>
|>> Thanks,
|>> Darrell Gorter[MSFT]
|>>
|>
 
you were totally correct Darrel,

i did attempt to do that and sure enough the problem got fixed. In fact I
did realize my mistake and was able to fix it. thank you for the reply and
it clarified things quite a bit. Again Thank you.

How can we go about and closing this post?

"Darrell Gorter[MSFT]" said:
Hello Joe,
The KMS key you were given is for KMS server machines, so you only install
that KMS key on machines that you want to running as a KMS server.
that key is limited to 6 activations, so if you used that key 6 times, you
already have 6 KMS server machines setup.
These machine activate against the Microsoft Activaton Server, not against
the KMS server machine,
I doubt you need another KMS server since you only have 35 machines. One
is all that can be used in that situation.

What you probably need to do is change the product key back to the key that
is in the PID.txt
open an elevated cmd prompt.
Run slmgr -ipk xxxxxx-xxxxxx-xxxxxx-xxxxxx-xxxxxx with the product key from
the pid.txt file.
This changes the product key back so that the machine will then become a
KMS_Client again and talk to the KMS server

Then attempt the activation of the product key.
Thanks,
Darrell Gorter[MSFT]

This posting is provided "AS IS" with no warranties, and confers no rights
--------------------
|>Thread-Topic: Volume Licensing and Activation error
|>thread-index: AceX6OlwrN1wFnsYTIiJFCtMaWOv5Q==
|>X-WBNR-Posting-Host: 67.67.39.128
|>From: =?Utf-8?B?Sm9lVC10ZWNo?= <[email protected]>
|>References: <[email protected]>
<DlozCb#[email protected]>
|>Subject: RE: Volume Licensing and Activation error
|>Date: Wed, 16 May 2007 11:35:00 -0700
|>Lines: 26
|>Message-ID: <[email protected]>
|>MIME-Version: 1.0
|>Content-Type: text/plain;
|> charset="Utf-8"
|>Content-Transfer-Encoding: 7bit
|>X-Newsreader: Microsoft CDO for Windows 2000
|>Content-Class: urn:content-classes:message
|>Importance: normal
|>Priority: normal
|>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2826
|>Newsgroups: microsoft.public.windows.vista.general
|>Path: TK2MSFTNGHUB02.phx.gbl
|>Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.vista.general:102359
|>NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
|>X-Tomcat-NG: microsoft.public.windows.vista.general
|>
|>Yes it does say something like that. the problem is that we already have
a
|>KMS server. Let me ask you this the key we were given is for KMS and we
have
|>attempted it on other machines. I did notice that if you do not enter a
key
|>during the setup "as volume activation does not require a key to be
entered
|>at that time" it is suppose to grab it from the PID.txt file found in
the
|>sources folder on the dvd. Well there is key specified there that does
not
|>match the one we were given could this have anything to do with it.
|>
|>We have already done 35 other machines and all this are contacting and
|>activating with the server with out problems. This is the first issue we
|>have experience with KMS activation.
|>
|>""Darrell Gorter[MSFT]"" wrote:
|>
|>> Hello Joe,
|>> It sounds like the wrong key was used on that machine and that it is
trying
|>> to activate against the Microsoft Servers rather than against the KMS
|>> server.
|>> Open an elevated cmd prompt:
|>> Run slmgr -dli
|>> It should say something similar to this if it's a kms client machine:
|>> Description: Windows Operating System - Vista, VOLUME_KMSCLIENT channel
|>>
|>> Thanks,
|>> Darrell Gorter[MSFT]
|>>
|>
Click to expand...
 
Back
Top