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
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
But I DO NOT have ANYTHING modded in this setup Host PowerEdge BIOS is Dell original & Hyper-V is just a default install sebus
Windows 2003 VLK doesn't need activation You seem to have fooled yourself effectively while trying to fool others.
but, he installed using OEM media which should be looking for SLP1.0 in bios. Hence his original question.
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
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...
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?
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!
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'
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)