Did you activate it with a WS12-Class-KMS-Host? Could you tell me the first and last five characteres of the product key? Which guide did you follow to build your Server 2012 KMS Host? I'm not sure but I think the xxxxx-B4W3F has been blacklisted.
Thanks for the edit. My self-built Windows Server 2012 Standard in VirtualBox has identical ePID to yours, every digit of it. I compared the ePID of my WES7 KMS host in VirtualBox with my Windows 8 Pro x86 KMS host in VirtualBox. Both are based on the same product key, but different tokens of course. Their ePID are almost identical, like this: xxxxx-OOOOO-OOO-OOOOO-OO-xxxx-xxxx.OOOO-xxxOOOO The x-s are different, the O-s are the same. Another thing I compared is two fresh installations of Windows 8 Pro x86, on which I restored the KMS host token. They have identical ePID. It's not entirely obvious that that should be the case, but it's not surprising either. I'd imagine the entire ePID is stored in the tokens, so restoring it results in identical ePIDs. At this point I believe that there is enough constant information in the ePID for Microsoft to uniquely identify the leaked host.
It's been said in this thread already that so far it looks like that only a client activated against the leaked W8-channel host gets non-genuine status. A client activated against WS12-channel is so far safe, but who knows how long.
I tested AutoKMS from the Microsoft Toolkit made by CODY... and it is still GENUINE Does it mean M$ have a blacklist of Key/ePID but not a whitelist?
AFAIK AutoKMS is not a "genuine" KMS in the first place. It's a complete emulator and serves whatever PID is hardcoded into it.
That's what I though, so it probably means they are juste blacklisting keys, not whitelisting good key. So I suppose that the only solution will be a new KMS emulator for Windows 8
The poll that was just added doesn't make sense, there is no such thing as Server 2010. What is it meant to be?
Tested on windows 7 & 8. Result is M$ disabled activation from leaked W8 KMS host channel, Host activated from key B4W3F. If you activated your window from online KMS host then Run SLMGR /dli on client & check if ePID is same to this "KMS machine extended PID: XXXXX-XXXXX-199-002764-03-XXXXX-XXXX.0000-XXXXXXX" then validation check will result to Not Genuine on windows 7. Tried to validate Windows 8 too but M$ says that validation is not supported for this version of Windows. But for how long its safe? I know best method is to avoid those updates but who knows when M$ will mix those with other updates. Another thought is that they are just testing & validating OS online when user initiate it so they just want to prevent fraud with Genuine users who purchased it & will not force this validation test in future to all. headbang: ) But win7 activated from Toolkit successfully passed validation test. This mean they are behind W8 & newer activation methods only & did't blocked ePID of this tool. Any one expert here on activation can confirm that where client saves PID of host? (i guess ans will be tokens or data file) I am just looking for some deep detail on it to play with it on client machine. Me an many other permanently activated windows using free WMC key & activation method was KMS to WMC. If activation store still have that KMS HOST information then i think we will face problem. But who used other method than KMS to activate & then used WMC key, will be safe.
I really don't see how Microsoft is disableing KMS keys, Universal KMS keys may I add. It's almost on the same lines as an OEM:SLP key. The only thing I can think of that Microsoft could of done was give out a rough update via Windows Update to add a blacklist but I don't see that as likely....
You clearly didn't, judging by your post. If you just "glanced a couple posts", you shouldn't be trying to offer up wild guesses as "explanations".