Eu fiquei sobrecarregado com a configuração dos Serviços de Gerenciamento de Chaves da MS para nossos sistemas. (Eu perdi a reunião ...)
A parte do servidor KMS parece ter sido instalada na caixa do servidor KMS e parece ter sido ativada, mas nenhum dos clientes é capaz de ativá-la e nem mesmo encontrá-la. Então, a primeira coisa que estou vendo é o DNS.
Na frente, aqui está o sintoma de um novo cliente winds2 (não configurado como um AD ou DNS ainda). Detalhes e exposição abaixo.
C:\>slmgr.vbs /dlv
C:\>nslookup -type=all _vlmcs._tcp
Server: winds1.ems.local
Address: 172.17.21.20
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to winds1.ems.local timed-out
Aqui está a configuração do sistema relevante
wsus3 -> KMS server 172.31.92.151/24 (a vmwware-convert of existing real live 2008R2 box acting as wsus server)
winds1 -> DNS server 172.17.21.20/24 (a vmware-convert of existing real live 2003 box)
winds2 -> win2008R2 172.17.21.21/24 -not- a DNS or AD box (yet). expecting to activate against wsus3
no winds2, [um dos] cliente KMS
C:>tcping.exe wsus3 1688
DNS: Could not find host wsus3, aborting.
C:>tcping.exe 172.31.92.151 1688
Probing 172.31.92.151:1688/tcp - Port is open - time=22.089ms Probing
172.31.92.151:1688/tcp - Port is open - time=14.074ms Probing 172.31.92.151:1688/tcp - Port is open - time=14.173ms Probing 172.31.92.151:1688/tcp - Port is open - time=14.033ms
Ping statistics for 172.31.92.151:1688
4 probes sent.
4 successful, 0 failed. Approximate trip times in milli-seconds:
Minimum = 14.033ms, Maximum = 22.089ms, Average = 16.092ms
C:>tcping.exe 172.17.21.20 53
Probing 172.17.21.20:53/tcp - Port is open - time=16.426ms Probing
172.17.21.20:53/tcp - Port is open - time=14.244ms Probing 172.17.21.20:53/tcp - Port is open - time=14.352ms Probing 172.17.21.20:53/tcp - Port is open - time=14.407ms
Ping statistics for 172.17.21.20:53
4 probes sent.
4 successful, 0 failed. Approximate trip times in milli-seconds:
Minimum = 14.244ms, Maximum = 16.426ms, Average = 14.857ms
C:>nslookup wsus3 Server: winds1.ems.local Address: 172.17.21.20
*** winds1.ems.local can't find wsus3: Server failed
C:>nslookup winds1 Server: winds1.ems.local Address: 172.17.21.20
*** winds1.ems.local can't find winds1: Server failed
C:>nslookup winds2 Server: winds1.ems.local Address: 172.17.21.20
*** winds1.ems.local can't find winds2: Server failed
C:>nslookup winds2. Server: winds1.ems.local Address: 172.17.21.20
*** winds1.ems.local can't find winds2.: Server failed
Portanto, há algo errado com o dns; não está resolvendo nomes (muito menos registros SRV), mas logo acima indica que o cliente ventos2 pode se conectar ao endereço IP e a porta DNS no servidor DNS ventos1
No entanto, dentro do servidor DNS 1, não há problema:
C:>nslookup -type=all _vlmcs._tcp Server: winds1.ems.local Address:
172.17.21.20
_vlmcs._tcp.EMS.LOCAL SRV service location:
priority = 0
weight = 0
port = 1688
svr hostname = wsus3.ems.local wsus3.ems.local internet address = 172.31.92.151
C:>ping wsus3
Pinging wsus3.EMS.LOCAL [172.31.92.151] with 32 bytes of data:
Reply from 172.31.92.151: bytes=32 time<1ms TTL=127 Reply from
172.31.92.151: bytes=32 time<1ms TTL=127 Reply from 172.31.92.151: bytes=32 time<1ms TTL=127 Reply from 172.31.92.151: bytes=32 time<1ms
TTL=127
Ping statistics for 172.31.92.151:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
C:>tcping.exe wsus3 1688
Probing 172.31.92.151:1688/tcp - Port is open - time=2.895ms Probing
172.31.92.151:1688/tcp - Port is open - time=2.124ms Probing 172.31.92.151:1688/tcp - Port is open - time=2.008ms Probing 172.31.92.151:1688/tcp - Port is open - time=2.122ms
Ping statistics for 172.31.92.151:1688
4 probes sent.
4 successful, 0 failed. Approximate trip times in milli-seconds:
Minimum = 2.008ms, Maximum = 2.895ms, Average = 2.287ms
C:>
Alguma opinião?
Eu configurei manualmente o DNS SRV por
link
Estou usando esses documentos (até agora) para configurar o KMS:
link
link
link