VCF 9 license expiration date and core allocation discrepancies in Business Services Console

Products

• VCF Operations

Issue/Introduction

• After splitting a license in the VCF Business Services Console (BSC), the newly created license displays approximately 180 days from the split date), even though the contract expires in 2029.
  
  
• License cores appear to be divided "randomly" or do not match the expected subscription line items.

Environment

VMware Cloud Foundation (VCF) 9.x

Cause

• Heartbeat Mechanism: VCF 9 uses a Solution License File with a rolling 180-day validity window. The console displays the next reporting milestone, not the contract end date.
  
  
• Allocation Logic: The BSC allocates cores from available subscriptions in a top-to-bottom sequence based on the order they appear in the UI. If specific lines are not targeted, cores are drawn from the first available pool.

Resolution

The variation in the displayed end date is expected system behavior and does not affect your legal entitlement.

1. To resolve the date display: Update your licenses in the VCF Operations instance. Navigate to License Management > Registration and click Update Licenses. This triggers a usage report and refreshes the 180-day window.
   
   
2. To resolve core allocation: When splitting, identify the specific subscription line item you wish to draw from. Perform separate split operations for each individual subscription rather than splitting from a combined total to ensure cores are drawn from the correct contract.
   
   
3. For detailed steps on the splitting process, see Splitting a VCF 9 license file in the VMware Cloud Foundation Business Services Console.

Additional Information

Different End Date Displayed After Splitting a VCF License in Business Services Console