LAS for NetScaler

Last published : Sep 24, 2026
File-based licensing system traditionally used for activating NetScaler instances will be End of Life (EOL) on April 15, 2026. License Activation Service (LAS) is the next generation technology for product activations across the suite of Citrix products. From April 15, 2026 onwards, file-based licensing will no longer function and LAS will be the only way to activate and license NetScaler instances.
To remain supported, your NetScaler and NetScaler Console deployments must be on a LAS compatible version and must be transitioned to leverage LAS based licensing.
The minimum required NetScaler versions that are LAS compatible are:
  • NetScaler ADC: 14.1-51.x, 13.1-60.x, 13.1-37.246 (FIPS)
  • NetScaler SVM: 14.1-51.x, 13.1-60.x
  • NetScaler Console service: Supported from early September 2025.
  • NetScaler Console on-prem: 14.1-51.x
Note:
LAS support for NetScaler Console on-prem is from release 14.1-51.x onwards. However, file-based licensing is deprecated as of April 15 2026 from Console on-prem releases 14.1-51.x onwards and 13.1-60.x onwards. If you upgrade to NetScaler Console on-prem release 14.1-51.x or release 13.1-60.x or later, you can continue using file-based licensing until 15th April 2026. However you must upgrade to NetScaler Console on-prem release 14.1-51.x or later, and switch to LAS before 15th April 2026 because NetScaler Console on-prem 13.1 does not support LAS.
Related information

Prerequisites

To use LAS, ensure that you have completed the following prerequisites:
  • You must have a valid Citrix Cloud account. For more information about existing cloud accounts or to onboard new cloud accounts, see Account Management.
  • The Organization ID (Org ID) linked to the Citrix Cloud account used for the LAS activation workflow must possess valid purchased entitlements. To view the current entitlements, see Entitlements.
  • For LAS-based licensing to work on hypervised environments, ensure that the dynamic MAC settings of your hypervisor are switched off.

LAS supported NetScaler license types and deployments

LAS supported license types Example product names as seen in MyCitrix portal Deployment options (link to LAS transition doc)
Citrix Platform License (CPL) Citrix Platform License contains keyword ‘Flexed’
Example: NetScaler Flexed VPX SW instance
Example: NetScaler Flexed MPX SW instance
LAS with Console service
LAS with Console on-prem Cloud Connect
Universal Hybrid Multi-Cloud (UHMC) License Citrix Universal Hybrid Multi Cloud contains keyword ‘Flexed’
Example: NetScaler Flexed VPX SW instance
Example: NetScaler Flexed MPX SW instance
Legacy Pooled Capacity/Bandwidth License Contains keyword ‘Starter Pool’
Example: ADC VPX/BLX/CPX Starter Pool for 20/20 pack, Premium Edition with 20G, 20 Instances
NetScaler Fixed Capacity /Bandwidth Subscription License Example: ADC VPX/BLX Software Subs (Fixed Model) Advanced 1 Gbps
Example: NetScaler MPX Fixed Term Software Premium 9120
Example: NetScaler SDX Fixed Term Software Premium 16030
LAS with NetScaler ADC (VPX, MPX)
LAS with NetScaler SVM (SDX)
Note:
LAS does not support any license type other than the license types specified in the preceding table.

FAQ

Are there any NetScaler licenses that the LAS does not support, and what is the path forward for those licenses?

The following table describes the path forward to LAS for some of the other legacy license types not supported by LAS.
Note:
This list is not exhaustive.
NetScaler License types not supported in LAS Path forward to LAS
Any License type with expired contract end date Expired termed licenses or perpetual licenses with expired maintenance date or expired contract expiry date are not supported in LAS. A new and supported license type needs to be purchased to transition to LAS.
Any license type running on EOL hardware Licenses running on EOL hardware are not supported in LAS. A new active/supported hardware with its relevant supported license type needs to be purchased to transition to LAS.
NetScaler VPX/MPX/SDX perpetual license with active maintenance beyond April 15, 2026 Replacement LAS compatible license for the remainder of the contract term duration will be provided which can be used to transition to LAS. Read more.
NetScaler Gateway license type with active maintenance beyond April 15, 2026 Replacement LAS compatible license for the remainder of the contract term duration will be provided which can be used to transition to LAS.
Pooled vCPU license (also known as NetScaler virtual CPU licensing) with license contract end date beyond April 15, 2026. Replacement LAS compatible license for the remainder of the contract term duration will be provided which can be used to transition to LAS.
NetScaler Marketplace VPX (Pay‑As‑You‑Go VPX) LAS works only with Citrix‑provided licenses and does not support Marketplace licenses. Customers must migrate from PAYG to BYOL VPXs to avoid service impact. Read more.
Note:
LAS-based licenses might not be available to customers where prohibited by law or regulations.
If you have questions or concerns, contact Customer Care. Citrix may limit or suspend your Citrix Maintenance for non-compliance with these requirements without liability in addition to any other remedies Citrix may have at law or equity. These requirements don’t apply where prohibited by law or regulation.

