SLP 1.0 activation in Hyper-V ???

Discussion in 'Windows Server' started by sebus, Sep 26, 2009.

  1. sebus

    sebus MDL Guru

    Jul 23, 2008
    5,895
    1,783
    180
    #1 sebus, Sep 26, 2009
    Last edited: Sep 28, 2009
    SLP 1.0 activation in Hyper-V ??? - SOLVED!

    W2K8 Ent SP2 (not R2!) activated on Dell PE 1950 with Dell Enterprise SLP key & certificate

    Installed Hyper-V role, created W2K3 R2 Virtual Machine using Dell original OEM media (that comes with SLP key already)

    I was expecting to need to modify Hyper-V BIOS, but the W2K3 R2 VM was instantly activated

    How did that happen? What was it activated with (obviously Dell oembios* set, but what SLP sring does it read from Hyper-V BIOS, or the host BIOS is being read in some passthrough way?)

    Thanks for explanation

    sebus
     
  2. morpheus00de

    morpheus00de MDL Novice

    Feb 14, 2008
    22
    1
    0
    W2k3 its the secret, using a VLK key ;)
    till 2003 VLK don't need activation...
     
  3. sebus

    sebus MDL Guru

    Jul 23, 2008
    5,895
    1,783
    180
    Of course if it was VLK then I would not be even asking. It is OEM as supplied with Dell Servers (blue disk in case you never saw one) - as stated in first post:

    ...W2K3 R2 VM using Dell original OEM media - VM means VirtualMachine

    sebus
     
  4. HSChronic

    HSChronic MDL Expert

    Aug 25, 2007
    1,213
    57
    60
    i think the SLP 1.0 table is in the modded BIOS too
     
  5. sebus

    sebus MDL Guru

    Jul 23, 2008
    5,895
    1,783
    180
    But I DO NOT have ANYTHING modded in this setup

    Host PowerEdge BIOS is Dell original & Hyper-V is just a default install

    sebus
     
  6. hspace

    hspace MDL Novice

    Sep 21, 2009
    8
    0
    0
    Windows 2003 VLK doesn't need activation :D
    You seem to have fooled yourself effectively while trying to fool others.
     
  7. Myrrh

    Myrrh MDL Expert

    Nov 26, 2008
    1,401
    500
    60
    but, he installed using OEM media which should be looking for SLP1.0 in bios. Hence his original question.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  8. sebus

    sebus MDL Guru

    Jul 23, 2008
    5,895
    1,783
    180
    Thank you, some people just can NOT read & simply assume things...

    No VLK anywhere near these machines (either host of VM)

    Yes, the question still stands, it is almost as the SLP from the host BIOS was passed through to the VM

    sebus
     
  9. HSChronic

    HSChronic MDL Expert

    Aug 25, 2007
    1,213
    57
    60
    I guess run everest or something that will tell you the SLIC data. I know Hyper-V runs it's own BIOS so I don't know how it would inherit the SLP settings hrmm...
     
  10. sebus

    sebus MDL Guru

    Jul 23, 2008
    5,895
    1,783
    180
    #10 sebus, Sep 28, 2009
    Last edited by a moderator: Apr 29, 2017
    (OP)
    There is NO SLIC (when run iside VM), as the Hyper-V BIOS is not modified (it is plain install)

    But the answer is here:

    The DELL (OEMBIOS CRC=99735910) set can be used on Virtual PC / Virtual Server without modding the Software internal bios, Virtual PC holds this string "MS_VM_CERT/SHA1/9b80ca0d5dd061ec9da4e494f4c3fd1196270c22", which activates ok which SHA1 hash is included in this set.

    And the same applies to Hyper-V

    DELL (OEMBIOS CRC=99735910)

    'f000','0000','ffff','9b80ca0d5dd061ec9da4e494f4c3fd1196270c22'
    'e000','0000','ffff','9b80ca0d5dd061ec9da4e494f4c3fd1196270c22'

    as per this thread:

    http://forums.mydigitallife.net/posts/554468

    sebus
     
  11. ZaForD

    ZaForD MDL Expert

    Jan 26, 2008
    1,180
    177
    60
    You've already found out why it happens. :)

    But there are also HP and FSC R2 Bios sets that work too. ;)
     
  12. kibkalo

    kibkalo MDL Member

    Sep 8, 2009
    124
    10
    10
    Sebus, can you explain, where should I put this:

    DELL (OEMBIOS CRC=99735910)

    'f000','0000','ffff','9b80ca0d5dd061ec9da4e494f4c3 fd1196270c22'
    'e000','0000','ffff','9b80ca0d5dd061ec9da4e494f4c3 fd1196270c22'

    So it activates SLP 1.0 with DELL OEM media and number on unmodded Hyper-V?
    Is this to be put somewhere in registry?
     
  13. sebus

    sebus MDL Guru

    Jul 23, 2008
    5,895
    1,783
    180
    #13 sebus, Jan 2, 2010
    Last edited by a moderator: May 23, 2017
    (OP)
    If you have Dell media that uses this oembios set already then you just install it as VM inside Hyper-V & it is magically activated.

    If you used Dell media that uses different oembios set (possible) then you need to get this set from thread in this forum (searrch is your friend) - or as ZaForD said above HP and FSC R2 Bios sets & read http://forums.mydigitallife.net/threads/6077

    Question implies that you have lots to learn yean, I recommmend Windows XP forum stickies as they are brilliant

    sebus
     
  14. kibkalo

    kibkalo MDL Member

    Sep 8, 2009
    124
    10
    10
    Hm, so the source of the "magic" is unknown? Why the original, unmodified version of virtualization in Hyper-Vand Hyper-V R2 activates DELL OEM SLP 1.0 ?

    I have read the thread and understand this as there are tricks that allow to modify some OEMBIOS settings in OEM Windows in VM, so it activates.

    I am not looking for ways that require modifying OS on VMs, if you understand me.
    I have two technical questions, if you have that knowledge, can you share it please:

    1) What/where is the setting that auto activates unmodified OEM DELL XP/2003 (SLP 1.0) in Hyper-V
    2) Is it possible to change something on virtualization HOST (registry, or Hyper-V files) that it auto activates SLP 1.0 VMs with other OEMBIOS (not DELL)

    Thanks!
     
  15. FreeStyler

    FreeStyler MDL Guru

    Jun 23, 2007
    3,503
    3,614
    120
    #15 FreeStyler, Jan 8, 2010
    Last edited by a moderator: Apr 20, 2017
    No not unkown, it is a implantation by Microsoft itself

    All server 2003 R2 oembios set contain a hash that also is included in Virtual PC/Virtual Server BIOS and apparently Hyper-V BIOS

    Code:
    'f000','0000','ffff','9b80ca0d5dd061ec9da4e494f4c3fd1196270c22'
    'e000','0000','ffff','9b80ca0d5dd061ec9da4e494f4c3fd1196270c22'
     
  16. FreeStyler

    FreeStyler MDL Guru

    Jun 23, 2007
    3,503
    3,614
    120
    #16 FreeStyler, Jan 8, 2010
    Last edited by a moderator: Apr 29, 2017
    Exactly, these are the sets grabbed from 'Server 2003 R2' systems

    the older do not have these special hashes, for more info take a look at the SLP strings posted here and see the difference
     
  17. FreeStyler

    FreeStyler MDL Guru

    Jun 23, 2007
    3,503
    3,614
    120
    #17 FreeStyler, Jan 8, 2010
    Last edited by a moderator: Apr 20, 2017
    Inge001, Does that really work?
     
  18. sebus

    sebus MDL Guru

    Jul 23, 2008
    5,895
    1,783
    180
  19. FreeStyler

    FreeStyler MDL Guru

    Jun 23, 2007
    3,503
    3,614
    120
    Cool, another thing learned today :)
     
  20. kibkalo

    kibkalo MDL Member

    Sep 8, 2009
    124
    10
    10
    Very interesting!
    The last question, I guess.
    Pretending, that my current BIOSLockString doesn't activate my OEM SLP 1.0 guests, where in guests should I look to find, what string they are looking for? So I may use that powershell scriptlet, or just add the registry key on host.. (What to add, to allow another (not DELL) OEM SLP 1.0 guest to auto-activate)