Confused about some of the defaults about py-kms HOT 4 CLOSED

Okay, according to

Regarding the client count... Maybe somewhere else in the code...

I'll update the docs when someone could explain this (and this person will not update the docs by herself)...

from py-kms.

I just looked into the code again and found this part that seems to explain what happens with the clientcount:

Looks like "none" actually means (according to the comment) 10 clients for Server versions and 50 for Desktop versions (or, 2x the minimum activation count).

Still wondering about the HWID though, is it at any point transmitted to the client or is that just the ePID (which is randomized by default)?

from py-kms.

The initial versions of py-kms had a "randomHWID.py", then fork-by-fork
this small code was introduced directly in "server.py".
Its use was intended to help the user to create the HWID string (and now with -w option), but
just for once, so you have to always reuse the same value.
Technically you should put real values for HWID and EPID, which come from a real KMS server,
otherwise your emulated server doesn't acts as much as possible as a real one.

In a local context doesn't seem to affect clients activations
(maybe when updating, some KB package can reveal that a client was activated by a not original server ??? I think not, but i don't know.).
Instead if you want to make public your KMS server you have some more problems, since can be marked by M$ as not genuine and stopped/banned.
So random HWID and EPID generation are not the best (but they are the original algorithms so as long as they work... i left them untouched).
See for details "vlmcsd" -r0, -r1, -r2 options.
Could be added something similar for py-kms.
Other info: https://forums.mydigitallife.net/threads/a-couple-questions-regarding-the-various-kms-tools.51662/

from py-kms.

Thanks for the explanation - in combination with the notes in the docs, I've now got a pretty clear picture of how it works! 👍

from py-kms.