Server 2012 R2 + SLIC 2.3 + Generated Key - potential issue?

Discussion in 'Windows Server' started by Ozymandias, Dec 7, 2013.

  1. Ozymandias

    Ozymandias MDL Junior Member

    Jun 17, 2008
    65
    25
    0
    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?
     
  2. Tito

    Tito Super Mod / Adviser
    Staff Member

    Nov 30, 2009
    17,636
    15,551
    340
    The error is same when you install & activate using a MSDM key taken from a OEM PC.

    :eek:
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. Sirchurchy

    Sirchurchy MDL Novice

    Oct 23, 2010
    16
    5
    0
    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?
     
  4. genuineintel

    genuineintel MDL Member

    Apr 28, 2009
    228
    25
    10
    Is there an MSDM table in old BIOS?
     
  5. Yen

    Yen Admin
    Staff Member

    May 6, 2007
    11,238
    11,054
    340
    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?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  6. Sabresite

    Sabresite MDL Member

    Nov 7, 2007
    210
    47
    10
    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?
     
  7. FreeStyler

    FreeStyler MDL Guru

    Jun 23, 2007
    3,504
    3,619
    120
    #7 FreeStyler, Dec 11, 2013
    Last edited: Dec 11, 2013
    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
     
  8. Ozymandias

    Ozymandias MDL Junior Member

    Jun 17, 2008
    65
    25
    0
    In Windows Logs/Application at least once an hour.
     
  9. Tito

    Tito Super Mod / Adviser
    Staff Member

    Nov 30, 2009
    17,636
    15,551
    340
    Care to 'leak' it??
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  10. FreeStyler

    FreeStyler MDL Guru

    Jun 23, 2007
    3,504
    3,619
    120
    #10 FreeStyler, Dec 11, 2013
    Last edited by a moderator: Apr 20, 2017
    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 ---
    
     
  11. FreeStyler

    FreeStyler MDL Guru

    Jun 23, 2007
    3,504
    3,619
    120
    #11 FreeStyler, Dec 11, 2013
    Last edited: Dec 11, 2013
    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)
     
  12. Tito

    Tito Super Mod / Adviser
    Staff Member

    Nov 30, 2009
    17,636
    15,551
    340
    Sorry to bother you, but the site seems extremely slow from my end.

    Do you mean the Server 2012 keys??
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  13. Sirchurchy

    Sirchurchy MDL Novice

    Oct 23, 2010
    16
    5
    0
    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?
     
  14. Tito

    Tito Super Mod / Adviser
    Staff Member

    Nov 30, 2009
    17,636
    15,551
    340
    http://forums.mydigitallife.net/threads/46845
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  15. FreeStyler

    FreeStyler MDL Guru

    Jun 23, 2007
    3,504
    3,619
    120
    No Server 2012 R2 Keys, not available through dropdown selectbox (yet)
     
  16. FreeStyler

    FreeStyler MDL Guru

    Jun 23, 2007
    3,504
    3,619
    120
    #16 FreeStyler, Dec 12, 2013
    Last edited: Dec 12, 2013
    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
     
  17. maggreg

    maggreg MDL Novice

    Sep 5, 2008
    1
    0
    0
    I think "Edition ID" is a clue.
    res-v2522 -> ok
    X18-90712 -> SERVER 1058 Warning

    pzdr
    maggreg
     
  18. Ozymandias

    Ozymandias MDL Junior Member

    Jun 17, 2008
    65
    25
    0
    I've just tried a res-v2578 key and I'm still getting the event.
     
  19. FreeStyler

    FreeStyler MDL Guru

    Jun 23, 2007
    3,504
    3,619
    120
    You have MSDM ACPI table holding that key?
     
  20. Daz

    Daz MDL Developer / Admin
    Staff Member

    Jul 31, 2009
    9,488
    66,571
    300
    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 :g:

    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.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...