Multi-OEM/Retail Project {MRP} - Mk3

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

  1. s1ave77

    s1ave77 Has left at his own request

    Aug 15, 2012
    16,093
    24,397
    340
    It's MSDM for VMware with generated key :cool2:.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  2. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    49,674
    103,510
    450
    It isn't a working key, just for VM/MRP/QT testing purposes:
    Code:
    will run QT39 as soon as the VM lets me :D
    
     
  3. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    6,317
    21,056
    210
    It looks like the Windows Setup has read the MSDM before the MRP and done a license switch during the reboot prior to the Username etc section of setup!

    So whatever they done for ProWS seems to affect other Editions as well?

    Technically the MRP MSDM section did the correct thing and NOT insert the Enterprise MSDM key, but Setup had other ideas. Not sure how to get around that. :g:
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  4. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    49,674
    103,510
    450
    It would be a bummer when people are restricted to the MSDM, if they have the bad luck having one :(
    Or have to keep license-switching after upgrade/reinstall.
     
  5. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    6,317
    21,056
    210
    Exactly, Its only my theory that this has happened as the log states:
    Code:
    [CMSDM] Processing MSDM Key...
    [CMSDM] -> Show WMIC/MSDM Edition/Channel Information.
    [CMSDM] -> {WMIC} OS Edition     : 'Professional'
    [CMSDM] -> {MSDM} KeyEditionID   : 'Enterprise'
    [CMSDM] -> {MSDM} ChannelID      : 'MSDM'
    [CMSDM] Key Detection Routine Used : 1
    [CMSDM] MSDM Key Information: Win 10 Enterprise
    [CMSDM] The detected MSDM Key cannot be used for the Edition installed, saved only. 
    MRP didn't insert the Enterprise MSDM key, it must of been done via Windows setup. Either at the username entry or the final stage of the oobe process.

    The only way around that would be to test with a PID.txt with the Key for Professional. Even so Setup may override that too!

    However i have not seen anyone mention that Enterprise MSDM's actually exist yet.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  6. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    49,674
    103,510
    450
    As soon as the current process of creating 16299.64>16299.125 SVFSFX patches (yes there are new 16299 iso's released on MVS), i will put in the pid.txt with the generic pro key :D
     
  7. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    6,317
    21,056
    210
    M$ may of not thought the license switch bit out properly, who knows or even testing it via the insider stages.

    If I am correct that Setup did the switch at some stage then it will cause a lot of back lash for them with someone that installs one edition and ends up with another for example someone with a MSDM for Home and they have a HWID for Pro and install Pro only to find it has been switched back to Home.

    The code in the MRP MSDM stage has always worked before, it was tweaked a long time ago to prevent the license switch with Pro<>Enterprise if anyone can remember?

    Now m$ may of changed things yet again. :(
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  8. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    6,317
    21,056
    210
    Hmm it says it was Switched from Enterprise to Professional :eek: yet it is actually Enterprise. Conflicting what the MRP log says! :g:

    Bustype: SAS thought it say that as from what i have read it is a virtual drive, and it detects it.

    Indicates a serial-attached SCSI (SAS) bus type.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  9. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    6,317
    21,056
    210
    It sure is! Gez what a total <expletive> up!
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  10. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    6,317
    21,056
    210
    Im am really confused.

    Now it says it is Pro, yet the project.log stated:

    [OSINF] Version Installed : Windows 10 Enterprise Insider Preview x64 !!!!!

    Unless m$ has made a total screw up with names ??
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  11. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    6,317
    21,056
    210
    #1934 mxman2k, Dec 19, 2017
    Last edited: Dec 19, 2017
    (OP)
    Yeah , VMware uses the SAS (SCSI) drive system. VBOX i think can be IDE/SATA/SAS even set it as a SSD even if it a HDD.

    Shows the routine is working :p

    Pity the API call used isn't available on less than Win 8.0 :( Can't have everything.

    Like the API for checking if the SLIC is duff/corrupt, why the hell only have that call in W8+ it's no bloody use for the new OS's!! M$ Logic is a bit suspect at times. lol
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  12. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    6,317
    21,056
    210
    #1935 mxman2k, Dec 19, 2017
    Last edited: Dec 19, 2017
    (OP)
    Just realized, at some point will have to adjust the MRP code in the CPU section like the way in the Query Tool :g:

    It can wait its only a cosmetic error :p

    *edit* Fixed for next release. :)
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  13. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    49,674
    103,510
    450
    Used pid.txt with generic pro key (3v66t):
    Code:
    Multi-OEM/Retail Project Version : 171219-R78.1.BF - BaseLine  [MRP/MDL]
     
    Required project files extracted successfully.
     
    DeCompile has detected a 'VMware' Virtual Machine.
     
    OEM's folder detected, structure appears OK.
     
    Detected Config File          - Checking For User Options...
                                  - Options Pre-Check Completed.
     
    MRP Logging Mode              : Enhanced
    Confirm File Delete           : Enabled
    W10 TitleBar Color            : Enabled  - Title Bars will be colorized to Grey.
    Hi-Lite Colorization          : Enabled  - Hi-Lited Text will be colorized to Grey.
    CustomTheme option            : Enabled  - Using 'RMplc' defined in the MRPConfig file.
    No Lock/Login Screen          : Enabled  - Lock/Login Screen's will NOT be replaced.
    Show 'ThisPC' On Desktop      : Enabled
     
    OS Installation Date/Time     : Wed 12/20/2017 -- 09:43am
     
    [OSINF] ======================= 
    [OSINF] Detected OS Information 
    [OSINF] ======================= 
    [OSINF] Version Installed     : Windows 10 Enterprise Insider Preview x64
    [OSINF] Edition {Registry}    : Professional
    [OSINF] Edition {WMIC}        : Professional
    [OSINF] Build Information     : 17063.1000.amd64fre.rs_prerelease.171213-1610
    [OSINF] Update Build Revision : 1000
    [OSINF] Edition Language/Code : en-US / 1033 {409h}
    [OSINF] Locale                : en-US
    [OSINF] Language Name Value   : ENU
    [OSINF] ======================= 
     
    [MBINF] =======================
    [MBINF] Motherboard Information
    [MBINF] =======================
    [MBINF] #01 CS Product Name   : [VMware Virtual Platform]
    [MBINF] #02 CS Model Name     : [VMware Virtual Platform]
    [MBINF] #04 CS Vendor Name    : [VMware, Inc.]
    [MBINF] #05 CS System Name    : [VMware, Inc.]
    [MBINF] #06 Baseboard Name    : [Intel Corporation]
    [MBINF] #08 BIOS or SLIC ID   : [DELL]
    [MBINF] #09 SLIC Information  : [2.2]
    [MBINF] #11 MSDM Brand Name   : [Dell]
    [MBINF] =======================
     
    [CMINF] =======================
    [CMINF] CPU/Memory  Information
    [CMINF] =======================
    [CMINF] CPU Name/Type         : [Intel{R} Core{TM} i7-3770 CPU @ 3.40GHz]
    [CMINF] CPU Description       : [Intel64 Family 6 Model 58 Stepping 9]
    [CMINF] CPU Architecture      : [32/64 Bit Instruction Set]
    [CMINF] CPU Cores/Threads     : [2] / [2]
    [CMINF] Total Physical Memory : [4095 Mb]
    [CMINF] Available Memory      : [3676 Mb]
    [CMINF] =======================
     
    [HDTYP] Info: HDD Detected.
     
    [SATOU] -> Show User options enabled/applied.
    [FEXTS] Show File Extensions option enabled.
    [REMSC] Remove '-Shortcut' reference from icons option enabled.
    [AMSRT] Disable 'Malicious Software Removal Tool' tweak applied.
    [GO2TP] Launch To 'ThisPC' instead of 'Quick Access' view option enabled.
    [APPDT] Apps use 'Dark Theme' option enabled.
    [REMPB] Remove 'People Band' option enabled.
    [REM1D] Prevent One Drive from installing tweak enabled.
    [REM6F] Remove 'Library Folders' from 'ThisPC' view tweak applied.
    [REM3D] Remove '3D Objects Folder' from 'ThisPC' view tweak applied.
    [MTTBT] Extra TaskBar Transparency option enabled.
    [AWLBM] Use 'F8' Legacy Boot Menu tweak applied.
    [NOAMT] Disable 'Automatic Computer Maintenance Tasks' tweak applied.
    [USERL] System Drive user rename option enabled, 'Local Disk' changed to 'Test_17063'.
    [PKEIC] -> PID.txt/ei.cfg Detection.
    [PKEIC] The PID.txt file "D:\Sources\PID.txt" was detected.
    [PKEIC] The ei.cfg file was not detected.
    [CKDMI] Querying BIOS for any manufacturer brand information.
    [VMWSD] Default DMI 'VMware' with a Dell [#08] SLIC detected.
    [THMOK] Dell [#08] manufacturer detected. Defined CustomTheme 'RMplc' will override this.
    [UDPNA] User defined 'Computer Model Name' option has been enabled.
    [CHKMN] Computer Model Name: 'MRP 17063' has been applied.
    [BRND1] -> Branding Extra Checks Section.
    [FTHWD] CustomTheme processing.
    [USRFT] User selected CustomTheme 'RMplc' will be applied.
    [THMMS] -> OEM Brand Transfer Management Section.
    [WPCHK] Wallpaper.jpg transferred.
    [BGDFC] Desktop backgrounds folder created.
    [BGDFC] BackgroundDefault.jpg created from Wallpaper.jpg.
    [W8XAP] -> Windows 10: User Account Picture Management {1}.
    [RMXML] OOBE.xml file processed.
    [UBREP] User.bmp replaced.
    [UPREP] User.png replaced.
    [UPREP] User-40.png replaced.
    [WXAP2] -> Windows 10: User Account Picture Management {2}.
    [UPREP] User-32.png replaced.
    [UPREP] User-48.png replaced.
    [UPREP] User-192.png replaced.
    [NLLSA] Note: Using Windows default Lock/Log-In Screens as the ChangeLockLoginScreens 'No' option was enabled. 
    [OTFTS] -> OEM Theme Files Transfer Section.
    [OTFTS] OEM theme folder has been created.
    [OTFTS] OEM files have been transferred.
    [USCTA] User specified 'RMplc' theme has been applied. 
    [BSHCS] Branding script has completed.
     
    [ADMAN] Add-On Manager: Started.
    [SATOU] -> Show User options applied.
    [FEXTS] Show File Extensions tweak applied.
    [REMSC] Remove '-Shortcut' on icons tweak applied.
    [REMPB] Remove 'People Band' tweak applied.
    [GO2TP] LaunchTo 'ThisPC' instead of 'Quick Access' tweak applied.
    [APPDT] Apps use 'Dark Theme' tweak applied.
    [REM1D] Prevent One Drive from installing tweak applied.
    [MTTBT] Extra TaskBar Transparency tweak applied.
    [CMSDM] Querying BIOS for MSDM data.
    [CMSDM] PID.txt file is present, any MSDM Key {if present}, will be saved only. 
    [CMSDM] Processing MSDM Key...
    [CMSDM] -> Show WMIC/MSDM Edition/Channel Information.
    [CMSDM] -> {WMIC} OS Edition     : 'Professional'
    [CMSDM] -> {MSDM} KeyEditionID   : 'Enterprise'
    [CMSDM] -> {MSDM} ChannelID      : 'MSDM'
    [CMSDM] Key Detection Routine Used : 1
    [CMSDM] MSDM Key Information: Win 10 Enterprise
    [CMSDM] The MSDM key details have been saved in C:\MSDM-Key.txt.
    [USRAC] Windows 10: Enhanced Log-On screen has been enabled.
    [WXSTB] Windows 10: 'Grey' Title Bar Colorization applied.
    [WXSHL] Windows 10: 'Grey' Hi-Lite Text Color applied.
    [USRAC] 'User Account Picture' registry entry applied.
    [USRRO] Windows 'Registered Owner' {Winver} registry entry corrected.
    [USRD0] Detected 'defaultuser0', removal process started.
    [RDUPM] Removal of 'defaultuser0' account completed.
    [AMBPS] -> Checking BIOS/Boot mode and OS HDD/SDD partition type.
    [AMBPS] BIOS/Boot Mode : Legacy 
    [AMBPS] Partition Type : MBR
    [AMHDC] SSD/HDD Mode   : AHCI
    [CHKLS] -> Check if Windows is activated/licensed.
    [CHKLS] License Status: Notification
    [OSLRC] License Status Reason Code: 0xC004F034
    [OSLRT] License not found/invalid or could not connect to the Activation Server.
    [CHKLS] Online connection maybe required to complete activation.
    [ADMAN] Add-On Manager: Completed.
    [CLNUP] MRP Clean Up Routine Processed.
     
    =========================================================================================
    = Please Note: It is advisable to log out or reboot your computer when possible to      =
    =              allow Windows 10 to finalize any settings/User Pictures etc.             =
    =                                                                                       =
    =              If you have used any tweak options within the configuration file then    =
    =              it is required to do a log out or reboot cycle to allow these options    =
    =              to take effect.                                                          =
    =========================================================================================
     
    The Multi-OEM/Retail Project has completed.
    
    
     
  14. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    6,317
    21,056
    210
    Hmm still shows:
    [OSINF] Version Installed : Windows 10 Enterprise Insider Preview x64

    Yet it still is Pro, what was selected during the Edition choice in Setup, and no indication of a 'switch'. :g:
    [OSINF] Edition {Registry} : Professional
    [OSINF] Edition {WMIC} : Professional

    It seems like whatever Microsoft has done regarding the fixed License switch coding, it does some other strange things. Obviously if we was not using the MRP we would not see what is happening during the setup process as we would select Pro/Home etc and think nothing more of it.

    Likewise with the query tool, this also shows that at some point a License switch was done in the background.

    Talk about muddying the water, in this case m$ has made a mud bath!

    Either way MRP still seems to work which is good, just that the information in the log can be a bit confusing.

    As long as a user installs say Pro and to all intensive purposes gets Pro installed that is all that matters. Hopefully by the time RS4 comes out m$ has sorted this mess out. Time will tell!

    I am wondering if they set to Enterprise on purpose regardless then License switch to the user's Edition choice during setup/oobe stage so that the switch is done correctly?

    Or as i previously mentioned the setup stage is picking up on the MSDM key/Edition. :thinking:
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  15. b01m

    b01m MDL Novice

    Nov 14, 2017
    27
    25
    0
    Test QTv39.0

    Code:
    MRP - OEM Query Tool v39.0 Enhanced  --  20/12/2017 -- 8:37pm
     
    -------------------------------------------
    - Basic OEM Information For This Computer -
    -------------------------------------------
     OS Name                   - Windows 10 Pro x64 
     OS Edition {Registry}     - Professional
     OS Edition {Switched}     - Enterprise
     OS Build Number           - 16299
     OS Update Build Revision  - 125
     OS Language Name/Code     - en-US / Dec:1033 {Hex:409}
     OS Locale                 - en-ID
     OS Installation Date      - 15/12/2017 10:00:10
     CPU Name                  - Intel{R} Core{TM} i3 CPU       M 350  @ 2.27GHz   
     CPU Description           - Intel64 Family 6 Model 37 Stepping 5
     CPU Architecture          - 32/64 Bit Instruction Set
     CPU Cores/Threads         - [2] / [4]
     HDD {Boot} Information    - [BusType:AT, Partition:MBR, Model:5AS             ]
     Bios Version              - [_ASUS_, Undefined Date]
     Total Physical Memory     - [3885 Mb]
     Available Memory          - [907 Mb]
     GPU Primary Adaptor Name  - [Intel{R} HD Graphics]
     
    --------------------
    - Scanned DMI/BIOS -
    --------------------
     #01 CSProduct Name        - K42F                            #09 SLIC Information - 2.1                                     
     #02 CSModel Name          - K42F                            #10 Product Key      - Not Shown On Saved Report     
     #03 CSBaseboard Prod      - K42F                            #11 MSDM Key         - No MSDM Table Detected         
     #04 CSProduct Vendor      - ASUSTeK Computer Inc.           #11 MSDM Edition     - Undefined                               
     #05 CSManufacturer        - ASUSTeK Computer Inc.           #11 MSDM Brand Name  - Undefined                     
     #06 Baseboard MFR         - ASUSTeK Computer Inc.           #12 BIOS/Boot Mode   - Legacy/MBR                     
     #07 Serial/Service Tag    - Not Shown On Saved Report       #13 Certificate      - Not Present                   
     #08 BIOS or SLIC ID       - _ASUS_                          #14 License Status   - Licensed {Volume_MAK}                   
     
    -----------
    - Summary -
    -----------
     OEM Theme/Branding        - Asus [id: #04]   
     OEM Activation Vista/7    - Asus [id: #08]
     Valid OEM Consumer OS     - Vista/Win7 Only
     .Net Versions Detected    - v1.1.4322 v2.0.50727 v3.5 v4.0.30319 v4.7.02556
     Powershell Version{s}     - 1.0, 2.0, 3.0, 4.0, 5.0, 5.1
     License Status Reason     - 0x4004F401: This computer has a valid Digital/Store License.
     Other Notes:              - Possible Edition switch detected.
     
     ** End of Query Tool report. **
    
     
  16. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    6,317
    21,056
    210
    Just noticed a small mistake on the bustype AT should of been ATA :oops:

    ATA/IDE maybe the correct wording. Will sort that for next release.

    I would of thought that computer would have a SATA interface :g:, maybe the way it set up as in non AHCI mode that the API returns ATA for IDE mode.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  17. s1ave77

    s1ave77 Has left at his own request

    Aug 15, 2012
    16,093
    24,397
    340
    Licensing gone weird :cool2:. Installed 17063 Pro from UUP AiO download and checked registry ... :thinking:

    17063.Reg.Info.jpg

    Looks like a license switch but definitely isn't.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...