KMS - How to prevent a client machine acting as a KMS host

We are a large secondary school in Glasgow and are rolling out Vista
Enterprise to a subset of our desktops, around 300. We have installed
and configured KMS server on one of our Windows Server 2003 R2
machines. Using the <slmgr.vbs> tool we can successfully activate our
machines against this W2K3 server. However, on reviewing the DNS
records we noted that a number of our Vista clients hyas actually
registered as KMS hosts, and had corresponding _VLMCS records in DNS.
On checking each of these machines we confirmed that they were indeed
running the KMS license service - effectively activating other KMS
clients on our infrastructure.

I can find no documentation which explains how to change the machine
from acting as a "KMS host" back to being a "KMS client". We've run
the slmgr.vbs script to uninstall the product key and rearm the
machine but it keeps coming back as a "KMS host".

Any help much appreciated.

Jonathan Caddy
Computing Services Manager
Hutchesons Grammar School, Glasgow UK

Hello Jonathan,
You need to change the machine running as KMS hosts back to KMS clients.
You need to install the generic vl key located in the PID.txt on the DVD
open an elevated CMD prompt
This is the FAQ at the link below. the setup key listed below is the
product key in PID.txt on the Volume License media DVD
http://www.microsoft.com/technet/win...px?info=EXLINK

Q. I inadvertently ran the slmgr.vbs –ipk script using a KMS key on several
computers. How do I convert them back to KMS clients?
A. Run slmgr.vbs -ipk <setup key>. Remember to delete any unnecessary SRV
resource records from DNS if applicable and restart the computers.


Thanks,
Darrell Gorter[MSFT]

This posting is provided "AS IS" with no warranties, and confers no rights
--------------------
|> From: "" <>
|> Newsgroups: microsoft.public.windows.vista.general
|> Subject: KMS - How to prevent a client machine acting as a KMS host
|> Date: Fri, 20 Jul 2007 04:48:59 -0700
|> Organization: http://groups.google.com
|> Lines: 22
|> Message-ID: <. com>
|> NNTP-Posting-Host: 62.49.244.210
|> Mime-Version: 1.0
|> Content-Type: text/plain; charset="iso-8859-1"
|> X-Trace: posting.google.com 1184932140 3187 127.0.0.1 (20 Jul 2007
11:49:00 GMT)
|> X-Complaints-To: groups-
|> NNTP-Posting-Date: Fri, 20 Jul 2007 11:49:00 +0000 (UTC)
|> User-Agent: G2/1.0
|> X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0;
SLCC1; .NET CLR 2.0.50727; .NET CLR 3.0.04506;
InfoPath.1),gzip(gfe),gzip(gfe)
|> Complaints-To: groups-
|> Injection-Info: 57g2000hsv.googlegroups.com; posting-host=62.49.244.210;
|> posting-account=ps2QrAMAAAA6_jCuRt2JEIpn5Otqf_w0
|> Path:
TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSF TFEEDS02.phx.gbl!msrtrans!
msrn-in!newshub.sdsu.edu!postnews.google.com!57g2000hsv .googlegroups.com!not
-for-mail
|> Xref: TK2MSFTNGHUB02.phx.gbl
microsoft.public.windows.vista.general:138482
|> X-Tomcat-NG: microsoft.public.windows.vista.general
|>
|> We are a large secondary school in Glasgow and are rolling out Vista
|> Enterprise to a subset of our desktops, around 300. We have installed
|> and configured KMS server on one of our Windows Server 2003 R2
|> machines. Using the <slmgr.vbs> tool we can successfully activate our
|> machines against this W2K3 server. However, on reviewing the DNS
|> records we noted that a number of our Vista clients hyas actually
|> registered as KMS hosts, and had corresponding _VLMCS records in DNS.
|> On checking each of these machines we confirmed that they were indeed
|> running the KMS license service - effectively activating other KMS
|> clients on our infrastructure.
|>
|> I can find no documentation which explains how to change the machine
|> from acting as a "KMS host" back to being a "KMS client". We've run
|> the slmgr.vbs script to uninstall the product key and rearm the
|> machine but it keeps coming back as a "KMS host".
|>
|> Any help much appreciated.
|>
|> Jonathan Caddy
|> Computing Services Manager
|> Hutchesons Grammar School, Glasgow UK
|>
|>