Is MPX/SDX 14000 FIPS supported in LAS?

For NetScaler MPX 14000 FIPS, LAS is supported when customers upgrade to firmware versions 14.1-66.x and 13.1-62.x. NetScaler MPX 14000 FIPS customers with perpetual licenses receive a fixed-capacity replacement license for the MPX 14080 FIPS license that supports LAS. For customers who have deployed pooled licensing on MPX 14000 FIPS, the appliance also works when they transition to LAS.
For NetScaler SDX 14000 FIPS, LAS is supported only on SVM release 13.1 starting from build 13.1-60.x. SVM 14.1 releases are not supported.
SDX 14000 FIPS customers with perpetual licenses receive a fixed-capacity replacement license for SDX 14080 FIPS that supports LAS. For customers who have deployed pooled licensing on SDX 14000 FIPS, the appliance also works when they transition to LAS.
The following table explains the SDX 14000 FIPS LAS-supported scenarios with licensing type:
SDX 14000 FIPS Licensing 13.1 SVM 14.1 SVM
Perpetual LAS is supported. Install the latest 13.1 SVM build, move to the available fixed-capacity replacement license, and follow LAS licensing steps.
Note: If a customer has not received a fixed-capacity replacement license for a perpetual license, ask your sales contact to open a ticket with the Citrix Operations team. If the customer meets the eligibility requirements, the Operations team helps issue a replacement license, which then appears in the customer’s MyCitrix portal.
Contact Citrix Support to connect with the Product Management team.
Pooled LAS is supported. Install SVM build 13.1.60.x and follow the instructions to make the license available from NetScaler Console. Contact Citrix Support to connect with the Product Management team.

Are End-of-Life (EOL) NetScaler hardware units supported by LAS?

EOL NetScaler hardware units are not supported in LAS. The following table lists the NetScaler hardware that has reached EOL in recent years.
NetScaler EOL hardware EOL date LAS support
MPX/SDX 14000-40G (All Bandwidth and Zero-capacity) April 1, 2025 No
MPX/SDX 14000-40S (All Bandwidth and Zero-capacity) April 1, 2025 No
MPX/SDX 25000-40G (All Bandwidth and Zero-capacity) April 1, 2025 No
MPX/SDX 25000A (All Bandwidth and Zero-capacity) April 1, 2025 No
MPX 25000TA (All Bandwidth) April 1, 2025 No
MPX 25000T (All Bandwidth) April 1, 2025 No
MPX/SDX 14000 (All Bandwidth and Zero-capacity) October 1, 2024 No
MPX/SDX 22000 (All Bandwidth and Zero-capacity) July 1, 2024 No
MPX 5550, MPX 5650, MPX 8005, MPX 8010, MPX/SDX 8015, MPX 8200, MPX/SDX 8400, MPX/SDX 8600, MPX/SDX 8800 January 1, 2024 No

I am using Admin Partitions on NetScaler. Will the transition to LAS impact my deployment?

If you are using VPX or SDX instances, there should be no impact. However, for MPX deployments transitioning from Fixed or Perpetual license types to Pooled or Flexed licensing, certain modifications might be required. For detailed instructions, see Admin Partition missing/fail to load after migrating from NetScaler local license to Pooled/Flexed license.

If I have transitioned from legacy file-based licensing to LAS-based licensing but still have legacy file-based licenses on my NetScaler or NetScaler Console, will this configuration cause a conflict?

There is a known issue affecting NetScaler SDX that has migrated from file-based licensing to LAS when specific criteria are met. To understand the scope, impact, and required resolution for this issue, see Important LAS Advisory: Action required for SDX customers migrating to LAS.

I am using LAS with NetScaler Console on-prem Cloud Connect. What notification support is available for this deployment?

For information related to Notifications for LAS with Console on-prem Cloud Connect, see Notification behavior for LAS with NetScaler Console on-prem Cloud Connected.

Are there any known issues with LAS exception of type license file extension?

