Yes that is where AMI_SLIC3 tool came from but Yen, china4ever, myself and I think a few others were on Kesnews forum originally.
Damn, I missed all you 'Old Timers' reminiscing, I'd forgotten I'd been on half those old sites. But, It didn't understand how you guys did this BIOS thing back then and I'm still no wiser now. Even after all the help I got. I'll stick with my screwdrivers, I know how they work I just installed Windows 8.1 Pro and Hyper-V on a test box. I switched vmwp.exe with the 6.2.9200.16384 version (Yen's I think) all seemed to work fine. But now I get an error when adding/removing NIC's in Hyper-V. Anyone else come across this ???
Hey Manolo, I don't think you can be technically late, until the next version of Server comes out, or at least a major update. Tried your file and it works great I still have the NIC problem, so maybe that a driver thing
Yen : I really appreciate the POC (proof of concept) However for me it's hard to see the true benefit of it ! Let me explain : - first, and as we all have guest, the interest of patching/injecting any slp/slic strings into vmwp.exe is to offer us complete offline activation. As Windows 8+ and OEM-DM/MSDM keys require one time internet access to succeed in activation, we loose this opportunity... - last but not least, I used your method (XSDT/RSDT tables extension and call to extra MSDM table) to generate another valid vmwp.exe for 2012 RTM. To achieve that, I injected a valid 55 bytes MSDM table grabbed from an OA3 Tool report done on a Hewlett Packard computer in place of the Fujitsu MSDM table and dummy key. In order to emulate a "100% Hewlett BIOS", I replaced all occurences of FSC strings from your model with HPQOEMSLIC-BPC strings. (this might have been un-needed extra job but I have prefered to...) Once all checksums corrected and verified, I successfully started a Win 8.1 Pro VM. DavidXXW Slic Toolkit showed valid HPQOEMSLIC-BPC SLIC 2.1. RW everything ACPI report showed correct HPQOEMSLIC-BPC MSDM table with key. Once OEM-DM key manually input and accepted by W8.1 Pro machine, I ran online activation. Slmgr returned unsuccessful activation with code 0xC004C008 : product key already in use by another machine ! I have to say that this HP machine booted once under OEM Windows 8 Pro before I downgraded to 7 Professional. At this step, machine may have activated it's OEM-DM key against MS and locked it... Even if this machine will never see Win 8 Pro again, it seems that I've lost the ability to re-use that OEM-DM key. I did not try to (and cannot anymore) test key again on the real machine with another clean Win 8/8.1 Pro "factory setup". This could and should work ! I feel that MS may not only compare MSDM table and OEM-DM key to achieve successfull OEM activation. They might store some other hardware things, in order to really lock OEM key with and only with the real machine... All that makes your POC pretty useless, at least for use within VMs (unless I missed some important things...) Anyway, just like all of us , I'm still waiting for : - SLIC 2.3 (with new matching certificates) for 2012R2 - KMS_v6_emulator.exe ! Again Yen, big thanks for your efforts and sharing your knowledge ! edit : smiley cleaning...
Yep ! But I'm not sure Hyper-V would like having 2 VMs with same serial/uuid... I remember last year when dealing with 2012 KMS hosts, changing VM settings to match provided tokens lead me to headache... (machines used to disappear from console... ) Finally I managed to get it work , but quickly abandonned that way since CODYQX4 released it's excellent MTK... Let be honest, it's a question of time for us to get SLIC 2.3 and local KMS6 emulator... No time to waste dealing with silly MSDM activation... Even if I appreciated the proof of concept !
Say there Sebus, would you be so kind as to include a link to an explanation of the phone activation solution please Sir? THanks!
Activate by phone pick up the phone dial no for your country speak to the machine give it string of numbers type string of no you get back