Multi-OEM/Retail Project {MRP} - Mk3

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

 

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.

 

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...

 

You need to login to view this posts content.

 

I thought as much, one of those 'odd' Edition/OS's that does not allow anything it not like to run, similar to that Cloud Edition?