Multi OEM/Retail Project

Discussion in 'MDL Projects and Applications' started by The_Guardian, Nov 8, 2014.

Thread Status:
Not open for further replies.
  1. apologized

    apologized MDL Addicted

    Nov 29, 2012
    874
    506
    30
    #2441 apologized, Oct 13, 2016
    Last edited by a moderator: Apr 20, 2017
    sorry for delay i'm far from home now (in evening i will post it)
    but i tested on another HP this is the results :

    Code:
    OEM Query Tool v10 Build 8 Standard     18:44  13/10/2016  
     
    OEM INFORMATION FOR THIS MACHINE 
    -------------------------------- 
     OS Name:     Windows 8.1  [x64] 
     OS Version:  6.3.9600.17415.amd64fre.winblue_r4.141028-1500 
     Processor:   Intel(R) Pentium(R) CPU  N3530  @ 2.16GHz 
     Processor Cores:          [4]           Logical Processors:  [4] 
     Processor Architecture:   [AMD64] 
     HDD Partition Type:       [MBR] 
     Bios Version:             [F.34, 12/19/2014] 
     
    SCANNED 
    ------- 
     #1 CSPRODUCT NAME       - HP Pavilion 17 Notebook PC  
     #2 COMPUTERSYSTEM MODEL - HP Pavilion 17 Notebook PC  
     #3 BASEBOARD PRODUCT    - 227C 
     #4 CSPRODUCT VENDOR     - Hewlett-Packard 
     #5 COMPUTERSYSTEM MFR   - Hewlett-Packard 
     #6 BASEBOARD MFR        - Hewlett-Packard 
     #7 SERIAL/SERV TAG      - 5CD433704F 
     #8 BIOS ID              - HPQOEM 
     #9 SLIC OA              - Un-Listed   
    #10 INSTALLED KEY        - ***** 
    #11 MSDM TABLE [OEM:DM]  - **** 
    #12 BIOS MODE            - LEGACY 
    #13 CERTIFICATE          - Un-Listed 
    #13 LICENSE STATUS       - Licensed  
     
    SUMMARY 
    ------- 
     THEME                   - HP [id:-`#1'] 
     ACTIVATION              - HP [id:-`#8'] 
     VALID [OEM OS]          - Win8.x/Win10 Only 
     
     
     
    SLIC TABLE 
    ---------- 
    Un-Listed 
    
    
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  2. The_Guardian

    The_Guardian Contributor

    May 7, 2012
    2,054
    6,794
    90
    I expected it to work on HP's like above but the other one had info in first two queries that is not included thus caused failure when conflict resolution kicked in. Good it worked on the one above but was more curious about the other machine. Think it is resolved now because i manually inputted info into query tool and it assigned the Hewlett-Packard instead of MSI. Thanks for testing though. :)
     
  3. apologized

    apologized MDL Addicted

    Nov 29, 2012
    874
    506
    30
    #2443 apologized, Oct 13, 2016
    Last edited by a moderator: Apr 20, 2017
    with last query tool same result o_O :

    Code:
    OEM Query Tool v10 Build 8 Standard     23:31  13/10/2016  
     
    OEM INFORMATION FOR THIS MACHINE 
    -------------------------------- 
     OS Name:     Windows 10 Pro  [x64] 
     OS Version:  6.3.14393.321.amd64fre.rs1_release_inmarket.161004-2338 
     Processor:   Intel(R) Core(TM) i5 CPU         650  @ 3.20GHz 
     Processor Cores:          [2]           Logical Processors:  [4] 
     Processor Architecture:   [AMD64] 
     HDD Partition Type:       [MBR] 
     Bios Version:             [6.18, 01/05/2012] 
     
    SCANNED 
    ------- 
     #1 CSPRODUCT NAME       - HPE-410fr 
     #2 COMPUTERSYSTEM MODEL - HPE-410fr 
     #3 BASEBOARD PRODUCT    - 2A9C 
     #4 CSPRODUCT VENDOR     - Hewlett-Packard 
     #5 COMPUTERSYSTEM MFR   - Hewlett-Packard 
     #6 BASEBOARD MFR        - MSI 
     #7 SERIAL/SERV TAG      - CZC042D4C0 
     #8 BIOS ID              - HPQOEM 
     #9 SLIC OA              - 2.1   
     
    SUMMARY 
    ------- 
     THEME                   - MSI [id:-`#6'] 
     ACTIVATION              - MSI [id:-`#8'] 
     VALID [OEM OS]          - Vista/Win7 Only 
     CONFLICT             - HP Resolved As MSI
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  4. The_Guardian

    The_Guardian Contributor

    May 7, 2012
    2,054
    6,794
    90
    #2444 The_Guardian, Oct 14, 2016
    Last edited: Oct 14, 2016
    (OP)
    The only way to resolve this in your case would be for me to remove custom builds from the project because that line of code is breaking it for this machine. I will explain further, even if you use the force theme text file it will still be assigned to MSI for MAN2 which is for activation. You can use the force theme to set MAN but will still try to activate using MSI. It should not but for some odd reason it is. Without having that machine myself, I cant fix it.

    What really kills me is why is #1-#5 not assigning as HP (Hewlett-Parkard)?
    It should see this #1 & #2 HP
    E-410fr then set as HP but it isnt. Then it fails on #4 and #5 which it should not either.

    This is what I have been trying to tell everyone, their will NEVER be a perfect conflict resolution for this project because OEM's are changing every year. If I fix for one, it breaks another. Never-ending story. o_O

    What I can do is add a check for force theme.txt file before the conflict resolution for BIOS ID then if it is present set MAN to it and set MAN2 to it also. Its a workaround not really a fix.

    Does everyone now see why I would like to get away from doing the project? Time consuming as hell plus there will always be issues with some oem at some point and time. I am burned out on this to tell the truth.
     
  5. The_Guardian

    The_Guardian Contributor

    May 7, 2012
    2,054
    6,794
    90
    #2445 The_Guardian, Oct 14, 2016
    Last edited: Oct 14, 2016
    (OP)
    Ahhh I see said the blind man. This is a modded motherboard isnt it? The reason I say this is because there is no cert but has bios id of HP. If bios id is HP it should have cert included in bios as well. Think this is the whole problem. If not modded then HP f*cked up on the slic/cert info.

    I just looked at the spec on this desktop model and it came with Windows 7 Home Premium 64-Bit so it should have slic 2.1 in bios with CERT but is has no CERT included. This is the problem.

    Was there a bios update done?

    This is also missing from query tool info...

    #12 BIOS MODE -
    #13 CERTIFICATE -
    #13 LICENSE STATUS -

    It doesnt show the cert plus it never tried to extract it thus no output in query tool. This is what is breaking the query tool and project. Looks like a bios issue.

    Tell the customer to get a refund. lol
     
  6. BALTAGY

    BALTAGY MDL Guide Dog

    Dec 23, 2014
    327
    518
    10

    I think you mixed between both Pc's

    The one that don't have a problem don't have slic

    The one that have problem have slic 2.1 but i think he just deleted it while posting, it's in the pic he posted before

    #12 BIOS MODE - LEGACY
    #13 CERTIFICATE - Un-Listed
    #13 LICENSE STATUS - Licensed

    Those too in the pic he posted before, he just didn't copy them above
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  7. The_Guardian

    The_Guardian Contributor

    May 7, 2012
    2,054
    6,794
    90
    I edited it but it still didnt show up in the query tool results. It should is my point...not the info in it because it failed. My point is that it should have the cert in the bios with the slic and it doesnt. There is a problem with the bios.

    Then if that is the case then I cant do troubleshooting without all the needed info.

    I still say it should have cert present according to HP support site. Its required for win7 activation and if it isnt in the bios then that is the problem.
     
  8. The_Guardian

    The_Guardian Contributor

    May 7, 2012
    2,054
    6,794
    90
    Either way, I will move the check for force theme before the bios id checks so if present it will assign correct MAN (branding) and MAN2 (activation). At least he will then have a workaround that works. :tea:

    If he has no cert then he will still not be able to activate with win7. Not that he is using win7 but still this is a problem if he wanted to go back to win7 instead of win10. Just saying...
     
  9. The_Guardian

    The_Guardian Contributor

    May 7, 2012
    2,054
    6,794
    90
    I am done with this project. Anyone who wants to try and continue it, go for it. I am retired.