I know that alot of ppl know how to do it by replacing the moded bios of Hyper-V and installing the correct cert and key So this is just a guide for those who don't Tested on Virtual Machines running Windows Server 2008 R2 Enterprise Edition Download the moded bios of Hyper-V from here - thats for Windows Server 2008 R2 Code: W/O SP rapidshare.com/files/293705278/vmwp_6.1.7600.16385.slic21.rar SP1 RC rapidshare.com/files/441371043/vmwp.rar Run these two commands from an elevated command prompt so u could replace vmwp.exe file inside system32 folder Code: takeown /f C:\Windows\System32\vmwp.exe cacls C:\Windows\System32\vmwp.exe /G YOUR-USER-NAME-HERE:F don't forget to replace YOUR-USER-NAME-HERE with the user u want to give permission to Replace vmwp.exe from system32 folder with the downloaded one after renaming it Run DAZ loader on the Virtual Machine (search the forum u'll find it in 3 seconds) but take care U've to go to Advanced option and check mark Ignore OEM Partiotions - checked by default Ignore existing SLIC Use legacy mode as default then back to the Installation tab and click Install thats it.....no restart needed and u r activated
Doesn't the cracked file already contain a SLIC though? If it does then launching the application with the /bios parameter will install just the certificate and serial for whichever SLIC the vmwp executable contains.
The reason is, that you as user should not touch it (but you did anyway) It honestly makes NO other difference to anything. And I did not yet find a way to add rights back for Trusted Installer sebus
Yeah that doesn't make sense, anyway installing loader without replacing vmwp.exe resulted in a blinking cursor for me
I have a test machine at home and had an issue activating Win Server 2008 R2 running on Hyper-V - this is GOOD+ Thanks
Ok, I've followed these instructions and had no luck. I just get the blinking cursor. Does anyone have any idea what I might be doing wrong or has MS changed something since the last post?
SVR2008 R2 is now SVR2008 R2 SP2. In that update vmwp.exe was updated, which could be you problem. Check the stickies if your using SVR2008 R2 SP2.
its easy, here in the forum are the tool WinSLIC NTFS, download and start the tool. take dell pc, install certificate "SLMGR /ILC DELL.XRMS-MS" install dell product key for server 2008 r2 with "SLMGR /IPK YOUR KEY" the tool and keys are here in the forum, the certificates also.
Thanks very much for the responses! I tried all of the above and no love. However, I tried a different srv 2008 R2 SP1 Disc and everything went beautifully. So evidently I beat my head on the wall for four days because of a modified .iso Go figure. Thanks again for the help. Edit: I also wanted to thank the OP for this great guide, DAZ for his awesome loader, and the MDL community.
Hello, I have Hyper-V running on top of a Windows 2008 R2 server. I ran the current 2.0.1 Daz crack within a VM which is a Windows 2008 R2 server and get the blinking cursor upon reboot. Rather than use the above methods described (Which I believe works in my scenario or is this for Hyper-V Bare Metal?) is there a way for me to reset the VM's back to a pre-Daz state? I know I should have made a Snapshot but like a dumb ass I didn't and my VM seem's hosed. Booooo. Thanks!
Same as you would do with any other physical machine It is all included with the loader, just read! * Boot up your PC from your Windows 7 install disk * Select the "Repair your computer" option * Select to open "Command Prompt" * Input "bootsect.exe /nt60 c:" (without quotes) * Restart sebus
Thanks Sebus for the quick response and the steps to do so! Worked great. However I cannot seem to register this VM using any of the above methods. Are there any suggestions at this point on how to use Daz (or any other method) to get a 2008 R2 SP1 unit working in a Hyper-V on top of Windows environment? Thanks
Thanks gents for the suggestions and I will look into WindSlic first as I don't want to modify Hyper-V in case an update happens and snuffs it out.
Well the WinSLIC version worked a treat! Only problem is that there just aren't any step by step guides on this site, or maybe I just missed it for this. I should create one for us noobs that don't really understand all the jargon. Thanks again!