Multi-OEM/Retail Project {MRP} - Mk3

Discussion in 'MDL Projects and Applications' started by mxman2k, Oct 15, 2016.

  1. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    1,621
    3,230
    60
    #1 mxman2k, Oct 15, 2016
    Last edited: Apr 6, 2018
    With kind permission from The_Guardian, the Multi-OEM project will continue to be updated here...

    For just the Query Tool {QT) see 2nd post for download link.

    Important Note: This project will ONLY activate a OEM system with either a valid SLIC (Vista/7/Server) or MSDM (8.x/10) present in the BIOS, it does NOT contain any 'other' method to activate apart from HWID (W10) or a valid retail key you own which can be entered via PID.txt.

    Project Only Works In OOBE Mode.


    Recommend running the Query Tool "first" before installation, (See Notes below).

    100+ OEM's:
    • Acer • Advent • Action • Alienware • AOC • Aquarius • ASI •ASRock • Asus • ATcomputers • ASI • 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 • Hampoo • 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 • Novatech • PeaQ •VirtualBox • VMware • Hyper-V • Supermicro • XEN • QEMU • ZOTAC
    OEM's Branded = 131~

    • BIOS Mode supported: Legacy MBR and/or UEFI GPT

    • You can force install 'ANY' brand theme by using the Config Creator to select the theme you wish to use of the brands above, or 'Custom' in the list for your own customized branding then save the MRPConfig.ini in the Scripts folder along side the DeCompile etc. See ReadMe files for details.

    Editions supported 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

    These should all brand providing DMI information is present. (N/KN/K/E/S/SN/G/GN and a few others.)

    Core, CoreN, CoreSingleLanguage, CoreConnectedSingleLanguage, SingleLanguage, CoreConnected.

    (Windows 10 S) : Cloud, CloudE, CloudN - Note needs special attention to work!

    Education, EducationN, EducationE, EducationK, EducationKN.

    Enterprise, EnterpriseN, EnterpriseE, EnterpriseSN, EnterpriseSN, EnterpriseK, EnterpriseKN, EnterpriseSubscription, EnterpriseSubscriptionN, EnterpriseG, EnterpriseGN.

    Ultimate, UltimateN, UltimateE, UltimateK, UltimateKN.

    Business, BusinessN, BusinessE, BusinessK, BusinessKN.

    Professional, ProfessionalWMC, ProfessionalN, ProfessionalE, ProfessionalK, ProfessionalKN, ProfessionalEducation, ProfessionalEducationN, ProfessionalCountrySpecific, ProfessionalSingleLanguage, ProfessionalWorkStation, ProfessionalWorkStationN.

    PPIPro - For Surface Pro.

    HomePremium, HomePremiumN, HomePremiumE, HomePremiumK, HomePremiumKN.

    HomeBasic, HomeBasicN, HomeBasicE, HomeBasicK, HomeBasicKN.

    Starter, StarterN, StarterE, StarterK, StarterKN.

    Server 2008, 2008R2, 2012, 2012R2, 2016 now branding, also some can now be OEM SLP activated!, see Server-ReadMe.txt for more details in MRP archive.

    Note: Some SKU/Editions may not 'exist' as such but have included them for conformity.

    Evaluation versions can be branded only. They cannot be activated via OEM methods.

    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.

    Win8.x|Win10
    Place the downloaded '$oem$' folder in the 'Sources' folder of your 'clean' ISO/USB, and add custom 'ei.cfg' file to the same 'Sources' folder and edit|save the ISO, if your using a ISO file. Windows will install the Edition identified within the 'ei.cfg' file if the Edition is set.

    If you use the ei.cfg provided, (Project's 'Optional/win10' folder includes 'ei.cfg' and instructions), it will allow you to select which Edition to install. On some you may also need the PID.txt added with the serial number of the Edition to force the required Edition.

    Using the ei.cfg and/or PID.txt file(s) will bypass the Windows Setup's way of detecting the MSDM and installing using that information and ignoring the oobe stage where MRP etc is run from.

    MRP will extract embedded 'OEM-DM' key from bios (if exists), and apply the serial during installation, only if the Edition installed matches the MSDM key.

    Note: Win8.0 login background limitation, you cannot change system login background color to an external image.

    Win7
    Place the downloaded '$oem$' folder in the 'sources' folder of your 'clean' ISO/USB, and delete the 'ei.cfg' file from the same 'sources' folder and edit|save the ISO, if you are using 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 whichever version the ISO/Image was for will install by default, (Home/Pro etc).

    You can also use the PID.txt file to 'force' a certain Edition.

    Vista
    Place the downloaded '$oem$' folder in the 'Sources' folder of your 'clean' ISO/USB, and delete the 'PID.txt' file (if exists) from the same 'Sources' folder and edit|save the ISO, if you are using 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 in that file will determine Edition installed.

    Server Editions
    Place the downloaded '$oem$' folder in the 'Sources' folder of your 'clean' ISO/USB, and edit|save the ISO, if you are using ISO...

    During install select the Edition of 'Server' you want installed making sure it has the GUI installation, NOT the core only version!

    Please read the 'Server-ReadMe.txt' file included in the download folder, for additional information.
    * Please read the 'readme' files included in the downloaded archives for additional information.

    * "UltraISO" recommended to edit|save your .iso, preserving 'bootable' image. You can use any ISO authorizing program if you wish as long as it saves the bootable image.

    VirusTotal Results:
    OEM Query Tool: (Due to compilation method. False positive, it is safe)
    Multi OEM Project: (Due to extraction method. False positive, it is safe)


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

    Size of $oem$ folder that is to be added to usb/dvd windows media = 40 Mb {Approximate}

    Please see the 'IMPORTANT - Read Me.txt' file within the project's folder for any latest changes etc.

    All change logs will now be within the respective archives this is to save updating this post every time.

    Change log 9-4-2016:
    -Updated additional reg files in oobe.cmd to address F8 function key for Window 10 builds. (Thanks EFA11)
    Note: This option has now been moved to the MRPConfig.ini file as part of the user options via the MRPConfigCreator.
    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.

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

    The QT will also tell you your MSDM key, its brand name and what edition it is for.

    When saving the report any sensitive information such as any Keys, MSDM table and tag numbers are omitted from the saved report so that if you need to post the report text file in the thread then no sensitive/personal information is shown.

    If you save the report and there is a MSDM key present in your computer then the QT will also save the MSDM key into a separate text file called 'QT_MSDM-KeyInfo.txt' for your reference. This is YOUR key for that computer ONLY -- do not post it!
    -The_Guardian for allowing me to keep the project alive.
    -Collaborative effort for Win 10 telemetry.
    -Alphawaves = Creating needed tools and advice.
    -alexwilson = Sharing Win10 logon background method.
    -Daz = Help and advice.
    -xinso = Scripting help and testing.
    -abbodi1406 = Scripting help with project and query tool.
    -FreeStyler = Cert Collection.
    -s1ave77 = Scripting help, MSDM key information/scripting. Many thanks.
    -hmmurdock = Scripting advice.
    -elnenedelinares = OEM contributor.
    -ZerOx16x = OEM contributor.
    -Baltagy = OEM contributor and BETA testing many project revisions.
    -555LE = OEM contributor.
    -M&J = Testing.
    -EFA11 = Additional reg file for Win10 f8 function. {R.I.P EFA11}.
    -l30 = Testing.
    -Snuffy = Testing.
    -apologized = Testing. Server branding beta testing/reports, many thanks for your help.
    -Mr.X = Testing, OEM contributor, Glitch finder!, Beta tester.
    -Tito = Vmware bios help.
    -rockyanexpert = Testing and useful info regarding Win10 Anniversary Builds.
    -user_hidden = For 7zip compression information.
    -Enthousiast = Testing, reports, more testing and even more testing of beta's and RC version.
    -MMIKEE = Bug hunting, testing and reports.
    -twiztidwolf = OEM contributor.
    -mad_max = Reporting the critical dummy/corrupt MSDM table bug, feedback.
    -tcntad = Reporting the Server 2016 Desktop Experience error.
    -b01m = Reporting a glitch in the "Switched Edition's" area in the Query Tool, also for testing the QT.
    -JanCerny = Supermicro OEM theme set. Also helping with bug fixes.
    -bhtbht - Bug report.

    -Other MDL members who contributed to the original and new project.
    -Bob 65536 for the KeyInfo.xx.exe program that made the MSDM check/info happen. Many thanks Bob.

    And finally a big thanks to you for using the OEM Project and to those that give reports and feedback.
    End users can edit/extract or omit the OEM's.7z file only.

    Use 7zip to extract the OEM's.7z file if you wish to edit anything within the brand folders. (See below)

    DeCompile.exe, OOBE.cmd are required!


    If you do edit the OEM's.7z file please make sure when you re-compress it that the file structure/layout is exactly as it was, or the project may use the Windows default theme as a fail-safe procedure. You can delete any brand folders not required to make the archive smaller, but you MUST have at least ONE folder , be it a OEM brand or just CUSTOM, within OEM's.7z.

    Important: If you use a 3rd party 'homebrew' ISO for installing Windows from such groups as Gen2 please be aware that due to their 'pre-activation' and 'OEM additions' this may cause your install to fail or 'hang' due to conflicts with MRP.

    Download Links on next post.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  2. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    1,621
    3,230
    60
    #2 mxman2k, Oct 15, 2016
    Last edited: Apr 7, 2018
    (OP)
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    1,621
    3,230
    60
    #3 mxman2k, Oct 17, 2016
    Last edited: Apr 20, 2018 at 22:09
    (OP)
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  4. apologized

    apologized MDL Addicted

    Nov 29, 2012
    886
    502
    30
    #4 apologized, Oct 17, 2016
    Last edited by a moderator: Apr 20, 2017
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    1,621
    3,230
    60
    @apologized Thanks for your report.

    Will zip next beta and give hash's i thought i had uploaded the zipped version oops :eek:.

    Can you access the HP pc that got the MSI bit wrong? Want to see if my changes has corrected that glitch and shows HP for theme and activation. I have tested with demo DMI/SLIC info to mimic that pc and it seemed to be corrected. But testing on the real pc might throw me a curve ball lol.

    Many thanks Mx.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  6. apologized

    apologized MDL Addicted

    Nov 29, 2012
    886
    502
    30
    #6 apologized, Oct 17, 2016
    Last edited by a moderator: Apr 20, 2017
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  7. The_Guardian

    The_Guardian Contributor

    May 7, 2012
    2,003
    6,701
    90
    When I get home later today I will send you info for pastebin link so you can edit it yourself mxman2k. I will setup a simple pass for you and send the info to you. It will then be your pastebin. :) Its on my ext hdd so will send to you this evening when I get back home.
     
  8. woarke

    woarke MDL Novice

    Apr 8, 2015
    25
    21
    0
    #8 woarke, Oct 17, 2016
    Last edited by a moderator: Apr 20, 2017
  9. The_Guardian

    The_Guardian Contributor

    May 7, 2012
    2,003
    6,701
    90
    #9 The_Guardian, Oct 18, 2016
    Last edited: Oct 18, 2016
    That is because user profiles are separate in win10 anniversary versions. Trying to compare this OS to past ones are since-less. How are we to know what user acct gets what from oobe mode when user accts are not setup yet? Remember oobe mode is done before user accts are setup, plus every user has different preferences. o_O

    Even better, how would we know what the passwords are for each user acct created?

    This would fall on "system administrators" to setup user accts if needed. Now I sound like M$. lmao! Come on, that is funny. :biggrin:
     
  10. The_Guardian

    The_Guardian Contributor

    May 7, 2012
    2,003
    6,701
    90
    From the looks of things in the query results seems as if the the first two queries are not checking because in the HP's above it should have queried those also but it only set MAN for #4, it should be #1 since HP is in the #1 query. This might cause issues for some. Thought I would point that out. I am still around to help if needed.
     
  11. woarke

    woarke MDL Novice

    Apr 8, 2015
    25
    21
    0
    I didn't want to blame someone. Was just wondering why it works for account picture on start menu and not on logon screen. Is there any possibility to get a custom default picture for all (future) user profiles?

    True, that sounds like M$ :suicide:
     
  12. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    1,621
    3,230
    60
    Thanks for the reports :worthy:, will address the ordering of checks as i can use the data to make a demo clone and tweak the check ordering and make a new Query Tool Beta.

    Regarding the W10 AU (RS1), when a new user is created, it seems to run a mini oobe as noticed when logging into that new user for the first time it does the We're Happy Your Here stuff... As the project is auto deleted after the initial full install/setup there is no files for it to call upon.

    There maybe a way that during the initial install that things could be copied over to the default 'all user' profile but then any new user would have the same OEM user image also any Customized options that may be set during the original setup/oobe stage which may not be a desired result.

    Will see if it can be done in a future update of the project. Have wrote it on my 'to do' list but cannot promise if it will be possible as the way W10 has changed since the first release and as we know M$ like to change things just for changes sake and every update seems to change/break things!

    Have removed BETA Query Tool Beta 3 Link in post #3 - New beta being worked on, will post link soon. :biggrin:
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  13. Mr.X

    Mr.X MDL Guru

    Jul 14, 2013
    5,682
    13,109
    180
    Of course M$ does like to change things, they go against their corporate interests. They have eyes watching and following this thread, I bet my life on it LOL
     
  14. BALTAGY

    BALTAGY MDL Member

    Dec 23, 2014
    161
    81
    10
    I will save my problem to the last after you finish fixing the conflicts since i'm the only one who have it maybe you can know what's really going on with me lol

    They are busy taking selfy's instant of making a stable system or updates lol, but i'm sure they are here :throw:
     
  15. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    1,621
    3,230
    60
    OK , Having re-adjusted the DMI checking procedure it will now pick theme id #1 if it matches the database, or id #2 etc, if no dmi info it will try to use the SLIC name as a final attempt then give up lol.

    Now the conflict side is the pain at the moment. However there is a solution of sorts... (which would make my life a bit easier lol).

    I could relax/remove the conflict resolution side, to allow slic mods of a different make/name to the board's DMI.

    Example: ASUSTek board with a DELL slic mod. At present things get complicated and could pick the theme (ASUS) as the activation and of course no activation because it will think to use ASUS 'slic' instead of DELL.

    I know the SLIC mod should ideally be set to the boards maker to make it appear all legit. But sometimes that isn't always possible, modding a few bios's myself sometimes the matching named SLIC does not fit for some reason and have had to choose another make to be able to complete the SLIC insertion (something about how compressible it is).

    The FORCE_THEME will still be active if you wish to theme your board as the SLIC or whatever your desire, the PC will be activated with whatever slic is present - Vista/7 only.

    Win 8.x/10+ will not be affected just be themed from DMI as normal or force_themed as required.

    So this is where i am at present and hence asking those that will be using the project how would you like it to progress.

    I have done the Query Tool BETA 4 with changes in DMI checking but left the conflict part in place for now, will await your replies.

    Depending on how many choose which way to go forward I will then put up a link to the QT Beta 4 with the changes.

    Once established how the majority wish to proceed then once beta testing has completed it will be added in the main project and all links updated with the new updated version.

    You can reply in the thread or via PM your vote to keep or relax, (ideally PM as this will keep the thread tidy). I will total up and which gets the most votes will be implemented into the main project also. Will leave the voting open until Saturday evening UK GMT to allow a reasonable time frame due to work and time zone differences plus real life in general.

    Many thanks, Mx
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  16. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    1,621
    3,230
    60
    @BALTAGY I will do my best to help you.

    As they say "where there's a will there's a way"
    (Cambridge English Dictionary : saying used to mean that if you are determined enough, you can find a way to achieve what you want, even if it is very difficult)

    :D
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  17. The_Guardian

    The_Guardian Contributor

    May 7, 2012
    2,003
    6,701
    90
    That would please you but what about others? Cant please everyone but to please one individual and upset many others isnt the solution either. In order to change system pics and images you will need to edit the dll files. They will be kicked out on updates so will be a cat and mouse game. Look at Alphawaves thread on this subject. He is always updating it so in my opinion, not worth it. Better to let user edit their own user profiles in windows and leave it at that. Forget about system pics and images. This is my opinion.

    Win7 days are over. lol
     
  18. woarke

    woarke MDL Novice

    Apr 8, 2015
    25
    21
    0
    This is exactly what I want. Same image for every user(of course as an optional component in the project if possible). What do you mean by "also any Customized options that may be set during the original setup/oobe stage which may not be a desired result"?
     
  19. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    1,621
    3,230
    60
    The also is meaning when you are installing the OS during the oobe screens to setup the main first user you get to the Customize screens (its similar on vista/7), you can alter what you wish, on windows 10 you get to turn off or on things like smartscreen, location etc then that 'sweetheart' called Cortana [sic]. Those options if changed could be also transferred inadvertently to every new user created by copying to the default user profile which may not be wanted or be able to be changed later for the additional user(s). It can also cause system wide instabilities when playing with the default user files.

    As The_Guardian mentioned it's all contained with system DLL files and would be a constant battle every cumulative monthly update to redo those DLL's.

    It would therefore be easier to let the new user add their own picture/settings which would be handled by the Operating System.

    The idea of the project is to brand the computer, (activate via slic/MSDM key where possible), set the main user picture/logos like the OEM manufactures do. Additional created users are optional to the computer owner and are added and customized as required.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  20. Mr.X

    Mr.X MDL Guru

    Jul 14, 2013
    5,682
    13,109
    180
    I suscribe, agreed, support and second this comment LOL
    I wanted to express that myself before but was a bit shy to do it as I don't want a flame war against me :p
    This project should focus exactly on this features above anything else...