KMS clients do not contact the server

Hello,
I'm in the middle of my Vista deployment, I had a test KMS server runing
on a Windows2003 SP1 box. It worked (I got events in the KMS event viewer)
but because I did not reach my 25 Vista tests machines I left it runing until
I started the real deployment. And now surprise... The clients do not talk
to the KMS server (sysprep'd clients), the DNS records are correct, I tried
to add manually the KMS server in the registry "KeyManagementServiceName"
in WindowsNT\CurrentVersion\SL, I also tried slmgr -skms myserver.mydomain.com
(I used my real server name of course) that resulted in error 800706BA "RPC
not available" even if the port 1688 is open on the server - remember the
KMS server was working before...

I also tried installing another KMS 1.1 on a Windows 2003 SP2 box without
more success (the KMS setup runs smoothly) on the client side.
I ran a packet capture and found that the Vista Client does not even try
to connect to any server on port 1688, the only connection I can see is an
http to microsoft.com that fails because of our authentication proxy. By
the way the error I see in the event log on the clients is 8004FE33 (Proxy
auth) as long as IE is configured with our proxy and if I remove the proxy
config I get an 80072EFD unable to connect to server when I run slmgr -ato.

A warm welcome to any idea/direction


Patrick

Hello Patrick,
Open and elevated CMD prompt on the KMS client..
Run SLMGR -dlv
Report back with the output. ( remove an personal information that may be
displayed like server names( verify they are correct))
Thanks,
Darrell Gorter[MSFT]

This posting is provided "AS IS" with no warranties, and confers no rights
--------------------
|> Date: Mon, 7 Apr 2008 17:17:36 +0000 (UTC)
|> Message-ID: <b2fc1e512c038ca66fb2c3bcee0@msnews.microsoft.com>
|> From: Patrick Ambuhl <pambuhl@removemecia.ch>
|> Subject: KMS clients do not contact the server
|> MIME-Version: 1.0
|> Content-Transfer-Encoding: 8bit
|> Content-Type: text/plain; charset=iso-8859-1; format=flowed
|> X-Newsreader: JetBrains Omea Pro 1098.1
|> Newsgroups: microsoft.public.windows.vista.installation_setup
|> NNTP-Posting-Host: any.3.15.195.vtx.ch 195.15.3.220
|> Lines: 1
|> Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP02.phx.gbl
|> Xref: TK2MSFTNGHUB02.phx.gbl
microsoft.public.windows.vista.installation_setup:38286
|> X-Tomcat-NG: microsoft.public.windows.vista.installation_setup
|>
|> Hello,
|> I'm in the middle of my Vista deployment, I had a test KMS server runing
|> on a Windows2003 SP1 box. It worked (I got events in the KMS event
viewer)
|> but because I did not reach my 25 Vista tests machines I left it runing
until
|> I started the real deployment. And now surprise... The clients do not
talk
|> to the KMS server (sysprep'd clients), the DNS records are correct, I
tried
|> to add manually the KMS server in the registry
"KeyManagementServiceName"
|> in WindowsNT\CurrentVersion\SL, I also tried slmgr -skms
myserver.mydomain.com
|> (I used my real server name of course) that resulted in error 800706BA
"RPC
|> not available" even if the port 1688 is open on the server - remember
the
|> KMS server was working before...
|>
|> I also tried installing another KMS 1.1 on a Windows 2003 SP2 box
without
|> more success (the KMS setup runs smoothly) on the client side.
|> I ran a packet capture and found that the Vista Client does not even try
|> to connect to any server on port 1688, the only connection I can see is
an
|> http to microsoft.com that fails because of our authentication proxy. By
|> the way the error I see in the event log on the clients is 8004FE33
(Proxy
|> auth) as long as IE is configured with our proxy and if I remove the
proxy
|> config I get an 80072EFD unable to connect to server when I run slmgr
-ato.
|>
|> A warm welcome to any idea/direction
|>
|>
|> Patrick

|>
|>

Hi,
As you can see no server is displayed, the output is complete (did not remove
anything)

*******************************************************
C:\Users\AutoInstall.CIA>cscript c:\windows\system32\slmgr.vbs -dlv
Microsoft (R) Windows Script Host Version 5.7
Copyright (C) Microsoft Corporation 1996-2001. Tous droits réservés.

Version du service de licences logicielles : 6.0.6000.16386
Nom : Windows(TM) Vista, Business edition
Description : Windows Operating System - Vista, VOLUME_KMS channel
ID d'activation : 212a64dc-43b1-4d3d-a30c-2fc69d2095c6
ID d'application : 55c92734-d682-4d71-983e-d6ec3f16059f
PID étendu : 55041-00142-026-183041-03-4108-6000.0000-2472007
ID d'installation : 012293434733461634102900108633973410273790899226478994
URL du certificat du processeur : http://go.microsoft.com/fwlink/?LinkId=57201
URL du certificat de l'ordinateur : http://go.microsoft.com/fwlink/?LinkId=57203

URL de licence d'utilisation : http://go.microsoft.com/fwlink/?LinkId=57205
URL du certificat de clé de produit : http://go.microsoft.com/fwlink/?LinkId=57204
Clé de produit partielle : M8MBR
État de la licence : période de grâce initiale
Temps restant : 27660 minute(s) (19 jour(s))

********************************************************
Find also my nslookup :

C:\Users\AutoInstall.CIA>nslookup -type=srv _vlmcs._tcp
Serveur : srvexch-2003.domain.win
Address: xxx.53.48.250:53

_vlmcs._tcp.cia.win SRV service location:
priority = 0
weight = 0
port = 1688
svr hostname = win-util.domain.win
_vlmcs._tcp.cia.win SRV service location:
priority = 0
weight = 0
port = 1688
svr hostname = srvexch-2003.domain.win
win-util.domain.win internet address = xxx.53.48.253
srvexch-2003.domain.win internet address = xxx.53.48.250
srvexch-2003.domain.win internet address = yyy.168.207.1
srvexch-2003.cia.win internet address = yyy.168.228.1


Thanks for your help

Patrick


> Hello Patrick,
> Open and elevated CMD prompt on the KMS client..
> Run SLMGR -dlv
> Report back with the output. ( remove an personal information that may
> be
> displayed like server names( verify they are correct))
> Thanks,
> Darrell Gorter[MSFT]
> This posting is provided "AS IS" with no warranties, and confers no
> rights
> --------------------
> |> Date: Mon, 7 Apr 2008 17:17:36 +0000 (UTC)
> |> Message-ID: <b2fc1e512c038ca66fb2c3bcee0@msnews.microsoft.com>
> |> From: Patrick Ambuhl <pambuhl@removemecia.ch>
> |> Subject: KMS clients do not contact the server
> |> MIME-Version: 1.0
> |> Content-Transfer-Encoding: 8bit
> |> Content-Type: text/plain; charset=iso-8859-1; format=flowed
> |> X-Newsreader: JetBrains Omea Pro 1098.1
> |> Newsgroups: microsoft.public.windows.vista.installation_setup
> |> NNTP-Posting-Host: any.3.15.195.vtx.ch 195.15.3.220
> |> Lines: 1
> |> Path:
> TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP02.phx.gbl
> |> Xref: TK2MSFTNGHUB02.phx.gbl
> microsoft.public.windows.vista.installation_setup:38286
> |> X-Tomcat-NG: microsoft.public.windows.vista.installation_setup
> |>
> |> Hello,
> |> I'm in the middle of my Vista deployment, I had a test KMS server
> runing
> |> on a Windows2003 SP1 box. It worked (I got events in the KMS event
> viewer)
> |> but because I did not reach my 25 Vista tests machines I left it
> runing
> until
> |> I started the real deployment. And now surprise... The clients do
> not
> talk
> |> to the KMS server (sysprep'd clients), the DNS records are correct,
> I
> tried
> |> to add manually the KMS server in the registry
> "KeyManagementServiceName"
> |> in WindowsNT\CurrentVersion\SL, I also tried slmgr -skms
> myserver.mydomain.com
> |> (I used my real server name of course) that resulted in error
> 800706BA
> "RPC
> |> not available" even if the port 1688 is open on the server -
> remember
> the
> |> KMS server was working before...
> |>
> |> I also tried installing another KMS 1.1 on a Windows 2003 SP2 box
> without
> |> more success (the KMS setup runs smoothly) on the client side.
> |> I ran a packet capture and found that the Vista Client does not
> even try
> |> to connect to any server on port 1688, the only connection I can
> see is
> an
> |> http to microsoft.com that fails because of our authentication
> proxy. By
> |> the way the error I see in the event log on the clients is 8004FE33
> (Proxy
> |> auth) as long as IE is configured with our proxy and if I remove
> the
> proxy
> |> config I get an 80072EFD unable to connect to server when I run
> slmgr
> -ato.
> |>
> |> A warm welcome to any idea/direction
> |>
> |>
> |> Patrick
> |> |>
>

Hi,
find also the output on the KMS server :
****************************************************
C:\Documents and Settings\Administrateur.CIA>cscript c:\windows\system32\slmgr.vbs
-dlv
Microsoft (R) Windows Script Host Version 5.6
Copyright (C) Microsoft Corporation 1996-2001. Tous droits réservés.

Version du service de gestion de licences des logiciels : 6.0.6001.16476
Nom : Windows(TM) Server 2003 KMS, KmsW2k3Prs edition
Description : Windows(TM) Server 2003 KMS, VOLUME_KMS channel
ID d'activation : 212a64dc-43b1-4d3d-a30c-2fc69d2095c6
ID d'application : 55c92734-d682-4d71-983e-d6ec3f16059f
PID étendu : 55041-00142-026-183041-03-1036-3790.0000-2052007
ID d'installation : 014856212262383916449296166421314991078895836502452024
URL du certificat du processeur : http://go.microsoft.com/fwlink/?LinkId=78937
URL du certificat de l'ordinateur : http://go.microsoft.com/fwlink/?LinkId=78938

URL de licence d'utilisation : http://go.microsoft.com/fwlink/?LinkId=78940
URL du certificat de clé de produit : http://go.microsoft.com/fwlink/?LinkId=78939
Clé de produit partielle : M8MBR
État de la licence : avec licence

Le service Gestionnaire de clés est activé sur cet ordinateur
Décompte actuel : 0
Écoute sur le port : 1688
Publication DNS activée
Priorité KMS : normale
*******************************************************

Regards

Patrick

> Hello Patrick,
> Open and elevated CMD prompt on the KMS client..
> Run SLMGR -dlv
> Report back with the output. ( remove an personal information that may
> be
> displayed like server names( verify they are correct))
> Thanks,
> Darrell Gorter[MSFT]
> This posting is provided "AS IS" with no warranties, and confers no
> rights
> --------------------
> |> Date: Mon, 7 Apr 2008 17:17:36 +0000 (UTC)
> |> Message-ID: <b2fc1e512c038ca66fb2c3bcee0@msnews.microsoft.com>
> |> From: Patrick Ambuhl <pambuhl@removemecia.ch>
> |> Subject: KMS clients do not contact the server
> |> MIME-Version: 1.0
> |> Content-Transfer-Encoding: 8bit
> |> Content-Type: text/plain; charset=iso-8859-1; format=flowed
> |> X-Newsreader: JetBrains Omea Pro 1098.1
> |> Newsgroups: microsoft.public.windows.vista.installation_setup
> |> NNTP-Posting-Host: any.3.15.195.vtx.ch 195.15.3.220
> |> Lines: 1
> |> Path:
> TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP02.phx.gbl
> |> Xref: TK2MSFTNGHUB02.phx.gbl
> microsoft.public.windows.vista.installation_setup:38286
> |> X-Tomcat-NG: microsoft.public.windows.vista.installation_setup
> |>
> |> Hello,
> |> I'm in the middle of my Vista deployment, I had a test KMS server
> runing
> |> on a Windows2003 SP1 box. It worked (I got events in the KMS event
> viewer)
> |> but because I did not reach my 25 Vista tests machines I left it
> runing
> until
> |> I started the real deployment. And now surprise... The clients do
> not
> talk
> |> to the KMS server (sysprep'd clients), the DNS records are correct,
> I
> tried
> |> to add manually the KMS server in the registry
> "KeyManagementServiceName"
> |> in WindowsNT\CurrentVersion\SL, I also tried slmgr -skms
> myserver.mydomain.com
> |> (I used my real server name of course) that resulted in error
> 800706BA
> "RPC
> |> not available" even if the port 1688 is open on the server -
> remember
> the
> |> KMS server was working before...
> |>
> |> I also tried installing another KMS 1.1 on a Windows 2003 SP2 box
> without
> |> more success (the KMS setup runs smoothly) on the client side.
> |> I ran a packet capture and found that the Vista Client does not
> even try
> |> to connect to any server on port 1688, the only connection I can
> see is
> an
> |> http to microsoft.com that fails because of our authentication
> proxy. By
> |> the way the error I see in the event log on the clients is 8004FE33
> (Proxy
> |> auth) as long as IE is configured with our proxy and if I remove
> the
> proxy
> |> config I get an 80072EFD unable to connect to server when I run
> slmgr
> -ato.
> |>
> |> A warm welcome to any idea/direction
> |>
> |>
> |> Patrick
> |> |>
>

Hello Patrick,
The output is from two KMS server ( host machines)
These are not KMS client machines.
You should see this in the description:
Description: Windows Operating System - Vista, VOLUME_KMSCLIENT channel
You will need to convert them back to KMS_Client machines before they can
activate via the KMS host machine.
This is described in the technical documentation links in the following
article.
929712 Volume Activation information for Windows Vista
http://support.microsoft.com/defaul...kb;EN-US;929712


Thanks,
Darrell Gorter[MSFT]

This posting is provided "AS IS" with no warranties, and confers no rights
--------------------
|> Date: Tue, 8 Apr 2008 08:11:43 +0000 (UTC)
|> Message-ID: <b2fc1e512de68ca6778142a246a@msnews.microsoft.com>
|> From: Patrick Ambuhl <pambuhl@removemecia.ch>
|> Subject: RE: KMS clients do not contact the server
|> References: <zzbf$VQmIHA.4932@TK2MSFTNGHUB02.phx.gbl>
|> MIME-Version: 1.0
|> Content-Transfer-Encoding: 8bit
|> Content-Type: text/plain; charset=iso-8859-1; format=flowed
|> X-Newsreader: JetBrains Omea Pro 1098.1
|> Newsgroups: microsoft.public.windows.vista.installation_setup
|> NNTP-Posting-Host: any.3.15.195.vtx.ch 195.15.3.220
|> Lines: 1
|> Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP03.phx.gbl
|> Xref: TK2MSFTNGHUB02.phx.gbl
microsoft.public.windows.vista.installation_setup:38324
|> X-Tomcat-NG: microsoft.public.windows.vista.installation_setup
|>
|> Hi,
|> find also the output on the KMS server :
|> ****************************************************
|> C:\Documents and Settings\Administrateur.CIA>cscript
c:\windows\system32\slmgr.vbs
|> -dlv
|> Microsoft (R) Windows Script Host Version 5.6
|> Copyright (C) Microsoft Corporation 1996-2001. Tous droits réservés.
|>
|> Version du service de gestion de licences des logiciels : 6.0.6001.16476
|> Nom : Windows(TM) Server 2003 KMS, KmsW2k3Prs edition
|> Description : Windows(TM) Server 2003 KMS, VOLUME_KMS channel
|> ID d'activation : 212a64dc-43b1-4d3d-a30c-2fc69d2095c6
|> ID d'application : 55c92734-d682-4d71-983e-d6ec3f16059f
|> PID étendu : 55041-00142-026-183041-03-1036-3790.0000-2052007
|> ID d'installation :
014856212262383916449296166421314991078895836502452024
|> URL du certificat du processeur :
http://go.microsoft.com/fwlink/?LinkId=78937
|> URL du certificat de l'ordinateur :
http://go.microsoft.com/fwlink/?LinkId=78938
|>
|> URL de licence d'utilisation :
http://go.microsoft.com/fwlink/?LinkId=78940
|> URL du certificat de clé de produit :
http://go.microsoft.com/fwlink/?LinkId=78939
|> Clé de produit partielle : M8MBR
|> État de la licence : avec licence
|>
|> Le service Gestionnaire de clés est activé sur cet ordinateur
|> Décompte actuel : 0
|> Écoute sur le port : 1688
|> Publication DNS activée
|> Priorité KMS : normale
|> *******************************************************
|>
|> Regards
|>
|> Patrick
|>
|> > Hello Patrick,
|> > Open and elevated CMD prompt on the KMS client..
|> > Run SLMGR -dlv
|> > Report back with the output. ( remove an personal information that may
|> > be
|> > displayed like server names( verify they are correct))
|> > Thanks,
|> > Darrell Gorter[MSFT]
|> > This posting is provided "AS IS" with no warranties, and confers no
|> > rights
|> > --------------------
|> > |> Date: Mon, 7 Apr 2008 17:17:36 +0000 (UTC)
|> > |> Message-ID: <b2fc1e512c038ca66fb2c3bcee0@msnews.microsoft.com>
|> > |> From: Patrick Ambuhl <pambuhl@removemecia.ch>
|> > |> Subject: KMS clients do not contact the server
|> > |> MIME-Version: 1.0
|> > |> Content-Transfer-Encoding: 8bit
|> > |> Content-Type: text/plain; charset=iso-8859-1; format=flowed
|> > |> X-Newsreader: JetBrains Omea Pro 1098.1
|> > |> Newsgroups: microsoft.public.windows.vista.installation_setup
|> > |> NNTP-Posting-Host: any.3.15.195.vtx.ch 195.15.3.220
|> > |> Lines: 1
|> > |> Path:
|> > TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP02.phx.gbl
|> > |> Xref: TK2MSFTNGHUB02.phx.gbl
|> > microsoft.public.windows.vista.installation_setup:38286
|> > |> X-Tomcat-NG: microsoft.public.windows.vista.installation_setup
|> > |>
|> > |> Hello,
|> > |> I'm in the middle of my Vista deployment, I had a test KMS server
|> > runing
|> > |> on a Windows2003 SP1 box. It worked (I got events in the KMS event
|> > viewer)
|> > |> but because I did not reach my 25 Vista tests machines I left it
|> > runing
|> > until
|> > |> I started the real deployment. And now surprise... The clients do
|> > not
|> > talk
|> > |> to the KMS server (sysprep'd clients), the DNS records are correct,
|> > I
|> > tried
|> > |> to add manually the KMS server in the registry
|> > "KeyManagementServiceName"
|> > |> in WindowsNT\CurrentVersion\SL, I also tried slmgr -skms
|> > myserver.mydomain.com
|> > |> (I used my real server name of course) that resulted in error
|> > 800706BA
|> > "RPC
|> > |> not available" even if the port 1688 is open on the server -
|> > remember
|> > the
|> > |> KMS server was working before...
|> > |>
|> > |> I also tried installing another KMS 1.1 on a Windows 2003 SP2 box
|> > without
|> > |> more success (the KMS setup runs smoothly) on the client side.
|> > |> I ran a packet capture and found that the Vista Client does not
|> > even try
|> > |> to connect to any server on port 1688, the only connection I can
|> > see is
|> > an
|> > |> http to microsoft.com that fails because of our authentication
|> > proxy. By
|> > |> the way the error I see in the event log on the clients is 8004FE33
|> > (Proxy
|> > |> auth) as long as IE is configured with our proxy and if I remove
|> > the
|> > proxy
|> > |> config I get an 80072EFD unable to connect to server when I run
|> > slmgr
|> > -ato.
|> > |>
|> > |> A warm welcome to any idea/direction
|> > |>
|> > |>
|> > |> Patrick
|> > |> |>
|> >

|>
|>

Great,
It worked ! I missed the KMS client specific key, I guess I forgot to document
correctly the steps when I tested last year....

Anyway, many thanks for your help.


Patrick

> Hello Patrick,
> The output is from two KMS server ( host machines)
> These are not KMS client machines.
> You should see this in the description:
> Description: Windows Operating System - Vista, VOLUME_KMSCLIENT
> channel
> You will need to convert them back to KMS_Client machines before they
> can
> activate via the KMS host machine.
> This is described in the technical documentation links in the
> following
> article.
> 929712 Volume Activation information for Windows Vista
> http://support.microsoft.com/defaul...kb;EN-US;929712
> Thanks,
> Darrell Gorter[MSFT]
> This posting is provided "AS IS" with no warranties, and confers no
> rights
> --------------------
> |> Date: Tue, 8 Apr 2008 08:11:43 +0000 (UTC)
> |> Message-ID: <b2fc1e512de68ca6778142a246a@msnews.microsoft.com>
> |> From: Patrick Ambuhl <pambuhl@removemecia.ch>
> |> Subject: RE: KMS clients do not contact the server
> |> References: <zzbf$VQmIHA.4932@TK2MSFTNGHUB02.phx.gbl>
> |> MIME-Version: 1.0
> |> Content-Transfer-Encoding: 8bit
> |> Content-Type: text/plain; charset=iso-8859-1; format=flowed
> |> X-Newsreader: JetBrains Omea Pro 1098.1
> |> Newsgroups: microsoft.public.windows.vista.installation_setup
> |> NNTP-Posting-Host: any.3.15.195.vtx.ch 195.15.3.220
> |> Lines: 1
> |> Path:
> TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP03.phx.gbl
> |> Xref: TK2MSFTNGHUB02.phx.gbl
> microsoft.public.windows.vista.installation_setup:38324
> |> X-Tomcat-NG: microsoft.public.windows.vista.installation_setup
> |>
> |> Hi,
> |> find also the output on the KMS server :
> |> ****************************************************
> |> C:\Documents and Settings\Administrateur.CIA>cscript
> c:\windows\system32\slmgr.vbs
> |> -dlv
> |> Microsoft (R) Windows Script Host Version 5.6
> |> Copyright (C) Microsoft Corporation 1996-2001. Tous droits
> réservés.
> |>
> |> Version du service de gestion de licences des logiciels :
> 6.0.6001.16476
> |> Nom : Windows(TM) Server 2003 KMS, KmsW2k3Prs edition
> |> Description : Windows(TM) Server 2003 KMS, VOLUME_KMS channel
> |> ID d'activation : 212a64dc-43b1-4d3d-a30c-2fc69d2095c6
> |> ID d'application : 55c92734-d682-4d71-983e-d6ec3f16059f
> |> PID étendu : 55041-00142-026-183041-03-1036-3790.0000-2052007
> |> ID d'installation :
> 014856212262383916449296166421314991078895836502452024
> |> URL du certificat du processeur :
> http://go.microsoft.com/fwlink/?LinkId=78937
> |> URL du certificat de l'ordinateur :
> http://go.microsoft.com/fwlink/?LinkId=78938
> |>
> |> URL de licence d'utilisation :
> http://go.microsoft.com/fwlink/?LinkId=78940
> |> URL du certificat de clé de produit :
> http://go.microsoft.com/fwlink/?LinkId=78939
> |> Clé de produit partielle : M8MBR
> |> État de la licence : avec licence
> |>
> |> Le service Gestionnaire de clés est activé sur cet ordinateur
> |> Décompte actuel : 0
> |> Écoute sur le port : 1688
> |> Publication DNS activée
> |> Priorité KMS : normale
> |> *******************************************************
> |>
> |> Regards
> |>
> |> Patrick
> |>
> |> > Hello Patrick,
> |> > Open and elevated CMD prompt on the KMS client..
> |> > Run SLMGR -dlv
> |> > Report back with the output. ( remove an personal information
> that may
> |> > be
> |> > displayed like server names( verify they are correct))
> |> > Thanks,
> |> > Darrell Gorter[MSFT]
> |> > This posting is provided "AS IS" with no warranties, and confers
> no
> |> > rights
> |> > --------------------
> |> > |> Date: Mon, 7 Apr 2008 17:17:36 +0000 (UTC)
> |> > |> Message-ID: <b2fc1e512c038ca66fb2c3bcee0@msnews.microsoft.com>
> |> > |> From: Patrick Ambuhl <pambuhl@removemecia.ch>
> |> > |> Subject: KMS clients do not contact the server
> |> > |> MIME-Version: 1.0
> |> > |> Content-Transfer-Encoding: 8bit
> |> > |> Content-Type: text/plain; charset=iso-8859-1; format=flowed
> |> > |> X-Newsreader: JetBrains Omea Pro 1098.1
> |> > |> Newsgroups: microsoft.public.windows.vista.installation_setup
> |> > |> NNTP-Posting-Host: any.3.15.195.vtx.ch 195.15.3.220
> |> > |> Lines: 1
> |> > |> Path:
> |> > TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP02.phx.gbl
> |> > |> Xref: TK2MSFTNGHUB02.phx.gbl
> |> > microsoft.public.windows.vista.installation_setup:38286
> |> > |> X-Tomcat-NG: microsoft.public.windows.vista.installation_setup
> |> > |>
> |> > |> Hello,
> |> > |> I'm in the middle of my Vista deployment, I had a test KMS
> server
> |> > runing
> |> > |> on a Windows2003 SP1 box. It worked (I got events in the KMS
> event
> |> > viewer)
> |> > |> but because I did not reach my 25 Vista tests machines I left
> it
> |> > runing
> |> > until
> |> > |> I started the real deployment. And now surprise... The clients
> do
> |> > not
> |> > talk
> |> > |> to the KMS server (sysprep'd clients), the DNS records are
> correct,
> |> > I
> |> > tried
> |> > |> to add manually the KMS server in the registry
> |> > "KeyManagementServiceName"
> |> > |> in WindowsNT\CurrentVersion\SL, I also tried slmgr -skms
> |> > myserver.mydomain.com
> |> > |> (I used my real server name of course) that resulted in error
> |> > 800706BA
> |> > "RPC
> |> > |> not available" even if the port 1688 is open on the server -
> |> > remember
> |> > the
> |> > |> KMS server was working before...
> |> > |>
> |> > |> I also tried installing another KMS 1.1 on a Windows 2003 SP2
> box
> |> > without
> |> > |> more success (the KMS setup runs smoothly) on the client side.
> |> > |> I ran a packet capture and found that the Vista Client does
> not
> |> > even try
> |> > |> to connect to any server on port 1688, the only connection I
> can
> |> > see is
> |> > an
> |> > |> http to microsoft.com that fails because of our authentication
> |> > proxy. By
> |> > |> the way the error I see in the event log on the clients is
> 8004FE33
> |> > (Proxy
> |> > |> auth) as long as IE is configured with our proxy and if I
> remove
> |> > the
> |> > proxy
> |> > |> config I get an 80072EFD unable to connect to server when I
> run
> |> > slmgr
> |> > -ato.
> |> > |>
> |> > |> A warm welcome to any idea/direction
> |> > |>
> |> > |>
> |> > |> Patrick
> |> > |> |>
> |> >
> |> |>
>

Hello Patrick,
You are welcome
Thanks,
Darrell Gorter[MSFT]

This posting is provided "AS IS" with no warranties, and confers no rights
--------------------
|> Date: Fri, 11 Apr 2008 06:49:34 +0000 (UTC)
|> Message-ID: <c28cc670f978ca69c819bf2ba6@msnews.microsoft.com>
|> From: Patrick Ambuhl <pambuhl@removemecia.ch>
|> Subject: RE: KMS clients do not contact the server
|> References: <UbCUHxZmIHA.3756@TK2MSFTNGHUB02.phx.gbl>
|> MIME-Version: 1.0
|> Content-Transfer-Encoding: 8bit
|> Content-Type: text/plain; charset=iso-8859-1; format=flowed
|> X-Newsreader: JetBrains Omea Pro 1098.1
|> Newsgroups: microsoft.public.windows.vista.installation_setup
|> NNTP-Posting-Host: client-addr-140-18.edipresse.ch 194.209.140.18
|> Lines: 1
|> Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP06.phx.gbl
|> Xref: TK2MSFTNGHUB02.phx.gbl
microsoft.public.windows.vista.installation_setup:38455
|> X-Tomcat-NG: microsoft.public.windows.vista.installation_setup
|>
|> Great,
|> It worked ! I missed the KMS client specific key, I guess I forgot to
document
|> correctly the steps when I tested last year....
|>
|> Anyway, many thanks for your help.
|>
|>
|> Patrick
|>
|> > Hello Patrick,
|> > The output is from two KMS server ( host machines)
|> > These are not KMS client machines.
|> > You should see this in the description:
|> > Description: Windows Operating System - Vista, VOLUME_KMSCLIENT
|> > channel
|> > You will need to convert them back to KMS_Client machines before they
|> > can
|> > activate via the KMS host machine.
|> > This is described in the technical documentation links in the
|> > following
|> > article.
|> > 929712 Volume Activation information for Windows Vista
|> > http://support.microsoft.com/defaul...kb;EN-US;929712
|> > Thanks,
|> > Darrell Gorter[MSFT]
|> > This posting is provided "AS IS" with no warranties, and confers no
|> > rights
|> > --------------------
|> > |> Date: Tue, 8 Apr 2008 08:11:43 +0000 (UTC)
|> > |> Message-ID: <b2fc1e512de68ca6778142a246a@msnews.microsoft.com>
|> > |> From: Patrick Ambuhl <pambuhl@removemecia.ch>
|> > |> Subject: RE: KMS clients do not contact the server
|> > |> References: <zzbf$VQmIHA.4932@TK2MSFTNGHUB02.phx.gbl>
|> > |> MIME-Version: 1.0
|> > |> Content-Transfer-Encoding: 8bit
|> > |> Content-Type: text/plain; charset=iso-8859-1; format=flowed
|> > |> X-Newsreader: JetBrains Omea Pro 1098.1
|> > |> Newsgroups: microsoft.public.windows.vista.installation_setup
|> > |> NNTP-Posting-Host: any.3.15.195.vtx.ch 195.15.3.220
|> > |> Lines: 1
|> > |> Path:
|> > TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP03.phx.gbl
|> > |> Xref: TK2MSFTNGHUB02.phx.gbl
|> > microsoft.public.windows.vista.installation_setup:38324
|> > |> X-Tomcat-NG: microsoft.public.windows.vista.installation_setup
|> > |>
|> > |> Hi,
|> > |> find also the output on the KMS server :
|> > |> ****************************************************
|> > |> C:\Documents and Settings\Administrateur.CIA>cscript
|> > c:\windows\system32\slmgr.vbs
|> > |> -dlv
|> > |> Microsoft (R) Windows Script Host Version 5.6
|> > |> Copyright (C) Microsoft Corporation 1996-2001. Tous droits
|> > réservés.
|> > |>
|> > |> Version du service de gestion de licences des logiciels :
|> > 6.0.6001.16476
|> > |> Nom : Windows(TM) Server 2003 KMS, KmsW2k3Prs edition
|> > |> Description : Windows(TM) Server 2003 KMS, VOLUME_KMS channel
|> > |> ID d'activation : 212a64dc-43b1-4d3d-a30c-2fc69d2095c6
|> > |> ID d'application : 55c92734-d682-4d71-983e-d6ec3f16059f
|> > |> PID étendu : 55041-00142-026-183041-03-1036-3790.0000-2052007
|> > |> ID d'installation :
|> > 014856212262383916449296166421314991078895836502452024
|> > |> URL du certificat du processeur :
|> > http://go.microsoft.com/fwlink/?LinkId=78937
|> > |> URL du certificat de l'ordinateur :
|> > http://go.microsoft.com/fwlink/?LinkId=78938
|> > |>
|> > |> URL de licence d'utilisation :
|> > http://go.microsoft.com/fwlink/?LinkId=78940
|> > |> URL du certificat de clé de produit :
|> > http://go.microsoft.com/fwlink/?LinkId=78939
|> > |> Clé de produit partielle : M8MBR
|> > |> État de la licence : avec licence
|> > |>
|> > |> Le service Gestionnaire de clés est activé sur cet ordinateur
|> > |> Décompte actuel : 0
|> > |> Écoute sur le port : 1688
|> > |> Publication DNS activée
|> > |> Priorité KMS : normale
|> > |> *******************************************************
|> > |>
|> > |> Regards
|> > |>
|> > |> Patrick
|> > |>
|> > |> > Hello Patrick,
|> > |> > Open and elevated CMD prompt on the KMS client..
|> > |> > Run SLMGR -dlv
|> > |> > Report back with the output. ( remove an personal information
|> > that may
|> > |> > be
|> > |> > displayed like server names( verify they are correct))
|> > |> > Thanks,
|> > |> > Darrell Gorter[MSFT]
|> > |> > This posting is provided "AS IS" with no warranties, and confers
|> > no
|> > |> > rights
|> > |> > --------------------
|> > |> > |> Date: Mon, 7 Apr 2008 17:17:36 +0000 (UTC)
|> > |> > |> Message-ID: <b2fc1e512c038ca66fb2c3bcee0@msnews.microsoft.com>
|> > |> > |> From: Patrick Ambuhl <pambuhl@removemecia.ch>
|> > |> > |> Subject: KMS clients do not contact the server
|> > |> > |> MIME-Version: 1.0
|> > |> > |> Content-Transfer-Encoding: 8bit
|> > |> > |> Content-Type: text/plain; charset=iso-8859-1; format=flowed
|> > |> > |> X-Newsreader: JetBrains Omea Pro 1098.1
|> > |> > |> Newsgroups: microsoft.public.windows.vista.installation_setup
|> > |> > |> NNTP-Posting-Host: any.3.15.195.vtx.ch 195.15.3.220
|> > |> > |> Lines: 1
|> > |> > |> Path:
|> > |> > TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP02.phx.gbl
|> > |> > |> Xref: TK2MSFTNGHUB02.phx.gbl
|> > |> > microsoft.public.windows.vista.installation_setup:38286
|> > |> > |> X-Tomcat-NG: microsoft.public.windows.vista.installation_setup
|> > |> > |>
|> > |> > |> Hello,
|> > |> > |> I'm in the middle of my Vista deployment, I had a test KMS
|> > server
|> > |> > runing
|> > |> > |> on a Windows2003 SP1 box. It worked (I got events in the KMS
|> > event
|> > |> > viewer)
|> > |> > |> but because I did not reach my 25 Vista tests machines I left
|> > it
|> > |> > runing
|> > |> > until
|> > |> > |> I started the real deployment. And now surprise... The clients
|> > do
|> > |> > not
|> > |> > talk
|> > |> > |> to the KMS server (sysprep'd clients), the DNS records are
|> > correct,
|> > |> > I
|> > |> > tried
|> > |> > |> to add manually the KMS server in the registry
|> > |> > "KeyManagementServiceName"
|> > |> > |> in WindowsNT\CurrentVersion\SL, I also tried slmgr -skms
|> > |> > myserver.mydomain.com
|> > |> > |> (I used my real server name of course) that resulted in error
|> > |> > 800706BA
|> > |> > "RPC
|> > |> > |> not available" even if the port 1688 is open on the server -
|> > |> > remember
|> > |> > the
|> > |> > |> KMS server was working before...
|> > |> > |>
|> > |> > |> I also tried installing another KMS 1.1 on a Windows 2003 SP2
|> > box
|> > |> > without
|> > |> > |> more success (the KMS setup runs smoothly) on the client side.
|> > |> > |> I ran a packet capture and found that the Vista Client does
|> > not
|> > |> > even try
|> > |> > |> to connect to any server on port 1688, the only connection I
|> > can
|> > |> > see is
|> > |> > an
|> > |> > |> http to microsoft.com that fails because of our authentication
|> > |> > proxy. By
|> > |> > |> the way the error I see in the event log on the clients is
|> > 8004FE33
|> > |> > (Proxy
|> > |> > |> auth) as long as IE is configured with our proxy and if I
|> > remove
|> > |> > the
|> > |> > proxy
|> > |> > |> config I get an 80072EFD unable to connect to server when I
|> > run
|> > |> > slmgr
|> > |> > -ato.
|> > |> > |>
|> > |> > |> A warm welcome to any idea/direction
|> > |> > |>
|> > |> > |>
|> > |> > |> Patrick
|> > |> > |> |>
|> > |> >
|> > |> |>
|> >

|>
|>