Quick test with a VMware VM (with Education MSDM)... Spoiler Code: Multi-OEM/Retail Project Version : 170312-R54.1 - BaseLine [MRP/MDL] Required files present and extracted successfully. Enhanced Log Mode: Activated. > Checking OEM's Folder Structure. OEM's folder detected, structure appears OK. OS Installation Date: 13/03/2017 14:42:25.09 > Checking installed OS name. 14:42:25.25 Windows 10 Education x64 version found. 14:42:25.26 > Checking installed OS Edition/SKU. 14:42:25.56 Education Edition/SKU installed. 14:42:25.56 Build Version: 14393.0.amd64fre.rs1_release.160715-1616 14:42:31.47 Edition Language/Code: en-GB ( 2057 [809h] ) 14:42:31.47 OS Locale: en-GB 14:42:31.47 OS Language Value: ENG -------------------- 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 : [DELL] > Detecting if a Solid State or Standard Hard Drive is present. INFO: Standard HDD Detected. 14:42:35.24 > Checking if 'LblDrv' flag is enabled. 14:42:35.33 Rename 'System Drive' flag was enabled, 'C:' changed to 'Windows_10_Edu'. 14:42:35.33 > Checking DMI for manufacture information. 14:42:35.87 VMware Bios ID conflict resolution enabled. VMware resolved as Dell [#8]. 14:42:35.87 Dell [VMware] manufacture will be used for theme/branding. 14:42:35.87 > Branding Section Part 1. 14:42:35.87 Force theme text file not present. 14:42:37.61 > Checking DMI for Model Name. 14:42:37.65 Computer Model Name: 'VMware Virtual Platform' detected and applied. 14:42:37.65 > Branding Section Part 2. 14:42:37.65 Desktop backgrounds folder created. 14:42:37.68 > Windows 8.x/10/Server 2016 User Account Picture Management Section 1. 14:42:37.68 OOBE.xml file deleted. 14:42:37.68 User.bmp replaced. 14:42:37.77 User.png replaced. 14:42:37.78 User-40.png replaced. 14:42:37.82 > Windows 10/Server 2016 User Account Picture Management Section 2. 14:42:37.82 User-32.png replaced. 14:42:37.86 User-48.png replaced. 14:42:37.88 User-192.png replaced. 14:42:37.90 Lock Screen {img105.jpg} replaced. 14:42:38.13 > Theme Management Section. 14:42:38.13 Dell theme has been applied. 14:42:38.20 Log-In Background {img100.jpg} replaced. 14:42:38.24 > Transfer Theme Files Section. 14:42:38.24 System32\oobe\info folder has been created. 14:42:38.25 Required theme files transferred to 'System32\oobe\info' folder. 14:42:38.25 > Deletion of obsolete files. 14:42:38.40 Branding script has completed. 14:45:03.57 Add-On Manager in progress. 14:45:04.99 > Detecting if Visual C 2012 DLL's are present. 14:45:08.21 > Visual C 2012 DLL's have been temporarily installed. 14:45:08.21 > Check BIOS for MSDM Key. 14:45:19.49 Processing MSDM Key for Edition status. 14:45:23.20 > Show MSDM Key Information. 14:45:23.20 MSDM Key Information: Win 10 RTM Education OEM-DM 14:45:49.20 Your MSDM key is for the Edition installed and has been applied. 14:45:49.21 See C:\MSDM-Key.txt for your saved MSDM key details. 14:45:49.21 > Temporary Visual C 2012 DLL's used have been uninstalled. 14:45:52.46 > Checking if the computer is a 'default' Virtual Machine. 14:45:52.46 > Detected: 'default' VMware VM. 14:45:53.20 Advanced Log-On screen has been enabled. 14:45:53.35 Set 'User Account Picture' registry entry applied. 14:45:54.20 'Registered Owner' registry entry corrected. 14:45:54.20 Detected 'defaultuser0', attempting to remove the folder... 14:45:55.14 Removal of 'defaultuser0' folder successful. 14:45:55.58 > Checking BIOS's mode and System drive's partition type. 14:46:01.40 BIOS Mode: Legacy, Partition Type: MBR 14:46:01.42 > Checking Hard Drive Controller Mode. 14:46:01.67 HDD Controller Mode: [AHCI] 14:46:01.67 > Checking Online Status. 14:46:01.67 Device does not appear connected to the Internet, online license check failed. 14:46:07.13 > Checking if Windows is activated/licensed. 14:46:07.72 License Status: Not Licensed. 14:46:07.72 > Checking if 'UserTweaks.cmd' present. 14:46:07.72 'UserTweaks.cmd' present, attempting to apply. 14:46:07.72 UserTweaks.cmd has completed. 14:46:35.26 > Checking if 'WinTel.cmd' present. ================================================================================ = Please Note: It is advisable to logout or reboot your computer when possible = = to allow the User and Log-On background pictures to finalize. = ================================================================================ Enhanced Log Mode: Deactivated. The Multi-OEM/Retail Project has now completed. For those who don't have a MSDM table in your computer and wondered what the saved MSDM-Key.txt file has inside. (Edited out key) Spoiler Code: Saved MSDM key ============== Your detected MSDM key: 7****-*****-*****-*****-***MW Key Edition: Win 10 RTM Education OEM-DM If required, you can insert this MSDM key manually via a Admin Command Prompt using: slmgr.vbs /ipk 7****-*****-*****-*****-***MW slmgr.vbs /ato The above commands will insert your MSDM key and attempt to activate when you are online. Activation will occur ONLY if the key matches the installed Edition/SKU. ================================= Other Information about your Key: ================================= Activate ID: = {1a9a717a-cf13-4ba5-83c3-0fe25fa868d5} Group ID: = 3278 Edition ID: = Education Key Name ID: = Win 10 RTM Education OEM-DM Channel ID: = OEM-DM Thanks s1ave77 for the VM bios's.
Hello guys! Do you have a manual how to use these tools with SCCM Task Sequence without MDT? At this time we have Task Sequence with original .wim of Windows 10 Pro Retail for example and adding to it during task sequence drivers, Cumulative Updates, applications and etc. Is it possible to add this tool to a .wim file or I need to create a package with this tool and then after OS deployment copy content from package to the OS and run commands to activate Windows?
It's either for use as $OEM$ folder in "iso:\sources" or in "iso:\sources\install.wim\windows\setup\scripts".
Sadly I don't have any manual on how to use SCCM with MRP. However it is possible to add the project to a wim/esd to do the branding/activation. There are members on MDL who perform that regularly who would be able to explain how to do that part.
Query Tool Updated! Query Tool v15 Build 7 Fixed a couple of spelling mistakes - no idea how i missed those! Added extra error checking and a little tweak to allow extra time to complete certain tasks. Adjusted operation mode from Highest to Administrator, this will hopefully help when the QT fails to execute first time, not sure why that happens it maybe a timing issue, it's not within the QT. Download Link Updated.
Have had a few times when everything looked ok, then after a few days you realize hmm how did i miss that. One mistake was 'System Query' that was spelt Sysytem Query. No one saw it either lol. There again it was only displayed for a fraction of a second. I only noticed it when i was altering some timing parts. It's been like that for about 2 builds. Went through every echo line and i am now sure have got them all... I put it down to being word blind , my excuse anyway.
Quick 15058 test: Code: Multi-OEM/Retail Project Version : 170312-R54.1 - BaseLine [MRP/MDL] Required files present and extracted successfully. OEM's folder detected, structure appears OK. OS Installation Date: 15/03/2017 9:50:15.37 Windows 10 Enterprise x86 version found. 9:50:15.79 Enterprise Edition/SKU installed. 9:50:15.80 Build Version: 15058.0.x86fre.rs2_release.170310-1436 9:50:20.68 Edition Language/Code: en-GB ( 2057 [809h] ) 9:50:20.68 OS Locale: en-GB 9:50:20.68 OS Language Value: ENG -------------------- 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. 9:50:23.19 Rename 'System Drive' flag was enabled, 'C:' changed to 'Windows_10_Ent'. 9:50:23.76 VMware [VMware] manufacture will be used for theme/branding. 9:50:23.77 Force theme text file not present. 9:50:24.01 Computer Model Name: 'VMware Virtual Platform' detected and applied. 9:50:24.02 Desktop backgrounds folder created. 9:50:24.04 OOBE.xml file deleted. 9:50:24.04 User.bmp replaced. 9:50:24.10 User.png replaced. 9:50:24.12 User-40.png replaced. 9:50:24.13 User-32.png replaced. 9:50:24.13 User-48.png replaced. 9:50:24.13 User-192.png replaced. 9:50:24.15 Lock Screen {img105.jpg} replaced. 9:50:24.40 VMware theme has been applied. 9:50:24.44 Log-In Background {img100.jpg} replaced. 9:50:24.51 System32\oobe\info folder has been created. 9:50:24.52 Required theme files transferred to 'System32\oobe\info' folder. 9:50:24.84 Branding script has completed. 8:55:14.86 Add-On Manager in progress. 8:55:20.50 No MSDM key detected in BIOS. 8:55:25.16 Advanced Log-On screen has been enabled. 8:55:25.57 Set 'User Account Picture' registry entry applied. 8:55:26.24 'Registered Owner' registry entry corrected. 8:55:26.24 Detected 'defaultuser0', attempting to remove the folder... 8:55:27.11 Removal of 'defaultuser0' folder successful. 8:55:31.21 BIOS Mode: Legacy, Partition Type: MBR 8:55:31.52 HDD Controller Mode: [AHCI] 8:55:37.46 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. = ================================================================================ The Multi-OEM/Retail Project has now completed.
ooh 15058 - No preview/insider name - must be one of the 'this might be "RTM" builds' ? I'm still puzzled why the TIME tag does strange things in the Project.log... It not important it gives a rough reference.
So I downloaded and ran MRPQTv15b7.exe. Then it starting doing things and I panicked. Can you explain in the OP what it does?
Done. Added a quick reference what the Q/Tool does on the first page. The Query Tool does a basic check on the computer it is run on to see if the main project will brand/activate that computer if used when re-installing a Windows OS. The important part is the summary section, this will indicate what branding will possibly be applied, (if the DMI has the required information), also what sort of LEGAL activation is possible ie SLIC (Vista/7/Some Server Editions), or MSDM (8.x/10).
Code: Multi-OEM/Retail Project Version : 170312-R54.1 - BaseLine [MRP/MDL] Required files present and extracted successfully. OEM's folder detected, structure appears OK. OS Installation Date: za 18-03-2017 22:25:40,51 Windows 10 Pro x64 version found. 22:25:41,03 Professional Edition/SKU installed. 22:25:41,03 Build Version: 15061.0.amd64fre.rs2_release.170315-1424 22:25:48,12 Edition Language/Code: nl-NL ( 1043 [413h] ) 22:25:48,12 OS Locale: nl-NL 22:25:48,12 OS Language Value: NLD -------------------- 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. 22:25:52,32 Rename 'System Drive' flag was enabled, 'C:' changed to 'Windows_10_Pro'. 22:25:52,81 VMware [VMware] manufacture will be used for theme/branding. 22:25:52,81 Force theme text file not present. 22:25:53,45 Computer Model Name: 'VMware Virtual Platform' detected and applied. 22:25:53,45 Desktop backgrounds folder created. 22:25:53,50 OOBE.xml file deleted. 22:25:53,50 User.bmp replaced. 22:25:53,64 User.png replaced. 22:25:53,67 User-40.png replaced. 22:25:53,67 User-32.png replaced. 22:25:53,67 User-48.png replaced. 22:25:53,67 User-192.png replaced. 22:25:53,68 Lock Screen {img105.jpg} replaced. 22:25:53,97 VMware theme has been applied. 22:25:54,15 Log-In Background {img100.jpg} replaced. 22:25:54,22 System32\oobe\info folder has been created. 22:25:54,23 Required theme files transferred to 'System32\oobe\info' folder. 22:25:54,53 Branding script has completed. 22:29:53,23 Add-On Manager in progress. 22:30:08,63 No MSDM key detected in BIOS. 22:30:12,26 Advanced Log-On screen has been enabled. 22:30:12,81 Set 'User Account Picture' registry entry applied. 22:30:13,26 'Registered Owner' registry entry corrected. 22:30:13,27 Detected 'defaultuser0', attempting to remove the folder... 22:30:14,11 Removal of 'defaultuser0' folder successful. 22:30:22,20 BIOS Mode: Legacy, Partition Type: MBR 22:30:22,49 HDD Controller Mode: [AHCI] 22:30:28,45 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. = ================================================================================ The Multi-OEM/Retail Project has now completed. Next time i will test with bios file (forgot it)
VMWare is updated last week. And i will retest with 14393 asap. It should pickup the MSDM key by default, standard win 10 does also. EDIT: Test with 14393.953 + bios442 pro + EFI, same result.
VMware must of changed something? VBox updated recently and reset my vm config file to default, i changed it back and it worked again for testing. I've not updated my VMware Player and that still works. Its still on 12.5.2 build-4638234.