-
Notifications
You must be signed in to change notification settings - Fork 99
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
KMS server discovery #45
Comments
Hi,
As a final step (to determine if the problem is on py-kms or your network), try to use Wireshark and see if Windows is really sending out packets to the py-kms host and if the py-kms host is even receiving it (and replying). Please post your results (and anonymize them!) for further investigation. Thanks! |
I believe what might be happening here is that you've created a record in your DNS server with the correct prefix, however you've provided no domain suffix. In the NSLOOKUP which returns successfully you do not provide a suffix and nor do you on the /skms example. I suspect that your DHCP server is providing a DNS suffix Windows is appending and subsequently the vlmcs lookup is never hitting the record you created in PiHole. Can you enable detailed request logging in PiHole and provide DNS server logs of the vlmcs request make by /ato? |
I was able to do a couple of quick changes and tests. Things are hectic here. :) I changed the hostname to the IPv4 address, no change in the results. I also tried wireshark and didn't seen any traffic going to the IPv4 address of the kms server regardless of using the IPv4 address or hostname in the KMS DNS entry. I also added a bogus DNS suffix to the client and the error message was different when trying to auto-activate. It indicated the KMS server could not be found. Just for the heck of it, I did The client is running inside a VMWare Workstation VM with a bridged network connection. Perhaps this makes a difference. |
I believe you should still see something, can you filter in Wireshark by |
btw its not /skms it is /skms-domain for autodiscovery via dns in slmgr
slmgr.vbs /ckms kms.poo this hould fix your problem. |
So it is NOT sending packets or requests to the KMS server until it is specified on the client with I'm starting to agree - using the DNS entry for KMS auto-discovery probably requires being part of a Windows domain. I'm thinking if you try to activate it before specifying the KMS server manually, even though there is a DNS entry, the client tries to request something from a domain first and then is directed to the KMS server? I am trying to get it to activate out of the box without having to run any 'slmgr' command. I used |
For this to work you indeed need to be in a AD. But you can create a custom image with the skms-domain flag set as a group policy |
Soooo.... Should we close this or do we need to add something to the documentation? |
Either way, this issue is deployment-dependent and related to Windows discovery of KMS servers and certainly out of the scope of this project to assist. |
I added a DNS record for py-kms in pihole using the method shown here. Linkie
A fresh install of Win 10 Pro on the client machine using the VL key provided by MS it is not activated automatically.
Running
nslookup -type=srv _vlmcs._tcp
from the client machine shows the py-kms server.I enter the key again manually using
slmgr /ipk VLKEY
just to make sure it is correct.Running
slmgr /ato
gives the following error (see attached screencaps)If I specify the kms server using
slmgr /skms mykms.server
then runslmgr /ato
it activates successfully.Am I doing something wrong?
Thank you for your time.
BTW I am using the latest py-kms
The text was updated successfully, but these errors were encountered: