Product Lifecycle Support Policy
While Citrix strives to produce the best quality software, it is virtually impossible to test against all scenarios and software environments. Occasionally, issues may arise which impact product performance or functionality. Customers should address these situations through the technical support programs described in the Support Programs and Services section of the Citrix web site.
Citrix lets you choose the right technical support program for your needs, with options including free web-based tools, our extensive network of solutions providers and technical support directly from Citrix.
The goal of Citrix support programs is to provide our customers with the tools and knowledge needed to identify any technical issue they have experienced. Once identified, Citrix may recommend the next steps required to resolve or prevent the issue. This may include recommendations to apply configuration changes, existing product updates or upgrades. In some situations, Citrix may determine that an escalation is required in order to further isolate the issue and potentially resolve it with a new product update. Your Citrix support representative will tell you the appropriate steps to resolve technical product issues.
For the purpose of this policy, the following support definitions apply:
- General troubleshooting of a specific issue to isolate potential causes
- Issue resolution through applying configuration changes, existing product updates or upgrades
- Resolving an issue through product code modification
- Typically delivered via product update or upgrade
- If a subsequent release contains the fix, the customer may be required to the upgrade to the new release
Citrix products progress through lifecycle phases
When Citrix initiates a product or release through lifecycle phases, an announcement is made on the Notice of Status Change (NSC) date and the Product Matrix Table is updated to include the specific dates for each phase. For definitions of the various lifecycle dates, refer to Lifecycle Definitions.
The Product Lifecycle Support Policy is intended exclusively for the benefit of Citrix customers with respect to theĀ perpetual and subscription license software, appliance and Saas products they purchase. It is not intended to benefit any third parties or apply to any third party products. Citrix reserves the right to make changes to its Product Lifecycle Support Policy, for all products or a particular product, at its sole discretion, from time to time, as business needs require, without notice. The Product Lifecycle Support Policy web pages will be updated with respect to any changes as of their effective date.
Lifecycle phases for products
Last updated: August 1, 2022
To help you plan and prepare for your product, maintenance and support needs, this page describes the key lifecycle phases and support policies in the product lifecycle.
Lifecycle milestones definitions
The date that signifies when a new product release may be ordered and fulfilled in all applicable languages, discount programs, delivery methods, and worldwide geographies.
With GA of a new release, some applicable offerings of the previous release will be phased out:
- Evaluations and Not for Resale offerings based on the previous product release will be replaced by offerings based on the new release.
- Downloads of the product release will remain available until the End of Life (EOL) date.
The date that signifies when a specific software or appliance release will no longer be available for purchase. EOS does not include the end of availability of a particular license model provided the software or appliance release remains available for purchase under other license models.
For the majority of Citrix products which incorporate a date based license model, the EOS date is generally not applicable since new connection licenses work with previous product versions. In the event that a product line under a date-based license model is being brought through End of Life (EOL), there will be a minimum 90 days notice of the EOS date.
Citrix products that have been added to the portfolio via an acquisition, or that have yet to transition to the date based license model, will typically offer a licensing method that associates connection licenses to the product version. In these cases, there will be a minimum of 90 days notice of the EOS date.
The 90-day notice period gives customers the opportunity to purchase additional licenses to allow for growth while they plan for a version upgrade or deployment of a new release.