Multi-OEM/Retail Project {MRP} - Mk3

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

  1. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    49,656
    103,438
    450
    You finally dug in that cabinet? ;):D
     
  2. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    6,314
    21,042
    210
    I was pressing the front panel button and nothing happening i was like ffs what next, ive only fitted the SSD. Then i looked at back of pc and the switch was off!

    As we say here "More haste, less speed." about right im my case :p
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    6,314
    21,042
    210
    Yep its a 128gb SSD but better than that growling HDD which is only a 5,300 RPM more like 5.3 RPM lol.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  4. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    6,314
    21,042
    210
    Code:
    Multi-OEM/Retail Project Version : 171126-R75.0 - RC  [MRP/MDL]
     
    Required project files extracted successfully.
     
    OEM's folder detected, structure appears OK.
     
    No Config File Detected - Using Default Option Settings.
     
    MRP Logging Mode        : Standard
    Confirm File Delete     : Disabled
    W10 TitleBar Color      : Disabled
    'ThisPC' On Desktop     : Disabled
     
    OS Installation Date/Time: 26/11/2017 -- 7:23pm
     
    [OSINF] =======================
    [OSINF] Detected OS Information
    [OSINF] =======================
    [OSINF] Version Installed     : Windows Server 2016 Standard x64
    [OSINF] Edition {Registry}    : ServerStandard
    [OSINF] Edition {WMIC}        : ServerStandard
    [OSINF] Build Information     : 14393.0.amd64fre.rs1_release.160715-1616
    [OSINF] Update Build Revision : 0 {Baseline Release}
    [OSINF] Edition Language/Code : en-US / 1033 {409h}
    [OSINF] Locale                : en-GB
    [OSINF] Language Name Value   : ENG
    [OSINF] =======================
     
    [MBINF] =======================
    [MBINF] Motherboard Information
    [MBINF] =======================
    [MBINF] #01 CS Product Name   : [H81M-HDS]
    [MBINF] #02 CS Model Name     : [H81M-HDS]
    [MBINF] #04 CS Vendor Name    : [ASUSTeK Computer INC.]
    [MBINF] #05 CS System Name    : [ASUSTeK Computer INC.]
    [MBINF] #06 Baseboard Name    : [ASUSTeK Computer INC.]
    [MBINF] #08 BIOS or SLIC ID   : [_ASUS_]
    [MBINF] =======================
     
    [CMINF] =======================
    [CMINF] CPU/Memory  Information
    [CMINF] =======================
    [CMINF] CPU Name/Type         : [Intel{R} Celeron{R} CPU G1820 @ 2.70GHz]
    [CMINF] CPU Description       : [Intel64 Family 6 Model 60 Stepping 3]
    [CMINF] CPU Architecture      : [32/64 Bit Instruction Set]
    [CMINF] CPU Cores/Threads     : [2] / [2]
    [CMINF] Total Physical Memory : [3896 Mb]
    [CMINF] Available Memory      : [3468 Mb]
    [CMINF] =======================
     
    [HDTYP] Info: SSD Detected.
     
    [SVROS] Server OS detected, branding/SLIC activation may fail, see Server-Readme.txt file for details.
    [SVROS] Detected Server Kernel Version: [10.0]
    [PKEIC] The PID.txt file was not detected.
    [PKEIC] The ei.cfg file "D:\Sources\EI.cfg" was detected.
    [CKDMI] Querying BIOS for any manufacturer brand information.
    [SPS8X] Asus [#08] SLIC manufacturer found for possible Server Server 2016 OEM activation.
    [THMOK] Asus [#04] manufacturer detected for automated theme/branding.
    [NOSLP] Note: No valid OEM-SLP Product Key available in the database for this Edition.
    [CHKMN] Computer Model Name: 'H81M-HDS' has been applied.
    [USRFT] CustomTheme option was not used.
    [WPCHK] Wallpaper.jpg transferred.
    [BGDFC] Desktop backgrounds folder created.
    [BGDFC] BackgroundDefault.jpg created from Wallpaper.jpg.
    [SVOEM] Attempting to brand Server OS.
    [RMXML] OOBE.xml file processed.
    [UBREP] User.bmp replaced.
    [UPREP] User.png replaced.
    [UPREP] User-40.png replaced.
    [UPREP] User-32.png replaced.
    [UPREP] User-48.png replaced.
    [UPREP] User-192.png replaced.
    [WXLS5] Lock Screen {img105.jpg} replaced. Original renamed as img0105.jpg.
    [WXLS1] Log-In Background {img100.jpg} replaced. Original renamed as img0100.jpg.
    [OTFTS] OEM theme folder has been created.
    [OTFTS] OEM files have been transferred.
    [ATHBA] Asus theme has been applied.
    [BSHCS] Branding script has completed.
     
    [ADMAN] Add-On Manager: Started.
    [SVRAF] Server 2016: Adding required Features...
    [SVRAF] Server 2016: Features Add-On module completed.
    [SVRAF] Note: Server reboot is required to finalize Features after the Desktop appears.
    [CMSDM] Server detected, MSDM Key will not be processed.
    [USRAC] Windows 10: Enhanced Log-On screen has been enabled.
    [USRAC] 'User Account Picture' registry entry applied.
    [USRRO] Windows 'Registered Owner' {Winver} registry entry corrected.
    [USRD0] The 'defaultuser0' account was not present.
    [AMBPS] BIOS/Boot Mode : Legacy
    [AMBPS] Partition Type : MBR
    [AMHDC] SSD/HDD Mode   : AHCI
    [CHKLS] License Status: Notification
    [OSLRC] License Status Reason Code: 0xC004F034
    [OSLRT] Connection to Activation Server has not been successful at this time, try again later.
    [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.
    
    
    All theme is present, just lock/loginscreens are default Windows ones but that the limitation i guess with Server installs.

    No errors (apart from user error working my way around that Server Manager lol)
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. tcntad

    tcntad MDL Guru

    Oct 26, 2009
    4,585
    1,584
    150
    Id also be happy to try it in wmvare soon:)
     
  6. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    6,314
    21,042
    210
    Not sure why it picked Lenovo on your install @tcntad. My Asus install shows the Republic of Gamers desktop background, not that a Server is designed to be a gaming OS as such lol.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  7. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    6,314
    21,042
    210
    I wasn't going to release MRP 75 just yet but as there was a 'minor' bug that had to be fixed i guess it is ready to go from RC to baseline.

    MRP 75 has all the new Reason Codes added along with a few code tweaks, and now this Server 2016 glitch fixed. :D

    Be about 15-30 mins to recompile it all and do the changelog etc.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  8. tcntad

    tcntad MDL Guru

    Oct 26, 2009
    4,585
    1,584
    150
    Beacuse it was in vmware with alternate branding:)
    My server however is an Asusboard and it was branded just fine.
     
  9. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    6,314
    21,042
    210
    You had me worried there that something else had changed in the Server 2016 full release. :p
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  10. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    6,314
    21,042
    210
    MRP 75.0 Baseline has been uploaded and first post updated with new password.

    Quick Summary

    + Added new Reason Codes and Text (now at 370+) that should cover almost all activation/Licensing errors!

    + Fixed Server 2016 (full release) Desktop Experience DISM failure message (because it is now integrated by default on those Editions on the Setup list).*

    + Few other minor code tweaks.

    *Thanks for @tcntad for bringing this to my attention and to @Enthousiast for testing Server 2016 and MRP 75.0 RC to make sure the error no longer appears.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  11. tcntad

    tcntad MDL Guru

    Oct 26, 2009
    4,585
    1,584
    150
    Will try in this very moment in vmware and maybe tomorrow IRL.
     
  12. bkul

    bkul MDL Member

    Apr 2, 2015
    163
    44
    10
    #1732 bkul, Nov 27, 2017
    Last edited: Nov 27, 2017
    I've succeed to find FULL table of the Reason Status explanations WITHOUT running SLUI. The way was as simple as: 1. search with Total Commander *.MUII files containing one of the messages. 2. Using very simple and reliable tool EXE.EXE, which permits to see DLL, EXE, MUI,.. files RESOURCES, I've found 403 messages which are present in SLC.DLL.MUI as a StringTable resource. These messages are contained also in SPP.DLL.MUI. EXE.EXE permits to copy all strings. Thus I know now that: there are 403 messages and I have these messages values. That is now I need only an algorithm to collate status codes and messages. I hope that MUI contains binary codes. Yess, I've found binary codes table in MUI, it starts at offset x'800' with a code 4004D30F ( bytes are inverted order ). P.S: SLError.h is out-of-date as it contains only 359 codes :) comparing 403 explanation messages and codes in spp.dll.mui of 17046. Will give a link on a full table ready to implement into script-code somewhat later today.
     
  13. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    6,314
    21,042
    210
    I exported the message table, just converting the decimal codes to hex, gez there is a lot lol
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  14. bkul

    bkul MDL Member

    Apr 2, 2015
    163
    44
    10
    Sure, very strange looks explanations like "Owner, write description pls" :)
    But when I've read this list of the messages, I"ve recognized that they strictly indicate at least 3 stages of the Activating procedure as there are messages which starts with "Genuine Validation", "The Software Licensing Service", "The activation server" and rather few messages without one of these prefixes. It seems to me that "Genuine Validation" is a 1st stage, "The Software Licensing Service" - 2nd one and "The activation server" - the last one.
     
  15. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    6,314
    21,042
    210
    Yeah considering M$ is the 'owner' they cant even write a description in the error messages!
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  16. bkul

    bkul MDL Member

    Apr 2, 2015
    163
    44
    10
    For sure there are some groups working with the same source-code and that is why member of the one group asks other guys to implement a correct message text.
     
  17. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    6,314
    21,042
    210
    C004C00E=Invalid Product Key Length.
    C004C00F=Invalid Product Key Format.
    C004C010=Invalid Product Key Character.
    C004C011=Invalid Product Key Binding.

    C004D000=Invalid License. {Remapping SP PUB API}.
    C004D009=The transaction manager doesn't support an asynchronous operation for this method.
    C004D00C=Software Licensing - Too Many Loaded Environments.
    C004D012=Software Licensing - Invalid Get-Information Query.
    C004D02C=Software Licensing - Invalid Handle.
    C004D055=Software Licensing - Invalid Key Length.
    C004D073=Software Licensing - No AES Provider.

    Those had the 'owner write description, pls' worked those out from the slui.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  18. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    6,314
    21,042
    210
    There are some really silly error messages such as:

    0x803FABBC The user is not eligible for reactivation because the user is throttled.

    :eek:
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  19. bkul

    bkul MDL Member

    Apr 2, 2015
    163
    44
    10
    And there are some INTERNAL, technical messages which can understand only developper, like:

    $c[0xC004D081] ="The handle was used before calling SPCommit with it";
    $c[0xC004D101] = "The security processor reported an initialization error";
    $c[0xC004D103] = "The security processor reported an error has occured";
    $c[0xC004D104] = "The security processor reported that invalid data was used";
    $c[0xC004D105] = "The security processor reported that the value already exists";
    $c[0xC004D107] = "The security processor reported that an unsufficient buffer was used";
    $c[0xC004D108] = "The security processor reported that invalid data was used";
    $c[0xC004D109] = "The security processor reported that invalid call was made";
    $c[0xC004D10A] = "The security processor reported a version mismatch error";
    $c[0xC004D10C] = "No more data is available";
    So I guess that likewise messages NEVER issued to the USER in PRODUCTION version of the system
     
  20. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    6,314
    21,042
    210
    Some other interesting ones...

    8004E026=A valid product key for an add-on sku was entered where a Windows product key was expected. (ProWS ?)
    803FA400=The offer no longer exists. (maybe for after the 31st Dec 2017 :g:)
    C004C016=OEM SLP COA - Key cannot be used for online activation. (Vista/7)
    C004C4A9=The specified product key has been blocked for this geographic location. (like youtube! :))
    C004D20B=The key does not exist. It may not have been created yet. (????)
    C004F061=This specified product key can only be used for upgrading, not for clean installations. (hmm)
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...