There is a critical issue related to the use of LAS exception license file extension blobs across NetScaler components. Review the following details carefully to take the recommended actions as applicable.
  1. If you are using or planning to use LAS exception (license file extension type) with NetScaler SDX 13.1-60.x or later, or Console on-prem 13.1-60.x or later, this section applies to you. This does not apply to NetScaler SDX 14.1 or Console on-prem 14.1.
    NetScaler Console on-prem:
    If you are using or planning to use LAS exception blobs of type license file extension on Console on-prem version 13.1-60.x or later, with Console-based license types (for example, CPL, UHMC, Pooled Bandwidth), note the following:
    A critical issue (JIRA ID: NSADM-127861) will cause the Console on-prem to become non-functional, and the LAS exception license file extension will not be honored.
    To resolve this:
    • Upgrade to Console on-prem releases with the fix: 13.1-62.27 or 13.1-61.28 or 13.1-60.33.
    • Refer to the ​​LAS Exception License File Extension​​ documentation for steps and follow all the steps in the documentation if you have not already completed the steps on an earlier version.
    NetScaler SDX (SVM):
    If you are using or planning to use LAS exception blobs of type license file extension on SVM 13.1-60.x or later, with NetScaler local license types (for example, Fixed Capacity Subscription or Perpetual licenses), note the following:
    A critical issue (JIRA ID: NSSVM-7346) will cause SDX to become non-functional, and the LAS exception license file extension will not be honored.
    To resolve this:
    • Upgrade to SVM releases with the fix: 13.1-62.27 or 13.1-61.28 or 13.1-60.33.
    • Refer to the ​​​​LAS Exception License File Extension​​ documentation for steps and follow all the steps in the documentation if you have not already completed the steps on an earlier version.
  2. If you are using or planning to use LAS exception (license file extension type) with NetScaler ADC, this message applies to you.
    Note:
    The following details have been updated in the LAS Exception License File Extension documentation as well.
    NetScaler ADC:
    • When generating the LAS exception license file extension blob, do not use the Host ID shown in the NetScaler GUI.
    • Always use the Host ID obtained from the NetScaler CLI.
    If you have already used the NetScaler GUI-based Host ID, regenerate the LAS exception license file extension blob using the Host ID from the NetScaler CLI command output and re-perform all the steps. Refer to the ​​​​LAS Exception License File Extension​​ documentation for detailed steps.

In case of LAS with Pooled or Flexed license type, what is a valid bandwidth to checkout/allocate to a NetScaler instance? Is there any known issue that I must be aware of?

For VPX, CPX, BLX: The starting minimum bandwidth is 20 Mbps. In all cases, the value must always be in multiples of 10 Mbps.
Important Note detailing a known issue:
Bandwidth allocation in non-multiples of 10 Mbps is considered invalid.
While Console service now auto-heals this situation (by rounding off the bandwidth to the nearest higher multiple of 10 Mbps), it is a known issue with NetScaler licensed using Console on-premises release 14.1-73.x or earlier that can cause your NetScaler instances to become unlicensed. This known issue, depending on your NetScaler version and build, could either hide silently and cause NetScaler to go unlicensed on the next reboot or it could put your NetScaler in grace and eventually cause it to become unlicensed. The issues have been release noted with NSCONFIG-14995 and NSHELP-44344 in the following release notes:
Given this issue, it is important that you review the bandwidth checked out by all your NetScaler VPX/BLX/CPX instances and take action as soon as possible to correct or update the bandwidth value to a multiple of 10 Mbps.
For MPX, SDX: Depending on the MPX or SDX model/platform, the minimum and maximum allowed bandwidth checkout varies. In all cases, it must be in multiples of 1 Gbps. Refer to the following documentation for more details.

If my NetScaler is LAS licensed using Pooled/Flexed license type with Console on-premises and I want to change the license server from one Console on-premises to another (or from Console on-premises to Console service), how can I do it?

To move NetScaler instances licensed using Console on-premises 1 to Console on-premises 2 as the licensing server, follow these steps:
  • Step 1: Deploy and ready the Console on-premises 2 with all the license entitlements reflecting in Console on-premises 2.
  • Step 2: Add or manage the NetScaler instances on Console on-premises 2.
  • Step 3: You will see the NetScaler instances under the Migrate or License with LAS option in Console on-premises 2. Use these workflows to re-license the NetScaler instance from Console on-premises 2.
  • Step 4: Remove NetScaler from Console on-premises 1, only after Console on-premises 2 starts to act as the license server. Otherwise, Console on-premises 1 will continue to show the devices in the Migrate option and an alarm would appear on Console on-premises 1 that there are devices in grace, which is incorrect.