Multi-OEM/Retail Project {MRP} - Mk3

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

  1. schnullibulli

    schnullibulli MDL Novice

    Jan 17, 2014
    16
    7
    0
    Tried so far:
    - DELL SLIC 2.3, 2.4, 2.5
    - modded efi and modded legacy bios
    - WS2016 en and de
    - [Channel] _Default and [Channel] OEM in ei.cfg

    Selection on install is "Windows Server 2016 Standard (Desktop Experience)"

    Will try with VMware WS now to find out, if the problem is related to my os image or the modded bios.
     
  2. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    5,679
    19,123
    180
    If 'oobe.cmd' is not being run then it is outside the scope of this project as it is then a issue with the ISO or setup.exe.

    At present i'am rechecking the code within the QT and MRP to make sure the SLIC detection is in order, so far all seems to be the same routine...

    I am at a loss what to suggest as it not a problem with the project itself in this case.

    The odd thing is on our Server test installs the 'oobe.cmd' is executed by the Windows Setup system. :g:
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    5,679
    19,123
    180
    #5406 mxman2k, Nov 20, 2019
    Last edited: Nov 20, 2019
    (OP)
    Other Notes: : BIOS Version or SLIC ID {#08} may not show correctly with UEFI or Secure Boot enabled.

    Sometimes when using UEFI+Secure Boot the SLIC table is ignored on Windows 8.x/10 (Server 2016/19 is based on Windows 10 Kernel) i am not sure if this is what is causing the setup.exe to ignore any oobe or setupcomplete .cmd files :g:

    On my Lenovo tower if i have UEFI bios in use i can never see the SLIC table it is either hidden or 'corrupted', yet if i install with MBR i can see the slic table, i know some HP's and Acer's recently do this too. If the user has W10 installed the SLIC is not always available to be seen.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  4. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    5,679
    19,123
    180
    AH!!!

    $OEM$ folder must be within the Sources folder, not the root of the ISO/USB as it will NOT be seen by the Setup.exe :)
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. schnullibulli

    schnullibulli MDL Novice

    Jan 17, 2014
    16
    7
    0
    @mxman2k
    To be clear, I *think* oobe.cmd is not executed, because there is no cert, activation or branding.
    How can I check, if oobe.cmd is started but maybe fails to execute for some reason?
     
  6. schnullibulli

    schnullibulli MDL Novice

    Jan 17, 2014
    16
    7
    0
    OMG - shame on me!!!
     
  7. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    5,679
    19,123
    180
    #5410 mxman2k, Nov 20, 2019
    Last edited: Nov 20, 2019
    (OP)
    when the wndows setup is run it copies all the windows files to the Hdd it also copies the $OEM$ folder's contents -- if it is within the Sources folder to C:\Windows\Setup\ (C: could be D: etc depending on how your partition table is setup).

    As the $OEM$ folder is not within the Sources folder Windows setup totally ignores it anywhere else. :)
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  8. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    5,679
    19,123
    180
    #5411 mxman2k, Nov 20, 2019
    Last edited: Nov 20, 2019
    (OP)
    If we get MRP to run i am hoping it will see the SLIC properly and do all the SLP Key + Cert and be activated, but UEFI mode may partially hide the SLIC table...

    At least get oobe.cmd and MRP to run to do at minimum the branding..

    The Certs are stored internally within the Decompile.exe and extract as needed during MRP's execution.

    https://forums.mydigitallife.net/threads/oa-2-x-slic-oemcert-collection.5952/page-53#post-514521 this has the Certs as well as the SLIC.BIN files...
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  9. schnullibulli

    schnullibulli MDL Novice

    Jan 17, 2014
    16
    7
    0
    activation failed, but branding was applied. I will try with legacy bios if that will be auto-activated.
    Code:
    [START] 
    [OSINF] =============================================================
    [OSINF] =================[ Detected OS Information ]=================
    [OSINF] =============================================================
    [OSINF] OS Install Date/Time  : 11/20/2019 {UTC} -- 10:50am
    [OSINF] Installation Type     : Server
    [OSINF] HyperVisor Detected   : Yes
    [OSINF] Domain Detected       : No
    [OSINF] Version {SKU}         : Server Standard {7}
    [OSINF] Edition {Registry}    : ServerStandard {7}
    [OSINF] Edition {Composition} : ServerStandard
    [OSINF] Edition {Type}        : General
    [OSINF] Architecture          : 64 Bit {AR:1}
    [OSINF] Release Identifier    : 1607
    [OSINF] Build Information     : 14393.1794.amd64fre.rs1_release.171008-1615
    [OSINF] Reference Version     : 10.0.14393.0
    [OSINF] ProductID Reference   : 3774
    [OSINF] Update Build Revision : 1884
    [OSINF] Edition UILang/Code   : de-DE / 1031 {0x407h}
    [OSINF] Locale                : German – Germany
    [OSINF] Time Zone Data        : W. Europe Standard Time {Bias: +01:00}
    [OSINF] Daylight Saving Mode  : No
    [MBINF] =============================================================
    [MBINF] =================[ Motherboard Information ]=================
    [MBINF] =============================================================
    [MBINF] #01 CS Product Name   : [VMware71] 
    [MBINF] #02 CS Model Name     : [VMware71] 
    [MBINF] #03 Baseboard Product : [440BX Desktop Reference 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 1 : [DELL   - 6040000] 
    [MBINF] #09 SLIC Information  : [No Valid SLIC Table Present] 
    [MBINF] #11 MSDM Information  : [No MSDM Table Present] 
    [MBINF] Chassis Type {01}     : [Other] 
    [MBINF] PC System Type        : [Desktop {0x1}] 
    [BDINF] =============================================================
    [BDINF] ==================[ Main BIOS Information ]==================
    [BDINF] =============================================================
    [BDINF] Manufacturer          : [VMware, Inc.] 
    [BDINF] Version               : [VMW71.00V.14410784.B64.1908150010] 
    [BDINF] Release Date          : [08/15/2019] 
    [...]
    [REPDR] ======================================================
    [REPDR] ===[ Retail.txt/Ei.cfg/PID.txt Detection Routines ]===
    [REPDR] ======================================================
    [REPDR] Note: Some results may return as 'not detected' if the install medium was removed during OS installation.
    [REPDR] The 'Retail.txt' file was not detected within the 'Scripts' folder.
    [REPDR] The 'ei.cfg' file was detected within the 'D:\sources' folder. 
    [REPDR] The 'PID.txt' file was not detected. 
    [CKDMI] =============================================================
    [CKDMI] ===[ Querying DMI For OEM Manufacturer Brand Information ]===
    [CKDMI] =============================================================
    [SVROS] Server OS detected, Branding/SLIC activation may fail, see 'Server-Readme.txt' file for details.
    [CKDCF] No DMI conflicts found.
    [CKDCF] DMI query routine completed.
    [NOSLC] No valid SLIC was found for Server OEM activation.
    [THMOK] VMWare  manufacturer was detected for automated theme/branding.
    [XRMAM] OEM SLP Key, Certificate and Activation Routine's will not be processed. Reason: No valid SLIC Table Detected. [NS]
    [...]
    [AMBPS] =================================================================
    [AMBPS] ===[ Check BIOS/Boot Mode, OS Partition Type/Controller Mode ]===
    [AMBPS] =================================================================
    [AMBPS] BIOS/Boot Mode  : {W} UEFI
    [AMBPS] Partition Type  : {W} GPT
    [AMBPS] Secure Boot     : {Q} Disabled
    [AMHDC] Controller Mode : {S} SAS/SCSI
    [CHKLS] =============================================
    [CHKLS] ===[ Detecting License\Activation Status ]===
    [CHKLS] =============================================
    [CHKLS] License/Activation Status  : Notification
    [CHKLS] License Channel Status     : OEM:SLP {PKC}
    [CHKLS] License Status Reason Code : 0xC004F063
    [CHKLS] The system is missing a required OEM licence component, {ACPI Table/Key/Certificate etc}.
    
    Seems, that SLIC is not detected by oobe.cmd.
    But if I run qt afterwards, it outputs valid SLIC info...
     
  10. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    5,679
    19,123
    180
    at least we getting somewhere now :)

    There *might* be a small glitch (again grr) in the SLIC detection side within MRP as i just noticed a part where when using NEQ GTR LSS statements they not like quotes around the variables and can give a false/weird result. The QT code does not have the quotes around those variables.

    But on manual testing it not matter if they are there or not - however under OOBE stage things act very different to normal mode.

    But the main thing is the MRP now ran and you got branding...

    Servers are awkward buggers and so the 'glitch' may not be of my doing and its m$ being its usual illogical self.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  11. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    5,679
    19,123
    180
    Just recompiled MRP TC9 with the removed quote parts on the SLIC checking -- fingers crossed 2.5 slic is detected properly on our internal tests....
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  12. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    5,679
    19,123
    180
    Failed again to detect slic 2.5

    Hmm looks like something is going very weird and MRP does not 'see' the valid SLIC...

    This may take a bit of creative thinking to sort it out :D:D
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  13. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    5,679
    19,123
    180
    Taking a break as going code blind :D:D so will resume tomorrow. :)

    Its 9pm GMT here and been a very long day.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  14. schnullibulli

    schnullibulli MDL Novice

    Jan 17, 2014
    16
    7
    0
    Thanks for your support!
     
  15. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    5,679
    19,123
    180
    At least we got one problem sorted - oobe now runs :)

    Now i got the task of working out where i made an error for the SLIC part on Servers... I will suss it one way or another :D:D
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  16. Dubioza Kolektiv

    Dubioza Kolektiv MDL Addicted

    Dec 27, 2012
    867
    1,463
    30
    @mxman2k

    Capture.JPG

    Can you make an option for Win 7 and Win 10 check or unchechk.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  17. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    5,679
    19,123
    180
    It is the same registry item as the Win8.x/10 one but it acts slightly different in the respective OS, also once it been set, the tick box is possibly greyed out in that dialog under Win 7 as it is a group policy edit.

    I will have a script that will revert to the OS default in the MiscScripts\General folder to 'unset' that policy if the end user requires later. :)

    ================
    MRP 118's release will be a bit delayed at the moment due to this SLIC problem with Servers, but it does give me a bit extra time to tidy up bits and pieces in the code.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...