Then I wonder (yes again) how keys are made. I expected it to be a 1 direction only process to go from key to XXX-XXXXXX-XX. But it would be a massive coincidence that the exactly the default key gives all 0s. So MS must have a non-brute-froce method of saying: create us a key that gives all 0s in the ePID. So it should be possible to generate a key for any given ePID. Not that this can be usefull in any way as our generated host keys can never be used to activate a kms host, cause they do have to be in MS' whitelist.
At least in the case of Windows XP, product key - product ID was certainly reversible, at least for MS. For XP, the product key encoded two numbers: a serial number (of sorts), and a cryptographic hash. The product ID was created from the serial number in a deterministic and reversible fashion. If you read the product ID, you could tell what the serial number is. Only MS could generate the appropriate cryptographic hash to go with it though (and therefore the complete product key), but it was certainly a reversible process. I am not familiar with the structure of the product key/product ID on Windows 7 and 8, so I don't know if this is still true.
Why release a KMS key and block it a few years later ? i don't understand . Now MS has to release a new KMS key for W7 Enterprise ? or ?
The client key is the same on all systems, but isn't blocked. The host key is unique for each company that uses kms, and the host key that leaked and was used for the windows 8 based vm's is blocked.
I just tried to check my activation and windows is telling me "your windows license will expire soon" - and the date is 12/05/13
Obviously. But now windows is complaining that it isnt activated??? s10.postimage. org/cqj2q1vfd/image.png s10.postimage. org/bpnfeo3tl/image.png
KMS clients are activated only for a duration of 180 days. After that, reactivation is a must if you want to stay genuine.
Normal behaviour as your KMS activated client is not able to contact the KMS Server it activated against. Your client by default would attempt to reactivate against the KMS server which you probably cleared using >slmgr -ckms
Hm, Moodle reported that expire date is sometimes next year May. So Notification mode comes when 180 days are over. When KMS is set to default doing ckms will not de-activate the OS, or does it? Afaik NO so there must be anything else running in the wrong direction ...
I activated with moo originally, but the server address got changed to 127.0.0.1 when i used the activation helper to check how long left i had on the activation
You will never know the truth unless you try try it out. If the validation fails, it means that the KMS host key used by moo ahs been blacklisted for good by M$. Currently, activation requests made against the KMS servers that run on the WS2012 KMS host keys pass the validation checks. But it's only a matter of time before M$ catches up !
that was the reason of my question as this can shoot the lights out at your activation. But you mentioned you are non-active. How come?
From my understanding people do not need to check their validation status, do they? We can activate against a 'bad' Win8 Host and never encounter problems if we pay attention to the updates and never run the validation check, right?