Windows server 2022 license unable to be activated after moving the VM to another host

When moving Windows Server VMs between different hosts, activation issues can arise due to the way Windows Server handles licensing and activation. Here are some steps you can take to troubleshoot and potentially resolve the activation problems:

1. Check Activation Status: Use the command cscript C:\Windows\System32\slmgr.vbs /dlv on the problematic VMs to check their activation status and see if there are any specific error messages that can guide you.
2. Duplicate Client Machine ID (CMID): If the VMs were created from a common image, they might share the same CMID, which can cause activation issues. You can generalize the original VM using Sysprep with the SkipRearm parameter set to 0, or rearm the existing VMs using slmgr /rearm followed by a restart.
3. License Compliance: Ensure that the licenses you are using are compliant with Microsoft’s licensing terms. Each VM may require its own unique license depending on how they are configured and activated.
4. KMS Activation: If you are using Key Management Services (KMS) for activation, ensure that the KMS server is reachable and properly configured. If you are moving VMs to a different environment, verify that the KMS server settings are still applicable.
5. Firewall and Proxy Settings: Make sure that any firewalls or proxies are configured to allow necessary connections for activation processes, especially if the VMs are now in a different network environment.

If these steps do not resolve the issue, consider reaching out to Microsoft support for further assistance with your specific licensing and activation scenario.

References:

• Windows activation - duplicate Client Machine ID
• Windows activation watermark continues to be displayed

Hi Hisham,

Thank you for sharing your question.

For better assistance, may I ask that what kind of licenses you are using to activate and what is the specific error message you received? You also mentioned about different serials, what exactly is different?

Additionally, since you have multiple licenses and VMs, I highly recommend using the VAMT to make it much easier to track and manage activations across all your machines. Here are for your reference: Introduction to VAMT

Hope this helps! Feel free to let me know if you have any other questions.