Hello everyone, I have a question regarding the OEM branding option of MRP. I want to just use the MRP Config Creator without applying any OEM branding to the target PC/Laptop… Can I just use the General tab in MRP Config Creator: Custom Theme and select WindowsDefault? Will that be enough? I do not want any branding or Device Model Name to be applied at the end of the installation. Do I need to modify the OEM's.7z file to achieve that result? Thanks
Simply add the $oem$ folder from the archive as normal but then delete the oem's.7z file , MRP will detect no oem's.7z file and ignore any branding, on win7/vista/server installs-- it will still attempt to activate via the SLIC methods, also the MSDM side will still be operative. But no branding will happen, as no brands for it to use. Still add your config.ini file in the folder next to decompile.exe and oobe.cmd and MRP will do all your option/tweaks.
I know the read me files are a bit out of date, but i think that is mentioned already as it was one 'feature' of the original project that if not oem's.7z file found it would ignore any branding.
Oh the lovely Server installs At least that update to the main code i added so that when a Server is detected it will turn off the 'Run-MRP-Silently' option
As i mentioned a few posts ago, on Server installations, as they so involved, it was best to make sure that all info windows was shown because if there was any error occurred , - more so in the features add-on - it could totally shaft the Server install, rare but it could happen, so to safe guard against that i made the choice not to hide any information screens. Server's are very fussy on certain aspects and such like the theme side if used, it requires a couple of reboots sometimes to make the theme show due to the extra tweaks needed to make the theme manager operate...
I still shudder at the thought of all those hours and days spent getting Servers to theme, it not 100% perfect but its the best that can be done, those that use the W10 kernel are more easier to work with in that respect but they can still throw a curve ball when something they not like is fiddled with
Code: Installation Type : Server Server 2019 Is a small cosmetic glitch in the QT hopefully i will get that sorted as i very much doubt that the OS has two 'Server' references in the same line within the kernel! There again it is m$ and we know that there is some sloppy coding going on
Server Server shows for Server 2019 and beyond only. Does not show in reports from Server 2016 or below. Nonsense entries did also appear before, e. g. Server 2008: Code: Version {Full Name} : Microsoftr Windows Serverr 2008 Standard where it included the "Reserved" mark but cleaned up the brackets around it.
The results in the qt that shows the '2009' etc is from the registry returned value, may have to see if there is a better method to find that data. I have tried to find the expire date for insider builds but it not in the registry or via wmic, i think that is stored within a dll etc that contains the timebomb stuff? There are a few bits to fix in the qt's results which i will get round to as soon as i can.
ReleaseId = 2009 DisplayVersion = 21H2 maybe the timebomb is controled/shown with Kernel-ExpirationDate Product Policy
Hello, I have a little problem with iso en_windows_10_iot_enterprise_ltsc_2019_x64_dvd_a1aa819f.iso OOBE.cmd is not executed during setup A solution?
Im not sure that IoT allows oobe.cmd or even setupcomplete.cmd to run Have you put in the ei.cfg file in the sources folder , i know that tells Windows setup to ignore checking for MSDM and also allows oobe.cmd etc to run... Not sure if a PID.txt file with the IoT key in that is needed as well, that file is placed in Sources folder too.. I personally not tried IoT ones so i cannot say for sure it even allows oobe.cmd etc when using the above two methods...