I added those lines to my Virtual Machine configuration file and rebooted the OS, re-ran the tool and now #09 is reporting SLIC 2.3 - does that mean the VM can now see what it needs? Trying to activate with key fails with "can't be used to activate this edition of windows". Code: MRP - OEM Query Tool v50.0 Enhanced -- 03/03/2018 {UTC} -- 1:35pm ------------------------------------------- - Basic OEM Information For This Computer - ------------------------------------------- OS Version {Registry} - Windows Server 2012 R2 Standard Evaluation OS Version {SKU} - Server Standard {evaluation installation} {79} OS Edition {Registry} - ServerStandardEval {79} OS Edition {CBS} - ServerStandardEval OS Architecture - 64 Bit OS Build Number - 9600 OS Installation Type - Server OS Language Name/Code - en-US / Dec:1033 {Hex:409} OS Locale - en-US OS Language Value - ENU OS Installation Date - 3/3/2018 12:58:44 PM {Localized Date Format} CPU Name - Intel{R} Xeon{R} CPU E3-1226 v3 @ 3.30GHz {x2} CPU Description - Intel64 Family 6 Model 60 Stepping 3 CPU Architecture - 32/64 Bit CPU ID Code - [0FABFBFF000006C3] CPU Cores/Threads - [2] / [2] CPU VT Mode Enabled - [No] Boot Drive Information - BusType: SAS, Mode: AHCI, Partition: MBR, DriveType: SSD, FS: NTFS Boot Drive Model Name - Virtual disk Bios Information - Type: Phoenix Technologies LTD , Version: 6.00 , Date: 04/05/2016 Total Physical Memory - 8191 Mb Available Memory - 7588 Mb GPU Primary Adaptor Name - Microsoft Basic Display Adapter GPU Primary Adaptor Info - Resolution: 1024x768 , Driver Date: 06/21/2006 , Driver Vers: 6.3.9600.16384 -------------------- - Scanned DMI/BIOS - -------------------- #01 CSProduct Name - ThinkServer TS140 #09 SLIC Information - 2.3 #02 CSModel Name - ThinkServer TS140 #10 Product Key - Not Shown On Saved Report #03 CSBaseboard Prod - 440BX Desktop Reference Platfo #11 MSDM Key - No MSDM Table Detected #04 CSProduct Vendor - LENOVO #11 MSDM Edition - Undefined #05 CSManufacturer - LENOVO #11 MSDM Brand Name - Undefined #06 Baseboard MFR - Intel Corporation #12 BIOS/Boot Mode - Legacy/MBR #07 Serial/Service Tag - Not Shown On Saved Report #13 Certificate - Not Present #08 BIOS or SLIC ID - LENOVO - 6040000 #14 License Status - Licensed ----------- - Summary - ----------- OEM Theme/Branding - Lenovo [id: #04] OEM Activation Vista/7 - Lenovo Valid OEM Consumer OS - Vista/Win7 Only Detected .Net Versions - v1.1.4322 / v2.0.50727 / v4.0.30319 / v4.5.51641 Powershell Version{s} - 1.0, 2.0, 3.0, 4.0 License Status Reason - 0x4004FC04: This computer is running within the time-based validity allowance. ** End of Query Tool report. **
I was referring to original OEM (i.e. Lenovo) provided update not to home-made ones or from the mainboard manufacturer (if exists for that OEM board).
If the PC they are using has a genuine server board then the SLIC will be present even with a bios update because the OEM's update would not touch that unless it is to change it to a higher slic version for example some older Toshiba laptops came with Vista slic 2.0 a later bios update changed the slic to 2.1 so that Windows 7 can be installed. It all depends on the OEM, Lenovo i believe in this case.
HELLO! Is still the EVAL that cannot be activated. You'll need to convert to non-Eval: https://forums.mydigitallife.net/th...l-project-mrp-mk3.71555/page-116#post-1415333. The SLIC 2.3 is perfectly detected now.
As the 2.3 slic is being seen then yes it should work. However as the installation is still EVAL it wont activate and the install did not insert the Lenovo certificate to be able to activate as at that time no slic was present.
So since he has now slic table detected after adding the 3 setting lines you mentionned so we can imagine that the update bios he did previously removed the slic.
No the slic is still present in the Host's bios. Version 2.3 if you look at the last QT report. It was not passed through to the VM before, which it is now and shows that it is present. You still have a lot to learn young grasshopper (from 'Kung Fu 1972–1975' with David Carradine). You need to read the reports/logs this is what they are designed for, not just for pretty words, it can help pinpoint areas of problems. In this case, it was a EVAL ISO used. The slic was not present as mentioned above so even if it wasn't a EVAL the MRP could not 'see' the slic to do the activation side.
I tried with the command in the post... Code: dism /online /Set-Edition:ServerStandard /ProductKey:REPLACED_WITH_KEY_I_PULLED_BEFORE_FORMAT /AcceptEULA It accepted the command and converted by install from Trial to Standard. When I go into System screen it shows "Windows is not activated". I think I will re-install the OS now that the VM can see the BIOS SLIC - so that the Lenovo certificate can be inserted. Will report back my progress. Appreciate all the help you guys have provided.
If you now reinstall on that same VM with the slic passthough MRP should now detect the slic and process the activation side as well It could not activate because at the first installation with no SLIC present MRP did not insert the Lenovo certificate, so at present you have two of the three factors that are required (key and slic), which wont allow OEM activation to occur. A reinstall should hopefully work... Unless something went wrong in my database! as not tested Lenovo Server, we only tested DELL when MRP was updated to do Servers.
It is OK to use 9600.17050.WINBLUE_REFRESH.140317-1640_X64FRE_SERVER_EVAL_EN-US-IR3_SSS_X64FREE_EN-US_DV9.iso media? This is the trial ISO I pulled from MS. Or should I use a standard windows server 2012 r2 iso (en_windows_server_2012_r2_with_update_x64_dvd_4065220.iso)?
The fun we had sorting the server stuff out , remember @s1ave77 The activation side was easy compared with the right order in which the DISM addon feature's was needed for each Server OS! It has paid off all that hard work
that's why i am here, to learn and i can say that i have learnt many things since i have registered to this site. so to come back to the point, should the slic have passed throught the VM without adding the 3 settings line you mentionned ? or it is necessary to add these 3 setings lines so that slic can pass through the VM ?
Nope VM's dont usually passthrough the slic etc you have to tell it to. VMware uses those line I posted. VirtualBox uses another way if i remember, same sort of thing with the config file. Other VM software such as XEN, Hyper-V etc probably have other ways.
I have learnt a lot since taking over the helm of the project, with help from s1ave77 , aboddi1406 and others with the scripting side it has become what it is today.
ok so that means that you have to add these lines yourself into the VM so the slic can pass through the VM, correct ?
yes if you wish to use the Host's slic. It does not affect the activation of the Host as it only the ACPI SLIC table being passed though.
Supermicro X9DAi, Lite-On CX2 NVMe, QT50 still reports AHCI; I will try Samsung SM953 drive. Code: MRP - OEM Query Tool v50.0 Enhanced -- 03/04/2018 {UTC} -- 12:29am ------------------------------------------- - Basic OEM Information For This Computer - ------------------------------------------- OS Version {SKU} - Windows 10 Pro {48} OS Edition {Registry} - Professional {48} OS Edition {CBS} - Professional OS Architecture - 64 Bit OS Build/Update Revision - 16299 {rs3_release} / 248 OS Installation Type - Client OS Language Name/Code - cs-CZ / Dec:1029 {Hex:405} OS Locale - cs-CZ OS Language Value - CSY OS Installation Date - 25.02.2018 2:14:01 {Localized Date Format} CPU Name - Intel{R} Xeon{R} CPU E5-2670 0 @ 2.60GHz {x2} CPU Description - Intel64 Family 6 Model 45 Stepping 7 CPU Architecture - 32/64 Bit CPU ID Code - [BFEBFBFF000206D7] CPU Cores/Threads - [16] / [32] CPU VT Mode Enabled - [Yes] Boot Drive Information - BusType: NVMe, Mode: AHCI, Partition: GPT, DriveType: SSD, FS: NTFS Boot Drive Model Name - CX2-8B256-Q11 NVMe LITEON 256GB Bios Information - Type: American Megatrends Inc. , Version: 3.2 , Date: 05/09/2015 Total Physical Memory - 65508 Mb Available Memory - 61557 Mb GPU Primary Adaptor Name - NVIDIA Quadro K4000 GPU Primary Adaptor Info - Resolution: 2560x1440 , Driver Date: 02/27/2018 , Driver Vers: 23.21.13.9103 -------------------- - Scanned DMI/BIOS - -------------------- #01 CSProduct Name - X9DAi #09 SLIC Information - 2.4 #02 CSModel Name - X9DAi #10 Product Key - Not Shown On Saved Report #03 CSBaseboard Prod - X9DAi #11 MSDM Key - No MSDM Table Detected #04 CSProduct Vendor - Supermicro #11 MSDM Edition - Undefined #05 CSManufacturer - Supermicro #11 MSDM Brand Name - Undefined #06 Baseboard MFR - Supermicro #12 BIOS/Boot Mode - UEFI/GPT #07 Serial/Service Tag - Not Shown On Saved Report #13 Certificate - Not Present #08 BIOS or SLIC ID - - 1072009 #14 License Status - Licensed {Retail} ----------- - Summary - ----------- OEM Theme/Branding - Supermicro [id: #04] OEM Activation Vista/7 - Un-Listed Valid OEM Consumer OS - Vista/Win7 Detected .Net Versions - 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: - SLIC ID or Version may not show correctly with UEFI or Secure Boot enabled. ** End of Query Tool report. **