A12 is what you need ! Code: Product Key : VT8JD Validity : Valid Product ID : 00257-80000-00000-AAOEM Activation ID : 2994120e-2119-47df-b779-076c79acc297 Edition Type : ServerSolution Description : Windows Server Essentials 2012 R2 RTM ServerSolution OEM:SLP Edition ID : X18-90815 Key Type : OEM:SLP Crypto ID : 2578 (2578 dec = A12 hex)
Thanks mate I worked my way one at a time from 9E2 to the low A0's That'll teach me not to give up to easily
I found A12 value nearly the same way you did ! Just took shorter path since I first checked MS official GVLK against FreeStyler's pidChecker to obtain a more precise range where to search your desired SKU/CryptoID ! LostED link to PKeyConfig Reader seems to be a smarter choice... Thx !
Hello All, I've been reading through this stuff and got all the tools hinted at by the various posters. I go my BIOS already updated with Slic 2.3 so that's no hurdle for me. However I am looking for the Windows server 2012 R2 Standard groupID. When using the product key tool discussed to open one of them XML files I just get one line with very little info, definitely no group ID as far as I can tell (see picture below): View attachment 25609 Could anyone pass me a hint as to what I am missing or doing wrong ? Thanks in any event to everyone is this great community !
I think I read its encrypted with 'Base64' or something like that. I don't really understand coding or encryption, so hopefully someone who knows what their talking about can help there. But hints I can do, try 9da That should give you a Standard SLP key
True, but how do you think about 50% for all currently known OEM:SLP keys ended up being leaked here Anyway I removed OEM:SLP for Server 2012 R2 from online collection for now as the most were generated keys
So, just to clarify; when you use a proper 2012 key, it doesn't cause this event log warning? If that's the case then Windows OEM:SLP must care about the keyid and/or the secret. I did try a 2012 R2 key using a KeyID and secret taken from the 2008 key on page 1 but to no avail.
Can I use the keys for Windows Server 2012 R2, too? I would really need one for the Standard R2 Edition.
I understand that people have generated keys (they understand the PID decoding thread where I get lost). I am assuming nobody is sharing it due to something in the American DMCA? Most of us would temporarily get by with it, as we have leaked SLIC for Fujitsu. ??