We should be able to handle the migration itself but have some questions about proper licensing of our Windows VMs. Since this is really annoying and we do not want to trouble our heads about it anymore we thought extending one of our Proxmox-Clusters and migrating all the virtual machines (vhdx) to it could be a good idea. slmgr.We have been experiencing serious SES-related problems with our Hyper-V-Failovercluster for a couple of weeks now. Once I had added my CSLVK, I was able to jump back into a new Windows Server 2019 virtual machine that I had created and use the slmgr.vbs command below to successfully activate the new virtual machine against my KMS server. After entered, you’ll see a pop-up message stating that the key has been successfully added. Replacing with my actual key issued by MS. Entering the command below, allowed it to get added successfully. The workaround was to the slmgr.vbs tool.

Apparently though, I found out that this is a know issue. I tried a couple more times, I even reinstalled the VAMT tool from the ADK toolkit. Jumping back into my KMS server, i tried to import the key directly into VAMT, also known as the Volume Activation Management Tool. (Note: Menu options may change, I called in February 2020) That got me directly in contact with a representative that was able to issue the key.

To contact them I called 1-86, option 4, option 1. The whole process took just under 5 minutes for me, and I was able to verify that I saw the key in my portal while I was still on the phone with MS.

You actually have to call them, verify some info, and have them generate a key for you which will then show up in your portal. The servers and desktops then use a Generic Volume License Key (GVLK) which let the machine know it needs to find and activate against an internal KMS resource and not go out to activate against Microsoft’s servers.įWIW – you can find all of the GVLK product keys here – Īpparently even if you have the Volume Licensing agreement, MS doesn’t automatically issue the CSLVK KMS key to you in your portal. It’s basically your volume license key that gets hosted internally. The CSLVK KMS key is what gets loaded into the KMS server. We did and so I jumped into the MS Volume Licensing Service Center (VLSC) portal to grab our Client Specific Volume License Key (CSLVK) Key Management Service (KMS) key. To begin with, you need to have a Volume Licensing agreement with Microsoft. Was beginning the introduction of Windows Server 2019 to a work environment and ran into some hurdles that were easily cleared, but want to share…

Windows Server 2019 Datacenter KMS