Clarification on Windows Server 2022 Standard VM limits with a 16-core package
Clarification on Windows Server 2022 Standard VM limits with a 16-core package
I need some guidance because I’ve encountered many conflicting details online about this topic. I installed Windows Server 2022 Standard on a VM inside VMware ESXi, which hosts the DC, DNS, and DHCP services. I understand certain server roles or features won’t allow installation or setup on the same VM as a DC. I created a new VM with another instance of Windows Server 2022 using the same product key from the vendor. Based on my knowledge, I can run up to two instances of Windows Server with that key regardless of hypervisor, as long as I have the correct core pack. My server has six cores and twelve threads per socket, so I don’t have a lot of threads to assign across VMs, but the network side is simpler—about ten computers and under fifty devices total on both wired and wireless connections. On the second VM I set up, it will host other roles that can’t run alongside a DC. I used the same license key via DISM and SLMGR commands and restarted the VM. Now it’s reporting that this instance isn’t licensed while the first one is. Am I missing something or misreading the rules? Is this only relevant for VMs in a hypervisor environment? If so, would roles like RRAS and IPAM function well in a hypervisor setup on the DC? Thank you for your assistance!
Reach out to Microsoft support. If an audit occurs, which response do you believe is more reliable: Microsoft Support informed me ... Or a user on a random online forum shared this information ...
I'm not entirely certain about this, but any environment not intended for personal use requires a separate license key. If you intend to break down the first VM, you should be able to reuse it. Reach out to Microsoft for guidance.