Add or Update Horizon 8 License

You can add or update a perpetual or term license key in your Horizon 8 environment while your pod is running. You do not need to reboot the system, and access to desktops and applications is not interrupted.

SaaS subscription licenses for Horizon 8 do not require keys, but need the Horizon Cloud Connector virtual appliance or Horizon Edge (depending on the version of the control plane you are connecting to) for connecting to Horizon Control Plane for license enablement. For information on enabling a SaaS subscription license, see Enabling Horizon 8 for SaaS Subscription Licenses and Horizon Control Plane Services in the Horizon 8 Installation and Upgrade guide.

Horizon SaaS subscription licenses include the date of the last license successful synchronization with the Horizon Cloud Control Plane and an additional grace period. The Horizon Cloud License service on the Horizon Control Plane syncs once every 24 hours with the connection server to maintain the health of the subscription license.

Note: A Horizon 8 pod can accept only one license key. If you have more than one license, you can use them for different pods. To use multiple keys in the same pod, work with your Omnissa representative to obtain an exception.

Horizon term licenses include an additional 30 days beyond the written expiration date for continued access. For example, if you have a Horizon term license with the expiration date of 1 Jan 2024, the 30-day grace period means that you have access until 12:00 AM local time on 1 Feb 2024. When the grace period ends, Horizon Console will enter restricted mode and you will be unable to add new pools or farms, expand existing pools and farms, or schedule push images for desktops and farms. You can continue to work with existing desktops, remote applications, and virtual machines.

The Horizon term license grace period **only** applies to Horizon 8. The vSphere for Desktop term license that is included with your Horizon term license bundle follows a different behavior when it expires. After the vSphere license expires, it immediately transitions to a restricted level of service. This restriction prevents operations such as powering on virtual machines, provisioning new virtual machines, and refreshing existing instant clone desktops.

To ensure uninterrupted service, contact your Broadcom representative to renew your license before the expiration date.

Mixing Licenses in the Same Horizon 8 Pod

Since each Horizon 8 pod only accepts one license key or one subscription bundle, certain combinations of license mixing is not supported. For those combinations that are supported, work with your Omnissa representative to obtain an exception approval.

Note: There are mechanisms in place to monitor use of two different licenses. It is your responsibility to stay compliant at all times.

• Mixing NU and CCU bundles in the same Horizon 8 pod is permitted via an exception approval.
• Mixing different Horizon Term editions in the same Horizon 8 pod is permitted via an exception approval.
• Mixing the same license bundle with different term lengths in the same Horizon 8 pod is permitted via an exception approval.
• Mixing different Horizon SaaS editions in the same Horizon 8 pod is permitted, depending on the editions, via an exception approval.
  • You can mix and match Horizon Universal Subscription, Horizon Apps Standard Subscription, and Horizon Apps Universal Subscription licenses.
  • You can mix and match Horizon Standard Plus Subscription and Horizon Enterprise Plus Subscription licenses.
  • Horizon Standard Plus Subscription or Horizon Enterprise Plus Subscription licenses cannot mix with any other Horizon SaaS edition (e.g., Horizon Universal Subscription).
• You cannot mix different license types in the same Horizon 8 pod: Term license and SaaS license, Term and Perpetual, Perpetual and SaaS.

Mixing Licenses in the Same Horizon 8 Pod

Since each Horizon 8 pod only accepts one license key or one subscription bundle, certain combinations of license mixing is not supported. For those combinations that are supported, work with your Omnissa representative to obtain an exception approval.

Note: There are mechanisms in place to monitor use of two different licenses. It is your responsibility to stay compliant at all times.

• Mixing NU and CCU bundles in the same Horizon 8 pod is permitted via an exception approval.
• Mixing different Horizon Term editions in the same Horizon 8 pod is permitted via an exception approval.
• Mixing the same license bundle with different term lengths in the same Horizon 8 pod is permitted via an exception approval.
• Mixing different Horizon SaaS editions in the same Horizon 8 pod is permitted, depending on the editions, via an exception approval.
  • You can mix and match Horizon Universal Subscription, Horizon Apps Standard Subscription, and Horizon Apps Universal Subscription licenses.
  • You can mix and match Horizon Standard Plus Subscription and Horizon Enterprise Plus Subscription licenses.
  • Horizon Standard Plus Subscription or Horizon Enterprise Plus Subscription licenses cannot mix with any other Horizon SaaS edition (e.g., Horizon Universal Subscription).
• You cannot mix different license types in the same Horizon 8 pod: Term license and SaaS license, Term and Perpetual, Perpetual and SaaS.

Prerequisites

• For a perpetual or term license, obtain a valid product license key. License keys can be found in the Omnissa Customer Connect portal.

• For a perpetual or term license upgrade to Horizon 8 2412 or later, you must obtain a new license key from the Omnissa Customer Connect portal that uses the Omnissa licensing module. If you fail to transition to the new Omnissa license key within the 60-day grace period, Horizon Console will enter restricted mode with limited functionality.

Note: Licenses for Horizon 7 do not work for Horizon 8 versions. If you have a Horizon 7 license, you must get a new license key for Horizon 8.

Note: Horizon 2412 and beyond Term and Perpetual license customers require a new format key. SaaS subscription customers are not impacted by the license key format change.

Procedure

1. In Horizon Console, select Settings > Product Licensing and Usage > Licensing.

   The first and last five characters of the current license key are displayed in the Licensing panel.

2. To edit the license key, click Edit License, enter the license serial number and click OK.

   The Licensing Settings panel shows the updated licensing information.

3. To change from a subscription license to a term license for a Horizon pod, click Use Perpetual/Term License and click OK.

   The Licensing Settings panel shows the updated licensing information.

4. To change from a term or perpetual license to a subscription license for a Horizon pod, click Use Subscription License and click OK. The Horizon Cloud Service administrator can then enable the Horizon pod for a subscription license.

5. To verify the license expiration date for a term or perpetual license, see License Expiration. For a subscription license, see License Synchronisation Expiration and verify subscription and usage details in the Horizon Cloud Next Gen Control Plane.

6. Verify that the component licenses are enabled or disabled based on the edition of Horizon 8 that your product license entitles you to use. The features and capabilities of Omnissa Horizon depend on license editions. For a comparison of feature sets in each edition, see Horizon SaaS matrix and Horizon subscription term editions.