- Remove From My Forums
Answered by:
Question
-
Hi
Currently, my Windows 7 client is connecting correctly to the KMS Server. Is there a way to check which KMS Server and the IP address the client is connecting to from the client side?
Thanks
Answers
-
Hi,
You should be able to find the KMS server reference in the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SoftwareProtectionPlatform
Look for the KeyManagementServiceName data and this should return your KMS server. Do a ping of this and it should then return you the IP address of the KMS server.
Regards,
Salvador Manaois III
MCSE MCSA MCTS MCITP:EA/SA C|EH CIWA
----------------------------------------------------------------------------
Bytes & Badz: http://badzmanaois.blogspot.com
My Passion: http://flickr.com/photos/badzmanaois
My Scripting Blog: http://sgwindowsgroup.org/blogs/badzWednesday, April 21, 2010 5:12 AM
-
Run "slmgr /dlv" and you will get the KMS host name.
- Marked as answer by cyw77 Friday, April 23, 2010 6:24 AM
Thursday, April 22, 2010 3:07 AM
All replies
-
Hi,
You should be able to find the KMS server reference in the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SoftwareProtectionPlatform
Look for the KeyManagementServiceName data and this should return your KMS server. Do a ping of this and it should then return you the IP address of the KMS server.
Regards,
Salvador Manaois III
MCSE MCSA MCTS MCITP:EA/SA C|EH CIWA
----------------------------------------------------------------------------
Bytes & Badz: http://badzmanaois.blogspot.com
My Passion: http://flickr.com/photos/badzmanaois
My Scripting Blog: http://sgwindowsgroup.org/blogs/badzWednesday, April 21, 2010 5:12 AM
-
Hi
I managed to navigate to the correct part but do not have the KeyManagementServiceNamedisplayed there.
Thanks
Wednesday, April 21, 2010 5:54 AM
-
Run "slmgr /dlv" and you will get the KMS host name.
- Marked as answer by cyw77 Friday, April 23, 2010 6:24 AM
Thursday, April 22, 2010 3:07 AM
-
Hi Tim
Nothing is found. Here is the result.
C:\Windows\system32>cscript slmgr.vbs /dlv
Microsoft (R) Windows Script Host Version 5.7
Copyright (C) Microsoft Corporation. All rights reserved.Software licensing service version: 6.0.6002.18005
Name: Windows Server(R), ServerStandard edition
Description: Windows Operating System - Windows Server(R), VOLUME_MAK_B channel
Activation ID: bb1d27c4-959d-4f82-b0fd-c02a7be54732
Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
Extended PID: 55041-00152-186-005547-03-3081-6002.0000-1042010
Installation ID: 020165480925906953062285886542905022320711159940746770
Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=48189
Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=48190
Use License URL: http://go.microsoft.com/fwlink/?LinkID=48192
Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=48191
Partial Product Key: CXMVY
License Status: LicensedThursday, April 22, 2010 5:41 AM
-
Hi,
According to this line:
“Description: Windows Operating System - Windows Server(R), VOLUME_MAK_B channel”,
you are using a MAK key instead of KMS. MAK activation does not need a host.
Tim Quan - MSFT
Thursday, April 22, 2010 6:01 AM
As an enthusiast deeply entrenched in the realm of Windows Server systems, I can confidently address the inquiry about identifying the KMS Server and its IP address from a Windows 7 client. My extensive expertise in Windows Server environments positions me to dissect and elaborate on the provided interaction between the user and the community of experts in the Windows Server General Forum.
The user sought guidance on locating the KMS Server and its corresponding IP address from a Windows 7 client. Salvador Manaois III promptly stepped in with a detailed response, directing the user to the registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SoftwareProtectionPlatform. Here, the KeyManagementServiceName data would unveil the KMS server. Salvador went a step further, advising a ping operation on the revealed KMS server to obtain its IP address.
Another contributor, not to be outdone, suggested a different approach. The command "slmgr /dlv" was proposed, promising to reveal the KMS host name. This concise yet effective solution was later marked as the answer by another user, indicating its accuracy and reliability.
However, the plot thickened as a user reported difficulty in finding the KeyManagementServiceName in the specified registry key. This prompted further troubleshooting, with Salvador Manaois III reinforcing the initial advice.
The climax of the discourse unfolded when a user attempted the "slmgr /dlv" command but encountered an unfruitful outcome. Tim Quan from Microsoft stepped in with a discerning analysis of the situation. Notably, Tim pointed out that the user was utilizing a MAK (Multiple Activation Key) instead of a KMS, evidenced by the line: "Description: Windows Operating System - Windows Server(R), VOLUME_MAK_B channel." This revelation was pivotal, clarifying that MAK activation doesn't necessitate a host.
In summary, the collective expertise exhibited in this exchange showcases a profound understanding of Windows Server activation mechanisms. The contributors demonstrated not only a comprehensive knowledge of registry keys and command-line tools but also an acute awareness of the distinctions between KMS and MAK activation methods. This interaction is a testament to the vibrant and informed community that surrounds Windows Server technologies.
