*********************************************************** VIRTUALBOX SLIC ACTIVATION AIO WINDOWS HOST & GUEST platforms TUTORIAL By "The PANCHO's TEAM" (Made in FRANCE) *********************************************************** After reading several posts on this web site, a lot for LINUX HOST, and try to test it for some of them without success (sorry guys....), I decide to write my own scripts and now, this tutorial as an unique POST that include ALL required stuff to do it automatically. It is simply the better solution to show that this solution with SLIC 2.1 table works fine... 1) Introduction This tutorial has been written to explain "HOW TO" configure a VIRTUALBOX Microsoft Windows OS "HOST" to be able to run a Microsoft Windows SEVEN OS "GUEST" and activate it using SLIC method. This tutorial, and others files included in the ZIP file, contains all stuff to do it automatically. Note: FOR WINDOWS HOST platform ONLY !!! 2) DOWNLOAD this tool: From this post, download the ZIP file. ZIP filename: VIRTUALBOX_SLIC_ACTIVATION_AIO__V1.0.zip Unzip the ZIP file anywhere on your Windows HOST machine. A folder named "VIRTUALBOX_SLIC_ACTIVATION_AIO" will be created with all files in it... 3) The following files are available in the ZIP file: - How_To__VIRTUALBOX_SLIC_ACTIVATION_AIO.txt (This tutorial). - VIRTUALBOX__HOST___VM_Configuration.cmd (First script to run on HOST side) - VIRTUALBOX__GUEST__Windows_SEVEN_License_Installation.cmd (Second script to run on GUEST side) - Table_SLIC__DELL.BIN (The SLIC table to be injected in the VIRTUALBOX BIOS on HOST side). - Certificat__DELL.XRM-MS (The Windows SEVEN certificat file used at activation time on GUEST side). 4) Microsoft Windows OS supported on "HOST" side: - Windows XP Professional SP3 (FR): Tested OK - Windows VISTA: Not tested but should work... - Windows 7 Professional SP1 (FR): Tested OK - Windows 8: Not tested, so waiting for feedback... - Windows 8.1: Not tested, so waiting for feedback... 5) Microsoft Windows OS supported on "GUEST" side (all 5 products are supported for SLIC activation): - Windows 7 Starter: Not tested, so waiting for feedback... - Windows 7 Home: Not tested, so waiting for feedback... - Windows 7 Home Premium: Not tested, so waiting for feedback... - Windows 7 Professional SP1 (FR): Tested and activated successfully !!! - Windows 7 Ultimate: Not tested, so waiting for feedback... 6) VIRTUALBOX software release used: From the official web site, download and used the "4.3.2 R90405" version or above. Filename: VirtualBox-4.3.2-90405-Win.exe 7) How it works: I used the DELL SLIC 2.1 table, and all DELL's OEM Keys specific to the Windows 7 kind of product (all stuff available in this forum). This works fine with VIRTUALBOX "whatever" hardware you have on your physical machine...You get a GUEST OS running with OEM license on an emulated DELL hardware machine. That's all the tips. 8) Steps by steps method: - Install and configure VIRTUALBOX software on your Windows platform. - Create, install and configure a VIRTUALBOX "GUEST" Windows seven OS, using a "temporary valid" license at installation time, or using the tips : Create or download the file "ei.cfg", and put it in your Windows SEVEN installation folder (see POST about this tips for details...): this will avoid the need to specify a valid license at installation time... - When Windows Seven "GUEST" OS is ready, up and running with access to INTERNET, close and shutdown ALL virtual machines, and VIRTUALBOX software ! This is mandatory ! - On HOST side::: From this folder, run the script "VIRTUALBOX__HOST___VM_Configuration.cmd". This script will ask you for the name of your VIRTUALBOX "GUEST" machine, from the list displayed by the script (please enter the exact machine name as it is case sensitive !!!), backup the current VIRTUALBOX config file for security, will configure the parameters for you automatically, and will displayed the change done. - On HOST side::: Start your VIRTUALBOX "GUEST" Windows Seven machine from the VIRTUALBOX software interface. - On GUEST side::: Login with an Administrator account ! This is mandatory ! Note: The GUEST machine should be able to access Internet, for activation purpose ! This is mandatory ! Using the File Manager/Windows Explorer, you will find a shared folder named "HOST-GUEST-Share", created automatically by the script. From this folder, run the script "VIRTUALBOX__GUEST__Windows_SEVEN_License_Installation.cmd" and follow the instructions...Your OS will be activated. That's all folks... 9) Comments, feedback, and testing results are welcome for better understanding of everybody... Thanks in advance... "The PANCHO's TEAM".
Hi TITO... Thanks for your link, but I already read plenty of them and try to put all interesting stuff in 2 single scripts.........I think it's better when you want to learn, or simply use it...Now, I personally know what is involved and where... hope it can serve a lot of readers.. Cheerss Foxmulder
Hi, hummmm hummm, may be related to several reads and tests and reads....., and I found that using SLUI.EXE works fine in all possibles cases.... May be this kind of thing, related here ? => http: // forums.mydigitallife.net/threads/42889-Win-7-Enterprise-Not-Genuine-message-won-t-go-away "Error: Windows is running within the non-genuine notification period. Run 'slui.exe' to go online and validate windows." Depends if you start from a "fresh" SEVEN installation, or sometimes, like me, from a previous longtime ago SEVEN installation using KMS activation. So, you are right for 99% of case, but remaining case sometimes fails and using SLUI.EXE resolv it.... Thanks anyway for you remark... Foxmulder
Hello Foxmulder09 Congratulation for your awesome work. Very useful. Btw, do you know if it's possible to use it with this: forums.mydigitallife.net/threads/15733-Win-8-x-%95-Win-7-%95-Vista-Multi-OEM-ISO-Project In that case, it should be no longer necessary to run the configuration command on the guest side. Is my understanding right? Also, beeing mostly a MacOS user i plan to adapt the configuration command on the host side for MacOS. Once again, great job. Thanks for sharing Best regards, Jeff_59 P.S.: Btw, i'm french too
Hello I do confirm: in case you use a multi OEM install disc: forums.mydigitallife.net/threads/15733-Win-8-x-%95-Win-7-%95-Vista-Multi-OEM-ISO-Project you don't even need to run the configuration command on the guest side. Once again, great job. Thanks for sharing Best regards, Jeff_59
it's good, I activate Windows 7 Ultimate, but only adding changes from your script manually in my vmx file, because your cmd don't see other VM's if not are installed in users's data folder. Also, the key in your script is only for Windows 7 Pro. The simple method - adding only one record in vmx, for example: <ExtraDataItem name="VBoxInternal/Devices/acpi/0/Config/SLICTable" value="E:\VirtualPC\Virtual_VMs\test\DELL.BIN"/> and after activate with key and cert.
Thanks, still working today (2020, Virtualbox 6.1.12) and with a Windows 7 Home Premium edition (FR) guest but I had to change 2 things: On the HOST system, had to add "C:\Program Files\Oracle\VirtualBox" in PATH system environement variable On the HOST system, had to edit the "VIRTUALBOX__HOST___VM_Configuration.cmd" to replace all occurrences of "%USERPROFILE%\VirtualBox VMs" by the proper path, as I don't use the default path.
Great! Worked with Win7 64bit Ultimate ENG guest on VirtualBox 6.1.34 with the original script (Win 10 host). Just added "SET VBOX_INSTALL_PATH=C:\Program Files\Oracle\VirtualBox\" at the beginning of the HOST script to take care of the VirtualBox path. During the GUEST script chosen the option 5 (Windows 7 Edition Integrale) for the Ultimate edition. THX!!!