How to use Windows Server 2022 license on multiple VM instances?

Question

I am currently trying to set up an Entra Connect server to sync our Active Directory with our Entra IDs. We have a physical server running Vmware ESXi to host our AD in a VM running Windows Server 2019. I am trying to set up a second VM instance using the same Windows Server license, to host Entra Connect. Before I started working here, a third party set up this server and licensed the AD VM. There is a product key sticky on the back of the server, but using this license doesn't allow me to activate Windows server on the second VM.

My question is two part:

1. How can I check the product license on the label to see more details about it?
2. How can I verify what license was used on the first VM originally (if different from the product license on the label) to provision the second VM with that license as well?

Answer 1

Hello afunk_283,

thank you for posting on the Microsoft Community Forums.

To address your questions, let's break down the steps you need to take.

Checking the Product License

1. **Identify the Product Key Type**:
   • The product key on the label could be an OEM (Original Equipment Manufacturer) key, which is usually tied to the physical hardware it came with, or it could be a retail or volume license key.
   • OEM keys are typically used for single installations tied to the hardware they came with and can't be reused on multiple VMs or different hardware.
2. **Check Product Details Online**:
   • You can use online tools or Microsoft’s resources to check the type and validity of your product key. Websites like Microsoft's M365 admin center or tools like PID Checker can help determine details about the key.

Verifying the License Used on the First VM

1. **Check License on the First VM**:
   • **Using Command Prompt**: Open Command Prompt on the first VM with administrative privileges and type the following command:

     slmgr /dlv
     

     This will display detailed information about the Windows license on that VM, including the activation ID, license status, and partial product key.
   • **Using PowerShell**: You can also use PowerShell to get detailed information. Open PowerShell with administrative privileges and execute:

     Get-WmiObject -query 'select * from SoftwareLicensingService'
     

     This will show similar information about the licensing status.
2. **Compare with Physical Product Key**:
   • Match the partial product key shown in the output with the key on the physical label to determine if the two are the same or different. Note that only the last few characters of the product key are shown for security reasons.

Provisioning the Second VM

1. **Determine Licensing Requirements**:
   • **Volume Licensing**: If your organization has a Volume Licensing agreement, you may have access to multiple activations using a single key. Check with your IT department for available keys.
   • **Datacenter Edition**: If the physical server is licensed with Windows Server 2019 Datacenter Edition, it allows for unlimited virtual instances on the same physical server. You would not need a separate key for each VM.
2. **Activate the Second VM**:
   • If the first VM uses a Volume License or you have Datacenter Edition, use the same key for the second VM.
   • Ensure you are following Microsoft’s licensing terms; consult your Microsoft licensing representative if you’re unsure about compliance.
3. **Using the Same Product Key**:
   • If your key allows for multiple activations (like a Volume License key), you can use it to activate the second VM directly. Use

       slmgr /ipk 
     

to install the key, then

       slmgr /ato

to activate it.

Steps Summary

1. Use Command Prompt or PowerShell to check the product key on the first VM.
2. Compare the key details with the physical server label.
3. Verify your licensing type (OEM, Volume, or Datacenter).
4. If applicable, use the same Volume License or Datacenter key to activate the second VM.

If you encounter issues or have uncertainties about the licensing specifics, reaching out to your licensing reseller might be necessary to ensure you remain in compliance and get any necessary assistance with key activations.

Hope it helps.

Kind regards,

Lei

Answer 2

The last 5 of the partial product key does not match what is on the label and it says it is Volume:MAK. This still does not help me to use this license for the second VM, how can I obtain the full product key? As I mentioned above, this was configured by a third-party contractor that didn't provide us with the original product key that was used to create the first VM.