WilliamLam.com

  • About
    • About
    • Privacy
  • VMware Cloud Foundation
    • VMware Cloud Foundation 9.1
    • VMware Cloud Foundation 9.0
  • VKS
  • Homelab
    • Hardware Options
    • Hardware Reviews
    • Lab Deployment Scripts
    • Nested Virtualization
    • Homelab Podcasts
  • VMware Nostalgia
  • Apple
You are here: Home / VMware Cloud Foundation / Decoding vSphere (vCenter/ESXi), vSAN & Tanzu License Keys

Decoding vSphere (vCenter/ESXi), vSAN & Tanzu License Keys

06.10.2024 by William Lam // 2 Comments

For most users, you probably have a large collection of vSphere license keys that have been provisioned over the years and keeping track of the product SKU, entitled features and capacity can be a challenge, especially if you are just looking at the raw 25 character license string.

While the Broadcom Support Portal (BSP) is recommended for all license management operations(view, split, merge, etc), did you know you could also use vCenter Server to help decode a particular license key?

When you attempt to add a valid license key (ESXi, vCenter, vSAN or Tanzu) to a vCenter Server, it provides a preview of the product SKU features and capacity, where it decodes the 25 character license string into something more meaningful.

With this information, we replicate the same behavior by using the vSphere API and specifically the decodeLicense method to decode a specific license key that vCenter Server understands.

To demonstrate this functionality, I have created a PowerCLI function called Decode-VMwareLicense that will allow users to specify one or more license keys and it will automatically decode the product SKU, Capacity, Unit, Expiration, entitled components and features for each license key.

Step 1 - Download DecodeVMwareLicense.ps1 to your local system

Step 2 - Source the Decode-VMwareLicense function by running the following command:

. ./DecodeVMwareLicense.ps1

Step 3 - Connect to one of your vCenter Server using the Connect-VIServer cmdlet

Step 4 - Run the following command with an array of license keys that you wish to decode:

Decode-VMwareLicense -LicenseKeys @("AAAA","BBB","CCC","DDD")

Here is an example output for decoding four license keys that translates to vSphere Enterprise Plus, vSAN Enterprise, vSphere Enterprise Plus for VCF and vSphere Enterprise Plus for VVF:

Categories // VMware Cloud Foundation, VMware vSphere Foundation, VSAN, vSphere, vSphere Supervisor Tags // license, VMware Cloud Foundation, VMware vSphere Foundation

Comments

  1. *protectedBruce Ferrell says

    06/11/2024 at 5:48 pm

    Just out of curiosity, can this determine is this is an eval license vs a purchased license?

    I've had instance in which evals were applied and presented a purchased... Needless to say, hilarity ensued.

    Reply
    • William Lam says

      06/11/2024 at 8:41 pm

      Yup. Eval is easy as the license key will show all zeros

      Reply

Thanks for the comment!Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Search

Thank Author

Author

William is Distinguished Platform Engineering Architect in the VMware Cloud Foundation (VCF) Division at Broadcom. His primary focus is helping customers and partners build, run and operate a modern Private Cloud using the VMware Cloud Foundation (VCF) platform.

Connect

  • Bluesky
  • Email
  • GitHub
  • LinkedIn
  • Reddit
  • RSS
  • Twitter
  • Vimeo

Recent

  • Quick Tip: The Fastest Way to Clear Partitions for ESX Reinstallation 08/15/2026
  • Quick Tip: Reducing High CPU Utilization in VCF Automation (VCFA) on AMD Zen4/Zen5 CPUs 08/12/2026
  • VCF 9.1 - Quick Tip: Optimized Workflow for Configuring Distributed Transit Gateway (DTGW) with NSX Virtual Network Appliance (VNA) 08/11/2026
  • Quick Tip: Selective ESX Host Patching in VCF 9.1 08/10/2026
  • Playing with Zero Touch Provisioning (ZTP) in vSphere 9.1 using an ASUS NUC 08/07/2026
Privacy & Cookies: This site uses cookies. By continuing to use this website, you agree to their use.

To find out more, including how to control cookies, see here: Cookie Policy

Copyright WilliamLam.com © 2026

Loading Comments...