VL2.0 KMS - has been installed on my workstation for some reason!

[Matthew M \(UK\)]

Hi,

For some reason the VL2.0 KMS has been activated on my vista machine. Any
way to get rid of this? It did not come to my attention until I installed
the KMS onto a 2003 server for proper implementation and found the resource
records in DNS registered from my machine!

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


Matthew

 

[Carey Frisch [MVP]]

Please discuss this matter with your internal systems administrator.

--
Carey Frisch
Microsoft MVP
Windows - Shell/User

--------------------------------------------------------------------------------

:

Hi,

For some reason the VL2.0 KMS has been activated on my vista machine. Any
way to get rid of this? It did not come to my attention until I installed
the KMS onto a 2003 server for proper implementation and found the resource
records in DNS registered from my machine!

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


Matthew

 

[Matthew M \(UK\)]

Hi,

I am, thats why i am asking here.

Thanks
Matthew

 

[Mike Brannigan]

Hi,

For some reason the VL2.0 KMS has been activated on my vista machine. Any
way to get rid of this? It did not come to my attention until I installed
the KMS onto a 2003 server for proper implementation and found the
resource records in DNS registered from my machine!

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


Matthew

Mathew,

What do you mean the KMS is running on your Vista machine.
The KMS is actually a service you see in Services as Software Platform
Protection Services (sppsvc), you are running a KMS only if that service is
installed a and activated.
Since you actually ran the Server 2003 SP1 package on a Server that is the
only place where that service will be running once you have activated the
KMS with your Key.
The KMS will then enable for activating clients once the n-count reaches 25.
Post install it will register the appropriate SRV records.

So I am a little confused as to what that leads you to beleiev that your PC
is hosting a KMS

 

[Guest]

Same problem here, I'm also the admin.

Would cscript c:\windows\system32\slmgr.vbs -upk <Volume License Key> work?

 

[Matthew M \(UK\)]

Hi,

I have read that if i use a KMS key and activate with that the KMS service
is automatically installed and started. I have since removed that key using
"slmgr.vbs -upk". I then activated using the MAK. Once we have 20 vista
machines online i will do the following to allow business edition to
register with the KMS which i setup...

Cscript c:\windows\system32\slmgr.vbs -ipk %key% (key is
vistamedia\sources\pid.txt)
Cscript c:\windows\system32\slmgr.vbs -ato

Matthew

 

[Mike Brannigan]

Hi,

I have read that if i use a KMS key and activate with that the KMS service
is automatically installed and started. I have since removed that key
using "slmgr.vbs -upk". I then activated using the MAK. Once we have 20
vista machines online i will do the following to allow business edition to
register with the KMS which i setup...

Cscript c:\windows\system32\slmgr.vbs -ipk %key% (key is
vistamedia\sources\pid.txt)
Cscript c:\windows\system32\slmgr.vbs -ato

Matthew

Mathew,

You install the KMS with its key - this allows the KMS to install and start.
You then need to give the KMS the VL key for the number of activation you
bought for Vista , to actually activate the Vista clients.
HOWEVER it will not actually activate ANY clients until there are 25 online
and waiting for activation (this is called the n-count and is covered in the
Activation 2.0 whitepapers at Microsoft.com which hopefully you have read).

I am also slightly confused about what you re actually trying to do as the
scripts you mention above are for running on a Vista client to change the
product key and activate - so this has nothing to do with KMS as the process
you outline is to use a MAK key to insert into a Vista client and then
activate.
These clients will then have nothing to do with your KMS.
KMS and MAK activation are two separate processes and mutually exclusive -
again covered in the white paper.

As an aside - it sounds like you used the wrong key on a client machine -
that would cause the "KMS enabled on this machine message" you mentioned in
your previous post.

The steps should be fairly straight forward.
Build you KMS on a Server 2003 SP1 system.
Activate it with its key and install the key for the number of activations
you are allowed to do as part of your VL with Microsoft
The KMS is then activate and waiting for its n-count to reach 25
Install your Vista business clients - you do not supply a product key - but
install your appropriate licensed product (Business or Enterprise etc).
Once installed they will activate with the KMS once 25 of them are on the
wire and contacting the KMS for activation (this "enables" the KMS)
Those 25 will then be activated and any future system will activate too - up
to the limit of the installed key on the KMS.

If I am still not getting the full picture please post back.