#Seriales de activacion de windows 10 license

I will leave it to the philosophers or others who have more time than me, to debate if this is legit use of license for win10.Īrguably last time I looked, it is hard to get a straight answer from MS on licensing, other than generally if you ask, they tell you that whatever you want is not valid and you must pay them more, to do what you want. So no intervention was required to get it to self-activate, it 'just worked'.

#Seriales de activacion de windows 10 install

As I might have hoped, it did NOT ask me what flavour of win10 I was trying to install (Home, Pro, etc) during install process - ie - first hint that the new config was doing what I wanted, ie, it already knew what license was available so did not ask.Īfter install windows, get network connected / installed VirtIO drivers.Ĭheck status of windows 10 activation in settings - bingo - it shows a happy 'windows is activated with digital license' message as per norm Virtio0: data:100/vm-100-disk-0.qcow2,size=500Gīoot the VM from my vanilla Win10 ISO. Smbios1: uuid=,manufacturer=,product=,serial=ĬONTENT THERE FOR REF cat /etc/pve/qemu-server/100.confĪrgs: -acpitable file=/data/images/100/slic_table $ dmidecode | grep -A8 'System Information'Īrgs: -acpitable file=/path/to/slic_table rw-r-r- 1 root root 85 May 26 05:37 /data/images/100/slic_tableĮDIT MY CONFIG vi /etc/pve/qemu-server/100.conf SLIC_TABLE FILE NOW ls -la /data/images/100/slic_table THEN HARVEST THE INFO INTO A FILE YOU WILL NEED TO REFER TO IN YOUR VM cat /sys/firmware/acpi/tables/MSDM > slic_tableįINALLY: WITH THIS ALL IN PLACE MANUALLY EDIT THE VM CONFIG FILE, APPROX THUS IS ENDGAME: MSDMU▒LENOVOTC-M2T ABCD IN ABOVE I HAVE CHANGED ALPHA LETTERS TO HIDE MY ACTUAL VALUE. THIS IS WHAT IT LOOKS LIKE IF YOU JUST CAT THE cat /sys/firmware/acpi/tables/MSDM (NOTE VALUES ABOVE ARE SLIGHTLY TWEAKED FOR INFO NEEDED PART TWO: SKU Number: LENOVO_MT_11DA_BU_Think_FM_ThinkCentre M70t Get Info needed PART dmidecode | grep -A8 'System Information'

Many thanks for the reply and if you could point me in correct direction WRT the SLIC Table Pass Through, that would be great. You don't end up spending a lot of time and effort going to agonizing trouble trying to determine what is suitable / and then attempting to adhere to extreme license complications).Īnyhoo. (This kind of 'license hell' is part of why I love Linux stack environments / with open source license products. (I did find a thread on this topic, at and the level of complexity involved makes me just shake my head.

#Seriales de activacion de windows 10 software

(ie, a Win10 instance running on the hardware with which the license was sold) - Strictly speaking I am not sure Microsoft officially condone Win10 as a VM Guest OS (unless possibly you have lots of extra Enterprise / Software Assurance licenses involved - see thread link below) so attempting to stay on the good side of MS License restrictions with 100% strict adherence in such a scenario is - generally a lost cause. Strictly speaking I am not going to fret about win10 license 'validity' to the degree beyond this. I am slightly confused how such a process can be time intensive (a few config stanzas for pass through in the KVM VM Config file most likely? But maybe there is more song and dance?)

#Seriales de activacion de windows 10 how to

If you can point me to any hints on how to do the SLIC Table pass through from physical to virtual, that would be great.

#Seriales de activacion de windows 10 license key

ie, just plan on spending the extra $200 or whatever for a vanilla Win10pro license key for install purpose for the VM. I am curious if anyone knows, is there any way I can make use of this Bios-embedded license key for my windows VM Guest install on proxmox? Or is that more or less impossible, because we're using a virtualized bios for Proxmox KVM Win10 guest, and no way to harvest/pass through this 'Windows license key' from the underlying hardware. The system hardware - comes out of box with a Win10Pro license bundled, which is 'burned into the bios' of the hardware / motherboard. With an add-in LSI Raid card it makes a decent little server (Pair of SSD drives for proxmox, and probably a pair of SATA drives for a 'bulk backup data mirror storage disk volume'). The Lenovo workstation I'm planning to use is a tower / i7 CPU / support for 32gb ram easily / decent solid system. They need 2 x small VMs, one will be a linux ClearOS 'NAS Fileserver' and the second will be Win10Pro for running Sage Simply Accounting. I'm setting up a small 'lenovo mid-level workstation' as a small on-prem server for a client. Hi, a 'fun' question I wonder if anyone has experience with.