Note: This article is no longer current. For the latest information and updated resources, please visit our new landing page here: https://xentegra.com/citrix-las-deadline-2026/
A: Citrix is fundamentally changing how licensing works for on-premises products. The company is ending support for traditional file-based licensing and moving entirely to the License Activation Service (LAS).
Starting April 15, 2026, on-premises products will only recognize licensing through LAS. Any remaining file-based licenses will simply cease to function after that date. This affects major on-premises components including Citrix Virtual Apps and Desktops (CVAD) and its optional components like PVS and WEM, XenServer hypervisor, and NetScaler ADC and Console.
It’s important to note that this is purely a technical licensing architecture change. Your commercial terms, contracts, and pricing remain unaffected. If you’re already using Citrix Cloud services exclusively, this change doesn’t impact you at all.
A: This is probably our most frequently asked question, and the answer is nuanced but reassuring: No, you don’t have to move your entire deployment to the cloud.
Your application delivery infrastructure and desktop environments can remain completely on-premises. Your controllers, VDAs, NetScaler appliances, and XenServer hosts can all stay exactly where they are.
However, there is one cloud dependency you need to understand: your on-premises License Server must register with Citrix Cloud to activate licenses via LAS. Think of it this way—your workloads stay on-prem, but the licensing control plane has a cloud component.
So you’re not moving your VDI or ADC workloads to Citrix Cloud, but you do need to allow cloud-registration for licensing purposes. This means ensuring your License Server has outbound HTTPS connectivity to the LAS endpoint.
A: This is a legitimate concern for organizations with strict security requirements or disconnected environments. If your infrastructure is truly isolated with no outbound internet access, you’ll need to work directly with Citrix on special arrangements for “dark site” licensing.
I strongly recommend reaching out to Citrix as early as possible if you’re in this situation. These exception cases require planning and may involve unique technical solutions that need to be architected well before the April 2026 deadline.
A: The time to start is now. Here’s my recommended action plan:
1. Inventory Your Environment (Do This First)
2. Upgrade to LAS-Compatible Versions You’ll need to ensure you’re running supported versions across your stack:
3. Enable Network Connectivity Work with your network and security teams to allow your on-premises License Server to register with Citrix Cloud. You’ll need outbound HTTPS connectivity to the LAS endpoint. The good news is there’s a grace period—if connectivity is temporarily lost, you have up to 30 days of cached licensing.
4. Timeline Planning
5. Post-Migration Validation
A: I cannot stress this enough: if you do nothing, your file-based licenses will cease to function on April 15, 2026. This will cause immediate service disruption for your users. Your virtual desktops, applications, and NetScaler services that depend on those licenses will be affected.
This isn’t a soft deadline or a suggestion—it’s a hard cutoff. Organizations that delay risk significant business impact.
A: Yes. Customers with perpetual license models and certain legacy NetScaler license types—such as pooled vCPU or CICO (Concurrent In/Concurrent Out) models—may face additional restrictions under LAS.
If you’re using these license types, I recommend engaging with your Citrix account team early to understand the specific implications for your deployment.
A: Beyond the obvious risk of service disruption if you miss the deadline, here are the key concerns I’m seeing:
Network and Firewall Changes: Your operations teams need to plan for and implement firewall rules to allow LAS registration. This often requires change control processes that take time.
Version Alignment: Some organizations are running older, stable versions that aren’t LAS-compatible. Upgrading always carries risk and requires testing, which means you need adequate lead time.
Compliance and Security: For organizations with strong isolation requirements or compliance constraints, the introduction of cloud connectivity for licensing requires careful evaluation. You’ll need to assess data flows, connectivity patterns, and fallback scenarios.
Timing Risk: The closer you get to April 2026 without starting, the more compressed your timeline becomes. If you encounter issues during testing or deployment, you’ll have less runway to resolve them.
A: Citrix has published detailed documentation on the LAS migration process, including technical guides for each product. Your Citrix account team should be your first point of contact for guidance specific to your environment.
Additionally, Citrix partners with expertise in migration planning can help assess your environment, develop a detailed migration plan, and execute the transition with minimal risk.
The transition to LAS represents a significant shift in how Citrix handles licensing, but with proper planning, it can be executed smoothly without disrupting your business operations. The key is starting now—not next year.
Create your inventory, assess your upgrade requirements, engage your network and security teams, and build a realistic timeline. Organizations that approach this methodically and start early will have the smoothest transitions.
If you need assistance with planning or executing your LAS migration, don’t hesitate to reach out. This is a deadline you don’t want to miss.
French 
English 
Hindi 