Multi-OEM/Retail Project {MRP} - Mk3

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

  1. smod14

    smod14 MDL Novice

    May 18, 2020
    1
    1
    0
    Thanks.....
     
  2. grinch843

    grinch843 MDL Novice

    May 14, 2010
    3
    1
    0
    No biggie on reverting the changes, I'll just reload the system, if they want cortana that bad, they'll have to deal with it :)....... At least I know now what is causing it to happen.....

    Thanks and keep up the good work......
     
  3. rady-s

    rady-s MDL Novice

    Oct 31, 2015
    2
    1
    0
    Great job, thank you very much
     
  4. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    28,706
    43,616
    390
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. Carlos Detweiller

    Carlos Detweiller MDL Spinning Tortoise

    Dec 21, 2012
    3,685
    3,409
    120
    Just two things I noticed, now done with testing my 20H1 19041.208 image with MRP applied:
    1. Home/Core SKUs need two reboots before everything applies. I know from this topic that this is the way it is and to be expected.
    2. For the IoT Enterprise SKU, absolutely nothing was applied. Nada. Could this be due to the fact that IoT Enterprise uses an OEM꞉DM key by default and thus skipped OOBE completely? But then, it would have completely ignored ei.cfg as well. Can MRP be applied to IoT Enterprise as well (no biggie if not)?
     
  6. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    3,157
    7,709
    120
    I have thought about adding extra info for grfx cards etc but have put that on the to-do list when i make a full QT GUI, so that it is easier to show more within respective tabs. :)
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  7. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    3,157
    7,709
    120
    Regarding the IoT Enterprise, odd as i have tested on IoT and all was OK, theme etc, although the device did not have a MSDM table and i still used ei.cfg... :g:

    I will have a search through my logs that i save when testing to find that Log.

    The use of the ei.cfg file should of made the Setup ignore the MSDM, but then m$ do somethings totally opposite of what their 'documentation' explains at times!

    When i get a bit of time (or if @Enthousiast beats me to it) i will get a copy of the IoT SKU and do new tests with a MSDM via VMware to see if MRP or anything within OOBE.cmd etc is ran.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  8. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    28,706
    43,616
    390
    #5989 Enthousiast, May 23, 2020
    Last edited: May 23, 2020
    IIrc, oobe/setupcomplete.cmd and related stuff didn't run on IoT when i did the test a long time ago.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  9. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    28,706
    43,616
    390
    #5990 Enthousiast, May 23, 2020
    Last edited: May 24, 2020
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  10. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    3,157
    7,709
    120
    What is odd is that the QT is showing the licensing channel as OEM_DM -- so i am guessing m$ is just using the MSDM channel regardless. :g:

    I cannot find my log with IoT test so i may not of done one or it was such a long time ago the older logs was purged, my memory is a bit fuzzy as done so many installs etc :D
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  11. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    28,706
    43,616
    390
    IoT doesn't have a gVLK available either, it takes the same hwid as generated for normal enterprise and MAS can generate one after the install is finished too.

    On my previous tests it also didn't run MRP or any other $OEM$ project.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  12. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    3,157
    7,709
    120
    #5994 mxman2k, May 25, 2020
    Last edited: May 25, 2020
    (OP)
    Only details i can find about IoT and the licensing it has are:
    Code:
    -------------------GUID---------------    ------SKU Name------  --License Channel--
    {8ab9bdd1-1f67-4997-82d9-8878520837d9} -- Win 10 IoTEnterprise  --   MSDM
    {b68e61d2-68ca-4757-be45-0cc2f3e68eee} -- Win 10 IoTEnterprise  --   OEM-NONSLP
    
    Not sure why the ei.cfg way does not allow $oem$/oobe stuff to run as there is a non-slp {retail?} key way to activate which i would of assumed allowed things to be run via setupcomplete etc...

    Another one of those 'odd' SKU's that is available like CloudS was etc :D
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  13. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    28,706
    43,616
    390
    Normal enterprise will be better to use anyway, it has all licensing options onboard:)
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  14. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    3,157
    7,709
    120
    MRP 126 is at Test Candidate 3 stage, not a huge amount can be seen completed this time round, due to work commitments, but a few items done to make things work smoother. :)

    All being well the timeline for release will be early June.

    The Query Tool is progressing along too and will probably be ready before the MRP's release.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  15. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    28,706
    43,616
    390
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  16. mU$!c

    mU$!c MDL Novice

    May 28, 2020
    1
    1
    0
    I've loved this product for years. Thanks for keeping it going, my guys :) OEM edition of Windows have captured my design eye since Win 7 Ultimate 30-in-1 OEM by Orbit30. Yeah I know, no one has seen Orbit30 since the 2000's.
     
  17. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    3,157
    7,709
    120
    The main core of the project is the same as it was, mainly OEM branding, the other bits are just an added bonus if you wish to use them such as the options etc. :)

    Just using the oobe.cmd, decompile.exe and OEM's.7z the project will be almost identical to the original project, the only difference is more checks on the DMI side and a few improvements in other parts of that routine's code but other than that 90% the same.

    The addition of the MRPConfig.ini and the use of the Creator to make option selection easier makes tweaking the OS during install less of a hassle, if the end user so requires, plus there are over 160 options, most are later OS specific but a good section is for older OS's too.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  18. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    3,157
    7,709
    120
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...