Multi OEM/Retail Project Build 06.12.2018

BaDshaH

Active Member
#1


Multi OEM/Retail Project Build 06.12.2018 | File size: 87.4 MB

100+ OEM's:
• Acer • Advent • Action • Alienware • AOC • Aquarius • ASRock • Asus • ATcomputers • Bangho • Beko • BenQ • BGH-SA • ByteSpeed • Casper • CCE • chiliGREEN • Compaq • crea • CZC • Dell • Depo • digimix • ECS • eMachines • Epson • Equus • Everex • Excimer • EXO • Exper • Extra • Founder • FSC • Fujitsu • Gateway • Genuine • Gericom • Gigabyte • Greatwall • Haier • Hannspree • Hasee • HCL • Hedy • Higrade • HP • Hyrican • IBM • Impression • Infinity • Insys • Intelbras • iQon • Itautec • Jetway • JooyonTech • Kohjinsha • Kouziro • Kraftway • KSystems • Lanix • Lenovo • LG • M&A Technology • Maxdata • Mecer • Medion • Megaware • Mesh • Mitac • Mouse • MSI • NEC • Nokia • Olidata • Olivetti • Onkyo • OQO • Packard Bell • Panasonic • Paradigit • Paragon • Philco • Positivo • PowerSpec • Prolink • qbex • Quanmax • RMplc • Rover • Samsung • SCC • Semp Toshiba • Seneca • Sharp • Sony • Stone • Synnex • Systemax • Tangent • Targa • Tarox • TCL • TTL • Tongfang • Toshiba • Trigem • Twinhead • Velocity • Vestel • Viewsonic • viliv • WD Corporation • Wortmann • xplore • Zoostorm • ZT ~incl. (branding only): BioStar • Foxconn • Intel • M$ $urface • VirtualBox • VMware

OEM's Branded = 133~

•BIOS Mode supported: Legacy and/or UEFI

• You can force install 'ANY' brand theme by reading and using the Force_Theme_[readme].txt

Editions for OEM Activation:
• Server 2008 • Server 2008 R2 • Server 2012 • Server 2012 R2
• Win10... • Home • Pro
• Win8.x... • Core • Pro
• Win7..... • Starter • Home Basic • Home Premium • Pro • Ultimate
• Vista..... • Starter • Home Basic • Home Premium • Business • Ultimate

Objective - add $oem$ folder to .iso /usb.

• $oem$ method can be used to apply activation & manufacturer brand to your Win10 • Win 8.x • Win 7 • Vista '.iso'/usb
• NOTE:- PC needs (Win8.x and Win10 'OEM-DM' • Win7 '2.1 slic' • Vista '2.0 slic') bios to apply genuine oem activation.
• Project includes optional Telemetry disabling, (WinTel.cmd), for all supported OS's and adds domains to block through Route commands.
• Optional Retail activation method via online, if needed.

How To:
Win8.x|Win10
Place the downloaded '$oem$' folder in the 'sources' folder of your 'clean' iso, and add custom 'ei.cfg' file to the same 'sources' folder and edit|save iso. Windows will install the edition identified from 'ei.cfg' file. (Project 'Options' folder includes 'ei.cfg' instructions). OOBE.cmd will call tool that will extract embedded 'OEM-DM' key from bios (if exists), and apply the serial during installation.

Win7
Place the downloaded '$oem$' folder in the 'sources' folder of your 'clean' iso, and delete the 'ei.cfg' file from the same 'sources' folder and edit|save iso... during install you will have option to select the edition of 'Win7' you want installed (ie. Starter • Home Basic • Home Premium • Pro • Ultimate)... if you don't delete 'ei.cfg' file, that's OK, just means Ultimate will install by default.

Vista
Place the downloaded '$oem$' folder in the 'sources' folder of your 'clean' iso, and delete the 'PID.txt' file (if exists) from the same 'sources' folder and edit|save iso... during install you will have option to select the edition of 'Vista' you want installed (ie. Starter • Home Basic • Home Premium • Business • Ultimate)... if you don't delete 'PID.txt' file, that's OK, just means serial used on that file will determine edition installed.

• Please read the 'readme' files included in the download folder, for additional information.
• "UltraISO" recommended to edit|save your .iso, preserving 'bootable' image.

Editions for OEM Activation:
• Win10.. • Technical Preview • Consumer Preview
• Win8.x... • Core • Pro
• Win7.... • Starter • Home Basic • Home Premium • Pro • Ultimate
• Vista.... • Starter • Home Basic • Home Premium • Business • Ultimate
• (Vista-Win10) If not known edition, branding only takes place.

