Query tool updated to v14 build 2. Changed compilation - now more compact. Also adjusted the DMI parsing method. Download link updated. =============== MRP will have a slight update soon, added 3 SKU's: EnterpriseEval EnterpriseEvalN PPIPro (Which i believe is for the Microsoft Surface Pro 64 bit.)
I included them as I am sure someone will attempt to try the MRP on those SKU's, so covered a few more bases so to speak
Main Project Updated! MRP has been tweaked and updated. Revision 35 PPIPro SKU name added to cover Surface Pro (x64). Tweaked scripts to remove redundant/duplicated code. Added option to auto name the SystemDrive with the Windows Version and SKU. See OOBE.CMD for details, it is OFF by default. Paste.co link Updated. Over 500 downloads in a few days since last MRP update.
Created a beta test MRP for Server editions... I removed my beta test download as i was not sure it worked as my download of Server 2016 was so slow and at the time was all theory. Finally it downloaded... Selected Server 2016 Datacentre x64 (RS1) with Desktop Experience from the list of Editions displayed to install. There was no editing of the WIM just added $oem$ folder and remade the ISO. First attempt at Server Standard failed part way through the setup, think this was due to me setting United Kingdom as keyboard. So 2nd attempt used Datacenter and left as 'US' on all location/Keyboard stuff. After the entering of username , then making a strong password grr, it finally started the OOBE, it opens a CMD window with nothing in it? I did NOT close that as i knew it must be the oobe section in progress. Then came a error 'No Instance Available' - probably one of the registry queries not correct? Anyway I left it alone and a few minutes later it vanished, desktop appeared with background. Then my user tweaks was installing - another CMD window saying please wait... Nice! Once all that done, the server manager window popped up. Closed that, and checked if the branding had worked elsewhere. It had put userpic in, but lock screen was a default one? So apart from the odd way server calls oobe etc it 'seems' to have worked. Here is a project.log of the results: Spoiler Code: Multi-OEM/Retail Project Version : 161218-R36-BETA [MRP/MDL] Files present and extracted successfully. NOTE: This is a BETA release and MRP may not work as expected. OEM's folder detected. OEM's folder structure seems OK. OS Installation Date: Sun 12/18/2016 17:30:08.30 Windows Server 2016 Datacenter x64 version found. 17:30:08.44 Server Edition installed. 17:30:08.45 Build Version: 14393.0.amd64fre.rs1_release.160715-1616 17:30:08.45 Warning, Server SKU detected, branding may fail. DMI BIOS Information #1 CS PRODUCT NAME : [Desktop] #2 CS MODEL : [Desktop] #4 CS VENDOR : [MSI-PC] #5 CS SYSTEM MNF : [MSI-PC] #6 BASEBOARD MNF : [value] #8 BIOS ID/VER : [MSI_NB] 17:30:14.33 MSI [#4] manufacture will be used for theme/branding. 17:30:14.33 No PIDKEY available in MRP database for this Edition/SKU. 17:30:14.35 Force theme text file not present. 17:30:15.09 System Product Name, not defined. 17:30:15.10 Backgrounds folder created. 17:30:15.13 Attempting branding for Server {experimental}. 17:30:15.13 OOBE.xml file deleted. 17:30:15.13 User.bmp replaced. 17:30:15.18 User.png replaced. 17:30:15.21 User-40.png replaced. 17:30:15.21 User-32.png replaced. 17:30:15.23 User-48.png replaced. 17:30:15.23 User-192.png replaced. 17:30:15.23 Img105.jpg replaced. 17:30:15.62 Aero theme replaced. 17:30:15.97 Img100.jpg replaced. 17:30:16.04 Error, $OEM$.theme replacement failed. 17:30:16.04 Info folder created. 17:30:16.07 Theme files transferred to System32\oobe\Info folder. 17:30:16.41 Cleanup registry entry added. 17:30:16.41 Installation script has completed. 17:34:20.00 BIOS Mode: Legacy, Partition Type: MBR. 17:34:20.04 Device not connected to the Internet, online license check failed. 17:34:33.05 License Status: Error, not licensed. 17:34:33.08 UserTweaks.cmd present attempting to apply. 17:34:33.08 UserTweaks.cmd completed. 17:36:12.43 Cleanup script has completed. ============================================================================ Please Note: It is advisable to logout or reboot your computer when possible to allow the User and Log-on background pictures to finalize. ============================================================================ I had expected some errors, well a LOT more than i got! Only the $OEM$.theme failed, which i had thought it would as it basically Windows 10 at heart and not 8 or 7 kernel. If anyone requires the beta test DeCompile.exe let me know and i will post a download link. Would be nice to see how MRP reacts to other Server SKU's such as R2, 2012 etc. Sadly I don't have the internet allowance to download any other Server ISO's this month to test. No other changes are added only the server testing part.
srv2008 (std) Spoiler Code: Multi-OEM/Retail Project Version : 161218-R36-BETA [MRP/MDL] Files present and extracted successfully. NOTE: This is a BETA release and MRP may not work as expected. OEM's folder detected. OEM's folder structure seems OK. OS Installation Date: 19/12/2016 0:20:09,31 Windows Server (R) 2008 Standard x86 version found. 0:20:09,37 Server Edition installed. 0:20:09,37 Build Version: 6002.18005.x86fre.lh_sp2rtm.090410-1830 0:20:09,37 Warning, Server SKU detected, branding may fail. DMI BIOS Information #1 CS PRODUCT NAME : [VMware Virtual Platform] #2 CS MODEL : [VMware Virtual Platform] #4 CS VENDOR : [VMware, Inc.] #5 CS SYSTEM MNF : [VMware, Inc.] #6 BASEBOARD MNF : [Intel Corporation] #8 BIOS ID/VER : [DELL] 0:20:11,77 VM Bios ID conflict resolution enabled. VMWARE resolved as DELL [#8]. 0:20:11,77 DELL [VMWARE] manufacture will be used for theme/branding. 0:20:11,77 No PIDKEY available in MRP database for this Edition/SKU. 0:20:11,77 Force theme text file not present. 0:20:14,21 System Product Name - 'VMware Virtual Platform' detected and applied. 0:20:14,21 Backgrounds folder created. 0:20:14,21 Attempting branding for Server {experimental}. 0:20:14,21 OOBE.xml file deleted. 0:20:14,21 User.bmp replaced. 0:20:14,22 Error, user.png replacement failed. 0:20:14,22 Error, user-40.png replacement failed. 0:20:14,22 Error, user-32.png replacement failed. 0:20:14,22 Error, user-48.png replacement failed. 0:20:14,22 Error, user-192.png replacement failed. 0:20:14,24 Error, img105.jpg replacement failed 0:20:14,24 Aero theme replaced. 0:20:14,36 Error, aero theme replacement failed. 0:20:14,36 Error, img100.jpg replacement failed. 0:20:14,36 Theme replaced with $OEM$.theme. 0:20:14,36 Info folder created. 0:20:14,38 Theme files transferred to System32\oobe\Info folder. 0:20:14,63 Cleanup registry entry added. 0:20:14,63 Installation script has completed. 0:21:18,08 BIOS Mode: Legacy, Partition Type: MBR. 0:21:18,08 Device not connected to the Internet, online license check failed. 0:21:23,82 License Status: Error, not licensed. 0:21:23,83 Cleanup script has completed. ============================================================================ Please Note: It is advisable to logout or reboot your computer when possible to allow the User and Log-on background pictures to finalize. ============================================================================ srv2008r2 (std) Spoiler Code: Multi-OEM/Retail Project Version : 161218-R36-BETA [MRP/MDL] Files present and extracted successfully. NOTE: This is a BETA release and MRP may not work as expected. OEM's folder detected. OEM's folder structure seems OK. OS Installation Date: 19/12/2016 0:21:41,01 Windows Server 2008 R2 Standard x64 version found. 0:21:41,06 Server Edition installed. 0:21:41,06 Build Version: 7601.17514.amd64fre.win7sp1_rtm.101119-1850 0:21:41,06 Warning, Server SKU detected, branding may fail. DMI BIOS Information #1 CS PRODUCT NAME : [VMware Virtual Platform] #2 CS MODEL : [VMware Virtual Platform] #4 CS VENDOR : [VMware, Inc.] #5 CS SYSTEM MNF : [VMware, Inc.] #6 BASEBOARD MNF : [Intel Corporation] #8 BIOS ID/VER : [DELL] 0:21:42,76 VM Bios ID conflict resolution enabled. VMWARE resolved as DELL [#8]. 0:21:42,76 DELL [VMWARE] manufacture will be used for theme/branding. 0:21:42,76 No PIDKEY available in MRP database for this Edition/SKU. 0:21:42,76 Force theme text file not present. 0:21:44,13 System Product Name - 'VMware Virtual Platform' detected and applied. 0:21:44,13 Backgrounds folder created. 0:21:44,13 Attempting branding for Server {experimental}. 0:21:44,13 OOBE.xml file deleted. 0:21:44,13 User.bmp replaced. 0:21:44,13 Error, user.png replacement failed. 0:21:44,13 Error, user-40.png replacement failed. 0:21:44,13 Error, user-32.png replacement failed. 0:21:44,13 Error, user-48.png replacement failed. 0:21:44,13 Error, user-192.png replacement failed. 0:21:44,13 Error, img105.jpg replacement failed 0:21:44,13 Aero theme replaced. 0:21:44,16 Error, aero theme replacement failed. 0:21:44,16 Error, img100.jpg replacement failed. 0:21:44,16 Theme replaced with $OEM$.theme. 0:21:44,16 Info folder created. 0:21:44,18 Theme files transferred to System32\oobe\Info folder. 0:21:44,44 Cleanup registry entry added. 0:21:44,46 Installation script has completed. 0:23:58,59 BIOS Mode: Legacy, Partition Type: MBR. 0:23:59,38 License Status: Error, not licensed. 0:23:59,40 Cleanup script has completed. ============================================================================ Please Note: It is advisable to logout or reboot your computer when possible to allow the User and Log-on background pictures to finalize. ============================================================================ notice : no cmd window showed during installation or first log
Did the theme work? I know the errors will appear about user pics as R2 2008 i think is either win 8 or win 7 kernel. Those errors can be ignored if the userpic etc has worked.
The command window may of appeared on my VM as my PC was maxed out, so slowing the VM down. Plus was on a normal HDD and not a SSD, took almost an hour to install on my setup.
Think 2008 R2 had that problem before ? The CTRL-ALT-DEL background was missing on 2016 one too, even the lockscreen was a default one. Everything else was ok, user pic, logo's. Server is a very odd beast, i guess because it not really designed to be a 'normal' OS.
yeah 2008r2 is big problem if i remember when i tested with @The_Guardian that's why he drop digging on server
Its odd that it partially does the theme. On normal OS Core/Pro... the script is run as SYSTEM, but on Server it is run as ADMINISTRATOR regardless this may be one of the reasons themes not taking as the project does not have highest privileges....
When my internet allowance is reset i will download a 2008 R2 and do a test install with a new script to find out what 'user' it is actually using, Admin or SYSTEM and nose about other Registry bits to interrogate the OS during OOBE/Install, might shine some light on why it such a PITA OS. Many thanks for testing the beta. Not sure if we are getting closer to the goal of multi-OS branding yet lol.
ur welcome i bypass srv2012 for now cuz my file is corrupted i'm downloading new one & testing 2012r2 now
Thanks Hopefully my 'net is reset tomorrow. Its a pain as i told my ISP i had lost my job at end of this month and they dropped my speed and took off unlimited downloads grr, ah well shaved off a few GBP lol I have managed to sell a few bits and pieces to put a chunk of money in bank to cover all bills, rent, 'net etc until February. 10GB a month limit is a bit sad these days! But until i can stabilise my finances i guess it better than having no net at all.