@mxman2k I've always used MRP since ages (searchengine's, The_Guardian's and now yours) and it always has activated and branded Win 7 OEM machines, including Starter, Home Basic, Home Premium editions. In fact, all of them .
On 7 Starter it also works but the old projects can't do the desktop background, will give it a test with this project I always only service the lowest 7 SP1/8.1 SKU and offline set-edition them to higher sku's.
Code: MRP - OEM Query Tool v15 Advanced 21:07 Wed 02/01/2017 Basic OEM Information For This Computer --------------------------------------- OS Name: - Windows 7 Professional [x64] OS Edition/SKU: - Professional OS Language Name/Code: - en-US ( 1033 [409h] ) OS Locale: - en-US OS Country: - United States OS Language Value: - ENU Processor: - Intel(R) Core(TM) i3-2350M CPU @ 2.30GHz Processor Cores: - [2] Logical Processors: - [4] Processor Architecture: - [64] HDD Mode: - [AHCI] HDD Partition Type: - [MBR] Bios Version: - [, ] Total Physical Memory: - [6055 Mb] Available Memory: - [4001 Mb] Scanned DMI ----------- #1 CSProduct Name: - 1141BTU #2 CSModel Name: - 1141BTU #3 CSBaseboard Prod: - 1141BTU #4 CSProduct Vendor: - LENOVO #5 CSManufacturer: - LENOVO #6 Baseboard MFR: - LENOVO #7 Serial/Service Tag: - Not Shown On Saved Report. #8 BIOS ID: - LENOVO #9 SLIC OA: - 2.1 #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: - Lenovo [id:-`#4'] OEM Activation Vista/7: - Lenovo [id:-`#8'] Valid OEM OS: - Vista/Win7 Only QTv15 didn't detect my system bios version. Why?
Me too. It's the best and fastest way to make an updated AIO. I use dism /set-edition then imagex /append to get higher skus.
Code: Multi-OEM/Retail Project Version : 170131-R52s-BaseLine [MRP/MDL] Files present and extracted successfully. OEM's folder detected, structure appears OK. OS Installation Date: wo 01-02-2017 2:46:05,68 Windows 7 Enterprise x64 version found. 2:46:05,79 Enterprise Edition/SKU installed. 2:46:05,79 Build Version: 7601.23572.amd64fre.win7sp1_ldr.161011-0600 2:46:21,06 Installed OS language: nl-NL ( 1043 [413h] ) -------------------- DMI BIOS Information -------------------- #1 CS Product Name : [VMware Virtual Platform] #2 CS Model Name : [VMware Virtual Platform] #4 CS Vendor Name : [VMware, Inc.] #5 CS System Name : [VMware, Inc.] #6 Baseboard Name : [Intel Corporation] #8 BIOS ID : [INTEL] INFO: Standard HDD Detected. 2:46:24,31 Rename 'System Drive' flag was enabled, 'C:' changed to 'Windows_7_Ent'. 2:46:24,73 Note: OEM activation is not possible due to no defined SLIC. 2:46:24,73 VMware [VMware] manufacture will be used for theme/branding. 2:46:24,73 Force theme text file not present. 2:46:25,10 x64 Theme registry patch file applied. 2:46:25,12 Model Name: 'VMware Virtual Platform' detected and applied. 2:46:25,12 Desktop backgrounds folder created. 2:46:25,13 User.bmp replaced. 2:46:25,20 VMware theme has been applied. 2:46:25,21 System32\oobe\Info folder has been created. 2:46:25,24 Required theme files transferred to 'System32\oobe\Info folder'. 2:46:25,51 Branding script has completed.
I always thought it's core business was oem activation and branding. Isn't the information collected only to see if the project ran correct?
I actually just did Win 7 Home Basic in a VM to update and capture. It did work on everything but the background. I had to go into oobe/info and set the background. It also shows up in backgrounds under appearance change desktop background.
The bios string may contain, non standard characters, this may prevent QT from displaying the data. Bios Version is queried via a WMIC call sometimes it gets it wrong, not sure why. I have a Lenovo Tower that does not show the bios version, it may be the OEM using odd characters? The important part of the QT is the DMI detection/slic/msdm and most of all the Summary part which will inform you that MRP will either brand the PC and/or activate either by SLIC or MSDM.
Thanks, but I'm doing it to I guess have my own version I can tell apart from others. I changed all the VM pictures and icons so its how I want it to look and I don't have to have the project unless I'm doing on an OEM machine.
If i remember Starter Edition was a odd beast regarding desktop background/theme and even multitasking, a lot of things was not there to change. Home basic was a 'bit' better. Any laptop/pc that came to me with Starter was usually upgraded to Home Premium as even if aero could not run at least the user had more fun playing with the settings - then coming back to me because they screwed it up lol.
Yeah, i know, but want to keep my AiO really ALL The desktop doesn't bother me on starter, as long as it gets properly activated by using the slic table
Nope, not all and i don't include server editions, people who play or work with server editions should be able to modify them themselves (IMO).
15025 , they bringing out the previews quite quick recently. Have noticed a slight pattern, Education Editions the defaultuser0 seems to always have to be forced removed. The odd Enterprise ones too.
Code: Multi-OEM/Retail Project Version : 170131-R52s-BaseLine [MRP/MDL] Files present and extracted successfully. OEM's folder detected, structure appears OK. OS Installation Date: Fri 02/03/2017 1:00:54.83 Windows 10 Home Insider Preview x86 version found. 1:00:54.99 Insider Edition/SKU installed. 1:00:54.99 Build Version: 15025.1000.x86fre.rs_prerelease.170127-1750 1:01:00.92 Installed OS language: en-US ( 1033 [409h] ) -------------------- DMI BIOS Information -------------------- #1 CS Product Name : [VMware Virtual Platform] #2 CS Model Name : [VMware Virtual Platform] #4 CS Vendor Name : [VMware, Inc.] #5 CS System Name : [VMware, Inc.] #6 Baseboard Name : [Intel Corporation] #8 BIOS ID : [INTEL] INFO: Standard HDD Detected. 1:01:04.34 Rename 'System Drive' flag was enabled, 'C:' changed to 'Windows_10_Prev'. 1:01:04.86 VMware [VMware] manufacture will be used for theme/branding. 1:01:05.92 No MSDM key detected in BIOS. 1:01:05.92 Force theme text file not present. 1:01:06.30 Model Name: 'VMware Virtual Platform' detected and applied. 1:01:06.30 Desktop backgrounds folder created. 1:01:06.31 OOBE.xml file deleted. 1:01:06.33 User.bmp replaced. 1:01:06.41 User.png replaced. 1:01:06.47 User-40.png replaced. 1:01:06.47 User-32.png replaced. 1:01:06.48 User-48.png replaced. 1:01:06.48 User-192.png replaced. 1:01:06.48 {Background} img105.jpg replaced. 1:01:06.73 VMware theme has been applied. 1:01:06.84 {Background} img100.jpg replaced. 1:01:06.87 System32\oobe\Info folder has been created. 1:01:07.03 Required theme files transferred to 'System32\oobe\Info folder'. 1:01:07.31 Branding script has completed. 16:06:00.11 Advanced Log-On screen has been enabled. 16:06:00.26 User Account Pictures registry entry applied. 16:06:00.31 'Registered Owner' registry entry corrected. 16:06:00.31 Detected 'defaultuser0', attempting to remove the folder... 16:06:00.48 Removal of 'defaultuser0' folder successful. 16:06:06.17 BIOS Mode: Legacy, Partition Type: MBR 16:06:07.54 HDD Controller Mode: [AHCI] 16:06:14.31 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. It looks like you've seen it correctly