Objective - add $oem$ folder to .iso /usb.

• $oem$ method can be used to apply activation & manufacturer brand to your Win10 • Win 8.x • Win 7 • Vista '.iso'/usb
• NOTE:- PC needs (Win8.x and Win10 'OEM-DM' • Win7 '2.1 slic' • Vista '2.0 slic') bios to apply genuine oem activation.

How To:
Win 10
Place the downloaded '$oem$' folder in the 'sources' folder of your 'clean' iso, and edit|save iso. OOBE.cmd (Install.cmd) will extract embedded 'OEM-DM' serial from bios (if exists), and apply the serial during installation.
Win8.1
Place the downloaded '$oem$' folder in the 'sources' folder of your 'clean' iso, and add custom 'ei.cfg' file to the same 'sources' folder and edit|save iso. Windows will install the edition identified from 'ei.cfg' file. (Project 'Options' folder includes 'ei.cfg' instructions). OOBE.cmd (Install.cmd) will extract embedded 'OEM-DM' serial from bios (if exists), and apply the serial during installation.
Win8.0
Place the downloaded '$oem$' folder in the 'sources' folder of your 'clean' iso, and edit|save iso. Windows will install the edition that matches the embedded 'OEM-DM' serial in your bios (if exists).
Win7
Place the downloaded '$oem$' folder in the 'sources' folder of your 'clean' iso, and delete the 'ei.cfg' file from the same 'sources' folder and edit|save iso... during install you will have option to select the edition of 'Win7' you want installed (ie. Starter • Home Basic • Home Premium • Pro • Ultimate)... if you don't delete 'ei.cfg' file, that's OK, just means Ultimate will install by default.

Vista
Place the downloaded '$oem$' folder in the 'sources' folder of your 'clean' iso, and delete the 'PID.txt' file (if exists) from the same 'sources' folder and edit|save iso... during install you will have option to select the edition of 'Vista' you want installed (ie. Starter • Home Basic • Home Premium • Business • Ultimate)... if you don't delete 'PID.txt' file, that's OK, just means serial used on that file will determine edition installed.

• Please read the 'readme' files included in the download folder, for additional information
• UltraISO recommended to edit|save your .iso, preserving 'bootable' image

Included link for images to be used with System Brand Changer if users prefer using a desktop branding tool with a nice gui, created by Alphawaves.

Whats New:
+ Added new Locale information from Microsoft's Locale database. Any that is missing then the standard data will appear.
+ Added extended KMS/MAK data such as renewal times etc. Note it does not detect MS Office if you have
pre-installed that. Maybe another time it is not a requirement as MRP is designed for OS management.
+ Fixed a glitch in which on Windows 7 Czech language (maybe others too) the project would abort due to some
strange reason. Have hopefully cured it with a bit of tweaking. Thanks to JanCerny and Dubioza Kolektiv for
letting me know. Also a big thanks to Enthousiast for testing my edits/fixes with CS-CZ Windows 7.
+ Added a new option for Windows 10 Only, remove tiles from the Start Menu, this does NOT uninstall any apps/programs
you will have to do that manually after setup has completed. But it does leave you with a 'slim' menu and not the
large sided one. Note this also transfers to any new user created by OS design.
+ In addition to the above option, if you have your own LayoutModification.XML file with tiles set up how you like you
can use that with MRP too! Just copy your XML file to the Scripts folder where decompile.exe is located and MRP will
detect this file and use it instead of the preset MRP 'blank' one. You will see a note in the project.log that the file
is beyond MRP's control and that YOU are responsible for its contents and that it is set out correctly.
+ Slight re-design of the project.log output, this is a phased operation and is the start of the transformation.
+ MRPConfigCreator has been updated to v9.0 to include the new option.
++ Note for Insider Core/Home Editions the Windows Mode Dark theme does not always work not sure why as the registry entries
are correct. This may be a glitch with M$ OS code and nothing can be done about it at present. For Pro and higher Editions
a logout/login or reboot cycle should set the mode(s) correctly. It seems like M$ are forcing the 'Light Theme' regardless of
the users wishes, (nothing unusual there!), I will find a work-around for it at some point.
++ Note2: It is wise to do a reboot/logout cycle after setup has completed anyway to make sure all options/theme elements have been set correctly.

HOMEPAGE
Code:
https://forums.mydigitallife.net


Download From UploadGig

Code:
https://uploadgig.com/file/download/8cB6955032dcD1e1/BaDshaH_Multi_OEMRetail_Project_06.12.2018.rar
Download From Rapidgator

Code:
https://rapidgator.net/file/bef75757127c7849adcd91632ce8f26b







 
Top