Hopefully that helps with activating virtual machines when using OEM media to do the install. If you have dealt with KMS in the past these commands will be very familiar. The last 5 characters of the key that was used to activate The channel of the OS – OEM, VL, Retail etc. You will need to use another method of activating Windows, such as using a MAK, or purchasing a retail license. This will bring up a screen that shows a lot of good information including If you want to activate Windows without a KMS host available and outside of a volume-activation scenario (for example, you're trying to activate a retail version of Windows client), these keys will not work.
This update enables support for Windows 8 and for Windows Server 2012. If you are having problems activating Windows 10, Server 2016, Windows 8, or Server 2012 one of these three solutions below should get you through: Command Line to Launch Activation GUI: This is handy if the GUI won’t start and you want to skip some steps to get it to work.
The issue that customers run across is that when they install from OEM media within the virtual machine, the install goes just fine – never prompts for a product key. Describes an update for Key Management Services (KMS) that is hosted in Windows Vista, in Windows Server 2008, in Windows 7, or in Windows Server 2008 R2. Typically this is done utilizing the OEM media that is shipped with the server. Server Windows Server 2012 R2 Datacenter W3GGN-FT8W3-Y4M27-J84CP-Q3VJ9: Server Windows Server 2012 R2 Essentials KNC87-3J2TX-XB4WP-VCPJV-M4FWM: Server Windows Server 2012 Core BN3D2-R7TKB-3YPBD-8DRP2-27GG4: Server Windows Server 2012 Core N 8N2M2-HWPGY-7PGT9-HGDD8-GVGGY.
With Windows 2012 OEM or Windows 2012 R2 OEM license you get the ability to run 2 virtual machines on a virtualization platform.