Page 36 of 40 FirstFirst ... 2633343536373839 ... LastLast
Results 351 to 360 of 400

Thread: Multi-OEM/Retail Project - Continued...

  1. #351
    MDL Senior Member mxman2k's Avatar
    Join Date
    21 Jun 2007
    Location
    England
    Posts
    325
    Thanks Information

    Default Query Tool Updated!

    Query Tool v14 Build 8

    Updated the QT as i forgot to output any possible DMI conflict information in build 7.

    Example QT Results file: (Using dummy info)
    Spoiler: 
    Code:
    OEM Query Tool v14 Build 8 Advanced     11:22 AM  11/01/2017 
     
    OEM Information For This Computer 
    --------------------------------- 
     OS Name:                  Windows 10 Pro [x64] 
     OS Edition/SKU:           Professional 
     OS Language:              2057 [809h] 
     Processor:                Intel(R) Core(TM) i5-6400 CPU @ 2.70GHz 
     Processor Cores:          [4] 
     Logical Processors:       [4] 
     Processor Architecture:   [64] 
     HDD Partition Type:       [MBR] 
     Bios Version:             [HPQOEM, 05/23/2016]
     Total Physical Memory:    [16344 Mb] 
     Available Memory     :    [14085 Mb] 
     
    SCANNED 
    ------- 
     #1 CSProduct Name       - HP Envy TS 
     #2 ComputerSystem Model - Dummy Info 
     #3 Baseboard Product    - P5K-VM 
     #4 CSProduct Vendor     - System manufacturer 
     #5 ComputerSystem MFR   - System manufacturer 
     #6 Baseboard MFR        - ASUSTeK Computer INC. 
     #7 Serial/Service Tag   - Not Shown On Saved Report. 
     #8 BIOS ID              - HPQOEM 
     #9 SLIC OA              - v2.4   
    #10 Installed PID Key    - Key Not Shown On Saved Report. 
    #11 MSDM Table [OEM-DM]  - Un-Listed 
    #12 BIOS Mode            - Legacy 
    #13 Certificate          - Un-Listed 
    #14 License Status       - Licensed 
     
    SUMMARY 
    ------- 
     OEM Theme/Branding      - HP [id:-`#1'] 
     Activation [Vista/7]    - HP [id:-`#8'] 
     Valid OEM [OS]          - Vista/Win7/Server 2016 
     Possible DMI Conflict   - [HP Envy TS] Resolved As [HP]   <<Now displays this line if any conflicts.
     
     
    SLIC Table 
    ---------- 
    Un-Listed 
     
    MSDM Table 
    ---------- 
    Un-Listed 
     
    Certificate 
    ----------- 
    Un-Listed
    Download link updated.
    Remember tiny pixels make up the whole picture!

  2. #352
    MDL Novice
    Join Date
    30 Dec 2009
    Posts
    26
    Thanks Information

    Default

    Quote Originally Posted by mxman2k View Post
    You can use a vm yes, it will detect if it is a Vbox or Vmware if you not alter any DMI settings within the VM's files. But you will see what happens before using on a real pc.

    Most of my testing was done using a VM (VBox), and altering the DMI information and adding a SLIC file to fool the VM into thinking it was a 'real' PC.

    Extract the $oem$ folder from the MRP 7z file, place within Sources folder on the ISO or USB stick, save ISO. boot up from the ISO/USB stick and do a normal setup. Once setup is complete, if all went well you will see the branding in place. On a VM obviously it wont activate unless as mentioned above some edits done to the VM prior to installing the OS. The branding will be for the VM used Vmware or Vbox.

    Then once desktop has appeared , open My Computer and the C drive and you should see a project.log open this in notepad and you will see the progress report. You may get a few errors due to no SLIC etc, but it will give you an indication of what will happen on a real pc.

    On your Lenovo PC it will brand with Lenovo logo's etc just like the OEM would of, (without all the bloatware!). Also if the SLIC is available in bios which most likely it is then you will be activated also on that PC. With Vista you may need to do a restart after the desktop appears to complete the activation process.

    Hope this helps

    Re Spoilers on first post, yes even i sometimes get confused when editing the page. Have to check and re-check i got the info i have added in the right place!
    the $OEM$
    I tested this yesterday with Vista in VM (VMware) after adding the $OEM$ folder to the ISO sources folder.
    The VM Vista completed and ran fine but there was no project.log file in the root of the VM C: drive.
    Does this indicate that the project failed in VM. Is there another check I can make to see that $OEM$ did do something?

    BTW: I was loading the ISO from the Win7 partn I loaded VMware .. not USB or DVD.

  3. #353
    MDL Senior Member mxman2k's Avatar
    Join Date
    21 Jun 2007
    Location
    England
    Posts
    325
    Thanks Information

    Default

    Did any theme/branding for the VM happen?

    As it is VMware you used to test, if the project ran then you would have VMware's background etc. If the VMware branding and logo's was present then MRP had ran.

    Within $OEM$ there should be a folder called $$ then within that folder another folder called Setup then lastly within that a folder called Scripts, within the Scripts folder should be DeCompile.exe, OOBE.cmd and if you are using branding, the OEM's.7z file.

    \Sources\$OEM$\$$\Setup\Scripts

    Even if the project failed, providing the DeCompile.exe and OOBE.cmd was present within the Scripts folder then it would of at minimum produced a log output of just even the Version number.

    Just running a test on Vista via a VM... All went ok.
    Spoiler: 
    Code:
    Multi-OEM/Retail Project Version : 170108-R50s-BaseLine  [MRP/MDL] 
     
    Files present and extracted successfully. 
     
    OEM's folder detected, structure appears OK. 
     
    OS Installation Date: 11/01/2017 
     
    21:25:25.04 Windows Vista (TM) Home Premium x86 version found. 
    21:25:26.04 HomePremium Edition/SKU installed. 
    21:25:26.04 Build Version: 6002.18881.x86fre.vistasp2_gdr.130707-1535 
     
    DMI BIOS Information 
    #1 CS Product Name   : [VirtualBox] 
    #2 CS Model          : [VirtualBox] 
    #4 CS Vendor         : [innotek GmbH] 
    #5 CS System Manf    : [innotek GmbH] 
    #6 Baseboard Manf    : [Oracle Corporation] 
    #8 BIOS ID           : [VBOX] 
     
    21:25:30.28 'LblDrv' flag not set, 'C:' will be left as OS default. 
    21:25:30.89 Defined VBOX [VirtualBox] manufacture found. 
    21:25:30.89 OEM activation not possible due to no defined MAN2. 
    21:25:30.89 VBOX [VirtualBox] manufacture will be used for theme/branding. 
    21:25:30.89 Force theme text file not present. 
    21:25:31.41 System Product Name, not detected. 
    21:25:31.41 Desktop backgrounds folder created. 
    21:25:31.41 BackGroundDefault.jpg renamed to img24.jpg. 
    21:25:31.41 Image applied to .DLL file. 
    21:25:37.68 User.bmp replaced. 
    21:25:37.83 Default Windows theme has been replaced with VBOX.theme.  
    21:25:37.83 System32\oobe\Info folder has been created. 
    21:25:37.89 Required theme files transferred to System32\oobe\Info folder. 
    21:25:38.32 MRP Branding script has completed.
    21:28:15.21 BIOS Mode: Legacy, Partition Type: MBR 
    21:28:15.21 Device not connected to the Internet, online license check failed. 
    21:28:19.70 License Status: Not licensed. 
    Thank you for using the project, MRP has now completed.
    Images below show the progress/results of my Vista VM test.

    vb1-install-ages.pngvb2-enternameetc.pngvb3-desktop and logos.png
    Last edited by mxman2k; 12 Jan 2017 at 19:30. Reason: added info..
    Remember tiny pixels make up the whole picture!

  4. #354
    MDL Senior Member mxman2k's Avatar
    Join Date
    21 Jun 2007
    Location
    England
    Posts
    325
    Thanks Information

    Lightbulb Using a Virtual Machine for testing MRP or in general.

    Remember tiny pixels make up the whole picture!

  5. #355
    MDL Guru Mr.X's Avatar
    Join Date
    15 Jul 2013
    Posts
    4,538
    Thanks Information

    Default VMware direct download links


  6. #356
    MDL Guru Enthousiast's Avatar
    Join Date
    30 Oct 2009
    Location
    MDL Testlabz
    Posts
    4,855
    Thanks Information

    Default

    I also have tested MRP_Enginering50s.7z in VMWare, I've installed windows (win 10.14393.693 Education N x86 nl-NL RETAiL) via Murphy78's Diskpart & Image apply script 1.2.8.

    I've used the $OEM$ Folder inside the "iso\x86\sources" and also the "iso\x64\sources" folder (multi-architecture iso, like the MCT makes). I will test with the project inside the wim (that's how i normally use MRP).

    On standard windows setup it works:

    Code:
    Multi-OEM/Retail Project Version : 170108-R50s-BaseLine  [MRP/MDL] 
     
    Files present and extracted successfully. 
     
    OEM's folder detected, structure appears OK. 
     
    OS Installation Date: do 12-01-2017 
     
    17:33:44,37 Windows 10 Education N x86 version found. 
    17:33:44,46 EducationN Edition/SKU installed. 
    17:33:44,46 Build Version: 14393.693.x86fre.rs1_release.161220-1747 
     
    DMI BIOS Information 
    #1 CS Product Name   : [VMware Virtual Platform] 
    #2 CS Model          : [VMware Virtual Platform] 
    #4 CS Vendor         : [VMware, Inc.] 
    #5 CS System Manf    : [VMware, Inc.] 
    #6 Baseboard Manf    : [Intel Corporation] 
    #8 BIOS ID           : [INTEL] 
     
    17:33:49,55 'LblDrv' flag not set, 'C:' will be left as OS default. 
    17:33:49,99 Defined VMware [VMware] manufacture found. 
    17:33:49,99 VMware [VMware] manufacture will be used for theme/branding. 
    17:33:51,13 No MSDM key detected in BIOS. 
    17:33:51,15 Force theme text file not present. 
    17:33:51,38 System Product Name - 'VMware Virtual Platform' detected and applied.
    17:33:51,38 Desktop backgrounds folder created. 
    17:33:51,40 OOBE.xml file deleted.  
    17:33:51,40 User.bmp replaced.  
    17:33:51,48 User.png replaced.  
    17:33:51,50 User-40.png replaced.  
    17:33:51,51 User-32.png replaced.  
    17:33:51,52 User-48.png replaced.  
    17:33:51,52 User-192.png replaced. 
    17:33:51,52 {Background} img105.jpg replaced. 
    17:33:51,67 Resources aero.theme has been replaced. 
    17:33:51,69 {Background} img100.jpg replaced. 
    17:33:51,73 System32\oobe\Info folder has been created. 
    17:33:51,73 Required theme files transferred to System32\oobe\Info folder. 
    17:33:52,29 MRP Branding script has completed.
    17:37:36,16 Advanced Log-On screen has been enabled.
    17:37:37,00 User Account Pictures registry entry applied. 
    17:37:37,03 'Registered Owner' registry entry corrected. 
    17:37:37,05 Detected 'defaultuser0', attempting to remove the folder... 
    17:37:37,19 Normal removal of 'defaultuser0' folder failed - retrying...  
    17:37:37,22 Forced removal of 'defaultuser0' folder successful. 
    17:37:43,25 BIOS Mode: Legacy, Partition Type: MBR 
    17:37:47,03 License Status: Not licensed. 
     
    ============================================================================  
    Please Note: It is advisable to logout or reboot your computer when possible  
                 to allow the User and Log-On background pictures to finalize.    
    ============================================================================  
     
    Thank you for using the project, MRP has now completed.
    Next test is with the project files inside the "install.esd\windows\setup\scripts"

  7. #357
    MDL Senior Member mxman2k's Avatar
    Join Date
    21 Jun 2007
    Location
    England
    Posts
    325
    Thanks Information

    Default

    That's one way i have never tried , to place the $oem$ / project within the actual WIM/ESD file, have only use the usual put in sources on the ISO way.
    Remember tiny pixels make up the whole picture!

  8. #358
    MDL Guru Enthousiast's Avatar
    Join Date
    30 Oct 2009
    Location
    MDL Testlabz
    Posts
    4,855
    Thanks Information

    Default

    Quote Originally Posted by mxman2k View Post
    That's one way i have never tried , to place the $oem$ / project within the actual WIM/ESD file, have only use the usual put in sources on the ISO way.
    On 7 SP1 and 8.1 it worked inside the install.wim/esd, i normally use the project that way on big AiO ISO's, with seperate non oem project and oem project indexes inside.

    EDIT: did a quick test, same conditions as before only now Pro x86 installed with the Murphy78 script. Also didn't run the OEM project.

    ATM integrating the oem project into install.esd.

  9. #359
    MDL Senior Member mxman2k's Avatar
    Join Date
    21 Jun 2007
    Location
    England
    Posts
    325
    Thanks Information

    Default

    I always wondered what would happen if it was directly integrated into the actual WIM/ESD.

    Never attempted it because of all the changes to the MRP recently, would be a pain to mount, replace $oem$, re commit etc.

    Now as MRP is a 'stable' baseline release I won't be updating it anytime soon, unless some nasty bug has crept in, but as no bad feedback has come in, it will stop at 50s for the time being.
    Last edited by mxman2k; 13 Jan 2017 at 01:24.
    Remember tiny pixels make up the whole picture!

  10. #360
    MDL Guru Enthousiast's Avatar
    Join Date
    30 Oct 2009
    Location
    MDL Testlabz
    Posts
    4,855
    Thanks Information

    Default

    Test with Education N with MRP project files inserted in install.wim and installed by using Murphy78's script works

    Code:
    Multi-OEM/Retail Project Version : 170108-R50s-BaseLine  [MRP/MDL] 
     
    Files present and extracted successfully. 
     
    OEM's folder detected, structure appears OK. 
     
    OS Installation Date: do 12-01-2017 
     
    18:44:06,42 Windows 10 Education N x86 version found. 
    18:44:06,53 EducationN Edition/SKU installed. 
    18:44:06,53 Build Version: 14393.693.x86fre.rs1_release.161220-1747 
     
    DMI BIOS Information 
    #1 CS Product Name   : [VMware Virtual Platform] 
    #2 CS Model          : [VMware Virtual Platform] 
    #4 CS Vendor         : [VMware, Inc.] 
    #5 CS System Manf    : [VMware, Inc.] 
    #6 Baseboard Manf    : [Intel Corporation] 
    #8 BIOS ID           : [INTEL] 
     
    18:44:13,67 'LblDrv' flag not set, 'C:' will be left as OS default. 
    18:44:14,11 Defined VMware [VMware] manufacture found. 
    18:44:14,11 VMware [VMware] manufacture will be used for theme/branding. 
    18:44:15,22 No MSDM key detected in BIOS. 
    18:44:15,22 Force theme text file not present. 
    18:44:15,48 System Product Name - 'VMware Virtual Platform' detected and applied.
    18:44:15,48 Desktop backgrounds folder created. 
    18:44:15,50 OOBE.xml file deleted.  
    18:44:15,50 User.bmp replaced.  
    18:44:15,60 User.png replaced.  
    18:44:15,60 User-40.png replaced.  
    18:44:15,61 User-32.png replaced.  
    18:44:15,61 User-48.png replaced.  
    18:44:15,61 User-192.png replaced. 
    18:44:15,61 {Background} img105.jpg replaced. 
    18:44:15,81 Resources aero.theme has been replaced. 
    18:44:15,87 {Background} img100.jpg replaced. 
    18:44:15,98 System32\oobe\Info folder has been created. 
    18:44:16,00 Required theme files transferred to System32\oobe\Info folder. 
    18:44:16,20 MRP Branding script has completed.
    18:46:29,65 Advanced Log-On screen has been enabled.
    18:46:30,00 User Account Pictures registry entry applied. 
    18:46:30,04 'Registered Owner' registry entry corrected. 
    18:46:30,04 Detected 'defaultuser0', attempting to remove the folder... 
    18:46:30,23 Removal of 'defaultuser0' folder successful. 
    18:46:39,18 BIOS Mode: Legacy, Partition Type: MBR 
    18:46:41,93 License Status: Not licensed. 
     
    ============================================================================  
    Please Note: It is advisable to logout or reboot your computer when possible  
                 to allow the User and Log-On background pictures to finalize.    
    ============================================================================  
     
    Thank you for using the project, MRP has now completed.
    Same result with install.esd

    Will implement it in all indexes and test some more.

Similar Threads

  1. Multi OEM/Retail Project
    By The_Guardian in forum MDL Projects and Applications
    Replies: 2448
    Last Post: 14 Oct 2016, 23:37
  2. Replies: 0
    Last Post: 03 Oct 2015, 03:14
  3. Win 8.x Win 7 Vista - 'Multi-OEM' ISO Project
    By searchengine in forum MDL Projects and Applications
    Replies: 2307
    Last Post: 23 Feb 2015, 10:59
  4. Project & Visio 2010 Retail
    By jmicantc in forum Microsoft Office
    Replies: 1
    Last Post: 21 Feb 2013, 07:16
  5. Retail Image to Multi OEM... all attempts failed
    By obogobo in forum Windows XP / Previous MS Operating Systems
    Replies: 12
    Last Post: 02 Apr 2012, 08:20

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •