You can use a vm yes, it will detect if it is a Vbox or Vmware if you not alter any DMI settings within the VM's files. But you will see what happens before using on a real pc. Most of my testing was done using a VM (VBox), and altering the DMI information and adding a SLIC file to fool the VM into thinking it was a 'real' PC. Extract the $oem$ folder from the MRP 7z file, place within Sources folder on the ISO or USB stick, save ISO. boot up from the ISO/USB stick and do a normal setup. Once setup is complete, if all went well you will see the branding in place. On a VM obviously it wont activate unless as mentioned above some edits done to the VM prior to installing the OS. The branding will be for the VM used Vmware or Vbox. Then once desktop has appeared , open My Computer and the C drive and you should see a project.log open this in notepad and you will see the progress report. You may get a few errors due to no SLIC etc, but it will give you an indication of what will happen on a real pc. On your Lenovo PC it will brand with Lenovo logo's etc just like the OEM would of, (without all the bloatware!). Also if the SLIC is available in bios which most likely it is then you will be activated also on that PC. With Vista you may need to do a restart after the desktop appears to complete the activation process. Hope this helps Re Spoilers on first post, yes even i sometimes get confused when editing the page. Have to check and re-check i got the info i have added in the right place!
Never had any problems with HP computers up to now - see attachment for query log with latest QT version Having problems attaching the text file - However here is the log: Code: OEM Query Tool v14 Build 7 Advanced 11:37 10.01.2017 OEM Information For This Computer --------------------------------- OS Name: Windows 10 Pro [x64] OS Edition/SKU: Professional OS Language: 1033 [409h] Processor: Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz Processor Cores: [2] Logical Processors: [4] Processor Architecture: [64] HDD Partition Type: [MBR] Bios Version: [N76 Ver. 01.06, 11/01/2016] Total Physical Memory: [16264 Mb] Available Memory : [13778 Mb] SCANNED ------- #1 CSProduct Name - HP ProBook 650 G2 #2 ComputerSystem Model - HP ProBook 650 G2 #3 Baseboard Product - 80FD #4 CSProduct Vendor - HP #5 ComputerSystem MFR - HP #6 Baseboard MFR - HP #7 Serial/Service Tag - Not Shown On Saved Report. #8 BIOS ID - HPQOEM #9 SLIC OA - 2.1 #10 Installed PID Key - Key Not Shown On Saved Report. #11 MSDM Table [OEM-DM] - Not Shown On Saved Report. #12 BIOS Mode - Legacy #13 Certificate - Un-Listed #14 License Status - Licensed SUMMARY ------- OEM Theme/Branding - HP [id:-`#1'] Activation [Vista/7] - HP [id:-`#8'] Valid OEM [OS] - Vista/Win7/Win8.x/Win10 Only SLIC TABLE ---------- Software Licensing Description Table: 53 4C 49 43 76 01 00 00 01 EF 48 50 51 4F 45 4D SLICv.....HPQOEM 53 4C 49 43 2D 42 50 43 01 00 00 00 48 50 20 20 SLIC-BPC....HP 01 00 00 00 00 00 00 00 9C 00 00 00 06 02 00 00 ................ 00 24 00 00 52 53 41 31 00 04 00 00 01 00 01 00 .$..RSA1........ 5B AB 60 56 BC 58 1E E8 C1 D2 A1 5C E5 4F BB FD [.`V.X.....\.O.. 1D A9 8C 94 B4 AE 08 11 DC 13 59 D3 7F F6 3E 87 ..........Y...>. 31 B9 95 74 10 DA 3B A4 5B B5 19 82 7C 39 D7 0D 1..t..;.[...|9.. 7C 22 AC 1C 2A 84 E9 0A 88 6D FA B1 E2 D8 E8 21 |"..*....m.....! 96 E1 2E 68 9A BF 44 45 3E 3C 8E 99 90 DE 37 38 ...h..DE><....78 57 0B 92 15 BC DE FF F2 07 7E B5 40 8C 51 3A C3 [email protected]:. 02 48 F6 13 12 72 FB 42 78 E6 47 88 54 C7 B0 F0 .H...r.Bx.G.T... 93 9E FB 04 B7 B8 B8 90 DE DB ED 32 E1 FB 54 A6 ...........2..T. 01 00 00 00 B6 00 00 00 00 00 02 00 48 50 51 4F ............HPQO 45 4D 53 4C 49 43 2D 42 50 43 57 49 4E 44 4F 57 EMSLIC-BPCWINDOW 53 20 01 00 02 00 00 00 00 00 00 00 00 00 00 00 S .............. 00 00 00 00 00 00 33 06 D7 20 8A 0A 63 95 08 94 ......3.. ..c... A9 60 30 37 CE 9F E8 B9 7B 07 DD CF 72 B3 0B E4 .`07....{...r... 0C 88 79 3C E8 46 01 E8 8B E0 60 F3 63 18 DE 7B ..y<.F....`.c..{ 5C BB A9 53 FE B1 C1 D4 82 67 5B 6C 13 45 9E 66 \..S.....g[l.E.f 49 23 CC 33 09 92 76 FA 31 70 35 F1 57 F8 BA A9 I#.3..v.1p5.W... 56 6F 3F 41 84 A5 3A E9 CD 6C 67 43 9B 70 91 7F Vo?A..:..lgC.p.. B4 06 F8 26 E2 FC 19 46 E5 F6 D7 66 0C 2D 73 99 ...&...F...f.-s. BA 94 38 64 D7 24 98 EB DA 39 64 C8 D3 8C 36 87 ..8d.$...9d...6. FD E5 47 BB A6 B8 ..G... Signature : "SLIC" Length : 0x176 (374) Revision : 0x1 (1) Checksum : 0xEF (239) SLIC OA : 2.1 OEM ID : "HPQOEM" OEM Table ID : "SLIC-BPC" OEM Revision : 0x1 (1) Creator ID : "HP " Creator Revision : 0x1 (1) OEM Public Key Structure Length : 0x9C (156) Reserved : 0x0 (0) Algorithm : 0x2400 (9216) MS-DM Table Not Shown On Saved Report. Certificate ----------- Un-Listed
HP/Compaq has so many variations of DMI which has been a pain to nail down for a while. Touch wood, a lot of the wrong detection's have been rectified, with the tweaked conflict system I have added. It may say possible conflict on the project.log thats mainly because i do a double check on that particular DMI entry. There may be the odd one or two that has slipped though the net so to speak.
Project log Code: Multi-OEM/Retail Project Version : 170108-R50s-BaseLine [MRP/MDL] Files present and extracted successfully. OEM's folder detected, structure appears OK. OS Installation Date: 10.01.2017 12:09:42,13 Windows 10 Pro x64 version found. 12:09:42,49 Professional Edition/SKU installed. 12:09:42,49 Build Version: 14393.0.amd64fre.rs1_release.160715-1616 DMI BIOS Information #1 CS Product Name : [HP ProBook 650 G2] #2 CS Model : [HP ProBook 650 G2] #4 CS Vendor : [HP] #5 CS System Manf : [HP] #6 Baseboard Manf : [HP] #8 BIOS ID : [HPQOEM] INFO: SSD Detected - {Experimental}. 12:09:43,17 'LblDrv' flag not set, 'C:' will be left as OS default. 12:09:43,28 Checking for DMI possible conflicts... 12:09:43,28 Possible [HP ProBook 650 G2] conflict re-checking DMI [#1] resolved as [HP]. 12:09:43,49 HP [#1] manufacture will be used for theme/branding. 12:10:04,41 MSDM key detected, saved and applied. 12:10:04,42 See C:\MSDM-Key.txt for saved key details. 12:10:04,42 Force theme text file present and branding will be set to HP. 12:10:04,47 System Product Name - 'HP ProBook 650 G2' detected and applied. 12:10:04,47 Desktop backgrounds folder created. 12:10:04,49 OOBE.xml file deleted. 12:10:04,49 User.bmp replaced. 12:10:04,49 User.png replaced. 12:10:04,49 User-40.png replaced. 12:10:04,49 User-32.png replaced. 12:10:04,49 User-48.png replaced. 12:10:04,50 User-192.png replaced. 12:10:04,50 {Background} img105.jpg replaced. 12:10:04,52 Resources aero.theme has been replaced. 12:10:04,53 {Background} img100.jpg replaced. 12:10:04,55 System32\oobe\Info folder has been created. 12:10:04,56 Required theme files transferred to System32\oobe\Info folder. 12:10:04,56 MRP Branding script has completed. 12:10:24,17 Advanced Log-On screen has been enabled. 12:10:24,22 User Account Pictures registry entry applied. 12:10:24,25 'Registered Owner' registry entry corrected. 12:10:24,26 The 'defaultuser0' folder is not present. 12:10:26,19 BIOS Mode: Legacy, Partition Type: MBR 12:10:29,45 License Status: Licensed. ============================================================================ Please Note: It is advisable to logout or reboot your computer when possible to allow the User and Log-On background pictures to finalize. ============================================================================ Thank you for using the project, MRP has now completed. Everything fine - good Job Soon I will try it with another HP model and post results but I don't expect any problem.
Looking good The one that caught me out until i nailed it was the 'HP ENVY TS' as MRP usually thought it was FujiTSu, but the tweaked conflict fixes that one. Just noticed you used the Force_Theme method, to make sure it was HP. However MRP got the correct HP result prior to the Forced method taking place.
I forgot i added the bit in about if Secure Boot is enabled that the SLIC information may not be correct.
Thank you for this tool! It's been indispensable when working with many brands of computers, especially with machines that came with Windows 7. I do have a quick question: does this tool do anything for Windows 10? I know it "supports" it, but machines that come with Windows 10 seem to automatically activate (assuming you install the right edition) as soon as they are online anyway. When I tested it didn't seem to activate until it went online, unless I did something wrong?
Nope nothing wrong, that's how win8.x and 10 work now, it all checked on line even if the MSDM key is used (which is in the bios on factory w8.x/10 computers).
Query Tool Updated! Query Tool v14 Build 8 Updated the QT as i forgot to output any possible DMI conflict information in build 7. Example QT Results file: (Using dummy info) Spoiler Code: OEM Query Tool v14 Build 8 Advanced 11:22 AM 11/01/2017 OEM Information For This Computer --------------------------------- OS Name: Windows 10 Pro [x64] OS Edition/SKU: Professional OS Language: 2057 [809h] Processor: Intel(R) Core(TM) i5-6400 CPU @ 2.70GHz Processor Cores: [4] Logical Processors: [4] Processor Architecture: [64] HDD Partition Type: [MBR] Bios Version: [HPQOEM, 05/23/2016] Total Physical Memory: [16344 Mb] Available Memory : [14085 Mb] SCANNED ------- #1 CSProduct Name - HP Envy TS #2 ComputerSystem Model - Dummy Info #3 Baseboard Product - P5K-VM #4 CSProduct Vendor - System manufacturer #5 ComputerSystem MFR - System manufacturer #6 Baseboard MFR - ASUSTeK Computer INC. #7 Serial/Service Tag - Not Shown On Saved Report. #8 BIOS ID - HPQOEM #9 SLIC OA - v2.4 #10 Installed PID Key - Key Not Shown On Saved Report. #11 MSDM Table [OEM-DM] - Un-Listed #12 BIOS Mode - Legacy #13 Certificate - Un-Listed #14 License Status - Licensed SUMMARY ------- OEM Theme/Branding - HP [id:-`#1'] Activation [Vista/7] - HP [id:-`#8'] Valid OEM [OS] - Vista/Win7/Server 2016 Possible DMI Conflict - [HP Envy TS] Resolved As [HP] <<Now displays this line if any conflicts. SLIC Table ---------- Un-Listed MSDM Table ---------- Un-Listed Certificate ----------- Un-Listed Download link updated.
the $OEM$ I tested this yesterday with Vista in VM (VMware) after adding the $OEM$ folder to the ISO sources folder. The VM Vista completed and ran fine but there was no project.log file in the root of the VM C: drive. Does this indicate that the project failed in VM. Is there another check I can make to see that $OEM$ did do something? BTW: I was loading the ISO from the Win7 partn I loaded VMware .. not USB or DVD.
Did any theme/branding for the VM happen? As it is VMware you used to test, if the project ran then you would have VMware's background etc. If the VMware branding and logo's was present then MRP had ran. Within $OEM$ there should be a folder called $$ then within that folder another folder called Setup then lastly within that a folder called Scripts, within the Scripts folder should be DeCompile.exe, OOBE.cmd and if you are using branding, the OEM's.7z file. \Sources\$OEM$\$$\Setup\Scripts Even if the project failed, providing the DeCompile.exe and OOBE.cmd was present within the Scripts folder then it would of at minimum produced a log output of just even the Version number. Just running a test on Vista via a VM... All went ok. Spoiler Code: Multi-OEM/Retail Project Version : 170108-R50s-BaseLine [MRP/MDL] Files present and extracted successfully. OEM's folder detected, structure appears OK. OS Installation Date: 11/01/2017 21:25:25.04 Windows Vista (TM) Home Premium x86 version found. 21:25:26.04 HomePremium Edition/SKU installed. 21:25:26.04 Build Version: 6002.18881.x86fre.vistasp2_gdr.130707-1535 DMI BIOS Information #1 CS Product Name : [VirtualBox] #2 CS Model : [VirtualBox] #4 CS Vendor : [innotek GmbH] #5 CS System Manf : [innotek GmbH] #6 Baseboard Manf : [Oracle Corporation] #8 BIOS ID : [VBOX] 21:25:30.28 'LblDrv' flag not set, 'C:' will be left as OS default. 21:25:30.89 Defined VBOX [VirtualBox] manufacture found. 21:25:30.89 OEM activation not possible due to no defined MAN2. 21:25:30.89 VBOX [VirtualBox] manufacture will be used for theme/branding. 21:25:30.89 Force theme text file not present. 21:25:31.41 System Product Name, not detected. 21:25:31.41 Desktop backgrounds folder created. 21:25:31.41 BackGroundDefault.jpg renamed to img24.jpg. 21:25:31.41 Image applied to .DLL file. 21:25:37.68 User.bmp replaced. 21:25:37.83 Default Windows theme has been replaced with VBOX.theme. 21:25:37.83 System32\oobe\Info folder has been created. 21:25:37.89 Required theme files transferred to System32\oobe\Info folder. 21:25:38.32 MRP Branding script has completed. 21:28:15.21 BIOS Mode: Legacy, Partition Type: MBR 21:28:15.21 Device not connected to the Internet, online license check failed. 21:28:19.70 License Status: Not licensed. Thank you for using the project, MRP has now completed. Images below show the progress/results of my Vista VM test.
That's one way i have never tried , to place the $oem$ / project within the actual WIM/ESD file, have only use the usual put in sources on the ISO way.
On 7 SP1 and 8.1 it worked inside the install.wim/esd, i normally use the project that way on big AiO ISO's, with seperate non oem project and oem project indexes inside. EDIT: did a quick test, same conditions as before only now Pro x86 installed with the Murphy78 script. Also didn't run the OEM project. ATM integrating the oem project into install.esd.
I always wondered what would happen if it was directly integrated into the actual WIM/ESD. Never attempted it because of all the changes to the MRP recently, would be a pain to mount, replace $oem$, re commit etc. Now as MRP is a 'stable' baseline release I won't be updating it anytime soon, unless some nasty bug has crept in, but as no bad feedback has come in, it will stop at 50s for the time being.
Test with Education N with MRP project files inserted in install.wim and installed by using Murphy78's script works Code: Multi-OEM/Retail Project Version : 170108-R50s-BaseLine [MRP/MDL] Files present and extracted successfully. OEM's folder detected, structure appears OK. OS Installation Date: do 12-01-2017 18:44:06,42 Windows 10 Education N x86 version found. 18:44:06,53 EducationN Edition/SKU installed. 18:44:06,53 Build Version: 14393.693.x86fre.rs1_release.161220-1747 DMI BIOS Information #1 CS Product Name : [VMware Virtual Platform] #2 CS Model : [VMware Virtual Platform] #4 CS Vendor : [VMware, Inc.] #5 CS System Manf : [VMware, Inc.] #6 Baseboard Manf : [Intel Corporation] #8 BIOS ID : [INTEL] 18:44:13,67 'LblDrv' flag not set, 'C:' will be left as OS default. 18:44:14,11 Defined VMware [VMware] manufacture found. 18:44:14,11 VMware [VMware] manufacture will be used for theme/branding. 18:44:15,22 No MSDM key detected in BIOS. 18:44:15,22 Force theme text file not present. 18:44:15,48 System Product Name - 'VMware Virtual Platform' detected and applied. 18:44:15,48 Desktop backgrounds folder created. 18:44:15,50 OOBE.xml file deleted. 18:44:15,50 User.bmp replaced. 18:44:15,60 User.png replaced. 18:44:15,60 User-40.png replaced. 18:44:15,61 User-32.png replaced. 18:44:15,61 User-48.png replaced. 18:44:15,61 User-192.png replaced. 18:44:15,61 {Background} img105.jpg replaced. 18:44:15,81 Resources aero.theme has been replaced. 18:44:15,87 {Background} img100.jpg replaced. 18:44:15,98 System32\oobe\Info folder has been created. 18:44:16,00 Required theme files transferred to System32\oobe\Info folder. 18:44:16,20 MRP Branding script has completed. 18:46:29,65 Advanced Log-On screen has been enabled. 18:46:30,00 User Account Pictures registry entry applied. 18:46:30,04 'Registered Owner' registry entry corrected. 18:46:30,04 Detected 'defaultuser0', attempting to remove the folder... 18:46:30,23 Removal of 'defaultuser0' folder successful. 18:46:39,18 BIOS Mode: Legacy, Partition Type: MBR 18:46:41,93 License Status: Not licensed. ============================================================================ Please Note: It is advisable to logout or reboot your computer when possible to allow the User and Log-On background pictures to finalize. ============================================================================ Thank you for using the project, MRP has now completed. Same result with install.esd Will implement it in all indexes and test some more.