Inquiry Regarding Microsoft ESU for Windows 10 on VMware VDI

Question

Inquiry Regarding Microsoft ESU for Windows 10 on VMware VDI

Fung, Sammy 0

We would like to request clarification regarding the use of Microsoft Extended Security Updates (ESU) for Windows 10 within a VMware VDI environment. Since our VDI environment will continue to run Windows 10 beyond its standard support lifecycle, we would like to ensure compliance and proper implementation of ESU.

Specifically, we would appreciate your advice on the following points:

Licensing

How should ESU licenses be acquired and assigned in a VMware VDI environment?

  Are licenses required per concurrent session, per virtual machine, or per device?
  
  **Activation**
  
     What are the supported activation methods for ESU in VDI (e.g., KMS, MAK, Active Directory-based)?
     
        Are there any special considerations for non-persistent VDI environments?
        
        **Technical Implementation**
        
           What are the recommended steps to deploy and validate ESU on Windows 10 VDI desktops?
           
              How can we verify that ESU patches are correctly applied in the VDI environment?
              
              **Support and Limitations**
              
                 Are there any known limitations or restrictions when applying ESU in a VMware-based VDI infrastructure?
                 
                    Is there specific Microsoft documentation or best practice guidance you can share for VDI scenarios?

At present, we are running approximately 100 concurrent VDI sessions. Your guidance on how ESU applies in this scenario will help us plan our licensing and technical approach.

1 answer

Your answer

Answer 1

Dear Fung, Sammy,

Below is a summary of guidance based on your key questions:

A) Licensing

ESU Licensing Model: ESU licenses are typically assigned per device. In a VDI environment, this means each virtual machine (VM) that runs Windows 10 and requires ESU coverage must be licensed individually.

Concurrent Sessions: Licensing is not based on concurrent sessions. Even in non-persistent environments, each image or instance that receives updates must be covered.

Acquisition: ESU licenses can be purchased through eligible Microsoft Volume Licensing programs. For customers with Software Assurance or Enterprise Agreements, your licensing partner can assist with procurement.

B) Activation

Supported Methods: ESU activation supports Multiple Activation Key (MAK) and Key Management Service (KMS).

Recommended for VDI:

KMS is preferred for persistent VDI environments due to centralized management.

  **MAK** may be used in non-persistent environments, but activation must be handled carefully to avoid exhausting activation counts.
  
  **Non-Persistent Considerations**:
  
     For non-persistent VMs, consider using **Volume Activation Management Tool (VAMT)** to manage MAK activations.
     
        Ensure that your base image is activated before deployment to avoid activation failures across sessions.

C) Technical Implementation

Deployment Steps:

Install the ESU license key using slmgr /ipk <ESU Key>

  Activate the key using `slmgr /ato`
  
     Install the ESU preparation package and servicing stack updates
     
        Apply monthly ESU updates via Windows Update, WSUS, or your patch management solution
        
        **Validation**:
        
           Use `slmgr /dlv` to confirm ESU activation status
           
              Check update history in **Settings > Windows Update** or via PowerShell to verify ESU patches are applied

D) Support and Limitations

Known Limitations:

ESU does not extend support for all components (e.g., certain apps or features may still reach end-of-life)

  VMware snapshots or rollback features may interfere with activation persistence if not managed properly
  
  **Documentation**:
  
     Microsoft provides ESU deployment guidance on Learn.microsoft.com
     
        While focused on Windows 7, many principles apply to Windows 10 ESU as well.
        
           For virtualization-specific licensing, refer to VMware’s Microsoft Client OS Licensing Guide

If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.

Best regards,

Harry Phan

Share via

Inquiry Regarding Microsoft ESU for Windows 10 on VMware VDI

1 answer

Your answer