Using Server 2012 R2 Essentials with a Fuji slic 2.3 in the bios, certificate & self generated key it activated fine with no problems. But looking in the event log every few minutes I'm getting ... SERVER1058WarningMicrosoft-Windows-Security-SPP Application Installation of the Proof of Purchase from the ACPI table failed. Error code: 0xC004F057 It's not entirely happy It seems to be looking for the (non existent) firmware key corresponding to the one I've entered. 0xC004F057 is fatal on Win7 and maybe in the future more serious for 2012 R2. Has anyone been getting these events or am I just unlucky on the key I generated?
Getting the same thing on 2012 R2 DC. I suspect the reason is a missing MSDM table within ACPI - I would bet that for this to be "proper" you need both the SLIC table and an MSDM containing an OEM:SLP key. Anyone got any guides to modifying UEFI to have an MSDM?
I'd try your assumption on a vm since vm bioses can be modified to have both tables.... So you guess M$ tries to find a generic SLP key at MSDMtable? Which is originally made to supply the DM channel?
Two questions: 1) Only a specific key will work with a specific BIOS now? 2) Can a loader (like the one Daz made) add the key properly to memory?
What event would this error be in? Application? And what would be the timespan for it to be created, don't have this warning message (yet) FYI, i am using a OEM:SLP key which (i think) is genuine and not a generated key
OK i'll keep monitoring this for a liitle while, still looks good though. Modded Hyper-V vmwp.exe, running Windows Server 2012 R2 Standard Code: Table NameOEMID&TableIDAddress LenthDescription Table (ACPI 1.0) RSD PTR ACPIAM 000F56F0 20Root System Desc.Pointer | |- RSDTFUJ PC 7FFF0000 68Root System Desc.Table | 00 |- FACP FUJ PC 7FFF0200 129 01 |- MSDM FUJ PC 000FF200 85 (This contains the OEM:SLP key) 02 |- WAET FUJ PC 7FFF1480 40 * 03 |- SLIC FUJ PC 7FFF14C0 374Software Licensing Desc.Table 04 |- OEM0 FUJ PC 7FFF16C0 100 05 |- SRAT FUJ PC 7FFF0600 240 06 |- APIC FUJ PC 7FFF0300 588 07 |- OEMB FUJ PC 7FFFF040 100 --- Scan Finished ---
If this is true, obviously MS has found a way to distinguish between a valid and generated OEM:SLP key The OEM:SLP (see signature) collection is being flooded with generated OEM:SLP keys, but if you look closely you should be able to find the 'real' ones (go to page 32/37, then reverse order by ID)
Sorry to bother you, but the site seems extremely slow from my end. Do you mean the Server 2012 keys??
Well, I'd assume they're lazy to bother renaming the table just for OEM:SLP, but who knows. any pointers as to how I can go about inserting an MSDM into the VMWare BIOS?
One thing i am sure of is that the MSDM table is being read by Windows Setup, with MSDM containing OEM:SLP for Server 2012 R2 Standard Key the only choice i got during installation Is Windows Server 2012 R2 Standard w/o GUI But Server DataCenter w/o GUI is not listed as it normally would without MSDM table using 'en_windows_server_2012_r2_x64_dvd_2707946.iso' as installation media. I am currently running a test on my Hyper-V box, but this time with a generated OEM:SLP key.... i'll update this post if i got some results UPDATE No problem whatsoever with generated key as well, could be a valid MSDM table requirement
So without an MSDM table it logs an error, but activation works. Doesn't it also log errors with Windows 8 if you take an OEM DM key and install it onto another system via phone activation? I could have sworn it logs an error yet the system remains activated I'm still waiting for a real key to be leaked before I update the loader app. I don't know if I'll include an MSDM table or not. I could do since I've still got a version of the loader that injects an MSDM from back when I was playing around with the Windows 8 stuff.