License Compliance Center
Last Revised March 27, 2019
License Compliance is a top priority for us at Citrix and should be with all of our customers. The Citrix License Compliance Center provides relevant information regarding license compliance and the associated rules regarding the deployment and use of Citrix products.
Explore helpful information related to product license compliance
Right to audit language in end-user license agreement (EULA), end-user service agreement (EUSA), and Cloud Service Level Agreement (SLA):
Citrix maintains an audit right with respect to your use of Citrix product licenses. Any audit may be conducted remotely or on your premises and shall not unreasonably interfere with your business activities. Citrix may perform the audit or use a third-party agent, such as an independent certified public accounting firm. Citrix shall not audit you more than once per calendar year. You must reasonably cooperate, and, without prejudice to other rights of Citrix, address any non-compliance identified by the audit, including, but not limited to, promptly paying any license or Maintenance fees owed.
Excess license usage will be determined based on your peak license deployment and will be billed to you at the then-current Citrix suggested retail price, including Maintenance for the lesser of the duration of the excess license usage or two years, as well as Maintenance determined to be due on any other licenses. If the audit reveals an underpayment of ten percent (10%) or more of total fees owed for the review period, or any other material breach of the Product License Agreement, you agree to also reimburse Citrix for its reasonable audit expenses.
Citrix and its agent will protect confidential information obtained during the performance of the audit by using the same degree of care as Citrix uses to protect its own information of a like nature, but no less than a reasonable degree of care, to prevent its unauthorized use, disclosure, dissemination, or publication. Citrix and its agent shall not have an obligation to maintain the confidentiality of information (i) received rightfully from a third party prior to the audit; (ii) you have disclosed to a third party without any obligation of confidentiality; or (iii) is independently developed by Citrix or its agent. You agree that you will not require any additional confidentiality or non-disclosure agreements to be implemented by Citrix or its designated third-party agents in relation to the audit.
This audit right is incorporated by reference into the Product License Agreement and Maintenance Program and these audit terms will be updated periodically.
Our wide range of product editions, licensing models and maintenance plans ensures you can find the right purchase options for your organization.
Licenses for this product must be run on a dedicated license server(s) for this product alone. All components of this product are licensed only to the same User (you may not authorize different Users for each component). Licenses for this product cannot be used or interchanged with licenses for components of this product sold as stand-alone products.
Licenses for this product must be run on a dedicated license server(s) for this product alone. Only those consuming Concurrent licenses for Citrix Virtual Apps and Desktops (formerly XenApp and XenDesktop) may be Users of the other components of this product. You may need to purchase additional User licenses for the other components to have sufficient licenses for all such Users. Licenses for this product cannot be used or interchanged with licenses for components of this product sold as stand-alone products.
Explore the Citrix Virtual Apps and Desktops (formerly XenDesktop and XenApp) licensing FAQ
How does Citrix define concurrency for Citrix Virtual Apps and Desktops (formerly XenApp and XenDesktop)?
With the Citrix Virtual Apps and Desktops concurrent model, users are anonymous and a license is consumed by each concurrent user to one or more apps and/or virtual desktops. A licensed concurrent user is an anonymous, floating user only licensed for the period during which access to the Citrix environment is required. Once access is terminated by the anonymous user, the license is immediately returned to the license pool and available for another anonymous user to consume.
How does Citrix define a licensed user of Citrix Virtual Desktop (formerly XenDesktop)?
With Citrix Virtual Desktop, a licensed user simply requires a unique user ID, typically an Active Directory entry, or the equivalent. There is no requirement to manage a separate or specific list of authorized users. If multiple users are sharing the same user ID, they will each require a Citrix Virtual Desktop user license. If a user connects to their desktop(s) and/or apps with multiple devices (e.g. desktop PC, laptop, netbook, smartphone and/or thin client) the user needs just one Citrix Virtual Desktop user license, even if all of the user’s devices are connected to one or more instances of Citrix Virtual Desktop simultaneously.
How does Citrix define a licensed device for Citrix Virtual Desktop (formerly XenDesktop)?
With Citrix Virtual Desktop, a licensed device simply requires a unique device ID. Under the device model, a device is any piece of equipment authorized by the customer to be used by any individual(s) to access instances of Citrix Virtual Desktop. For a shared device, like a classroom workstation, or a clinical workstation in a hospital, a single Citrix Virtual Desktop device license can support multiple users.
(Number of total users) – (number of users that only access via shared devices) + (number shared devices) = total number of licenses to buy
What happens if a licensed user of Citrix Virtual Desktop (formerly XenDesktop) exits my organization?
If an existing licensed user leaves a customer’s organization, the customer has the right to release the departing user’s license without notifying Citrix. The release of the licenses is done using the “udadmin” utility. If the administrator does not use the utility to release the license, the license server will automatically release any license after 90 days of inactivity. Customers are prohibited from using the “udadmin” utility to release all licenses, also known as “cache clearing.”
What is the license overdraft feature?
The Citrix Virtual Desktop (formerly XenDesktop) license overdraft feature is specific to user/device license model deployments ONLY and allows a limited number of additional user licenses to be provided to support temporary spikes in demand. Any overdraft licenses used must be purchased within 30 days of first use. Citrix reserves the right to remove any overdraft feature in new product releases.
How do I get overdraft licenses?
Citrix Virtual Desktop User/Device (formerly XenDesktop) customers will automatically receive 10% Citrix Virtual Desktop overdraft licenses when they allocate their Citrix Virtual Desktop User/Device licenses after purchase. Overdraft licenses are available for use when all licenses are allocated. Overdraft usage is reported within Studio.
How can I identify license overdraft?
The license overdraft count will be displayed in a separate column within the License Administration Console. Please note the installed column will display both the purchased license total plus the associated overdraft total. Overdraft usage is also visible in Studio.
What happens when a license is consumed from the overdraft feature?
A license is assigned from your installed licenses to enable access to your Citrix Virtual Desktop (formerly XenDesktop) environment. This overdraft license provides the same level of access and functionality as your other edition specific licenses.
How do I license my disaster recovery site?
The same licenses that are provided for your production environment can be used to support your disaster recovery environment. This requires your disaster recovery environment to be configured and managed independently of your production environment. Please note the license server in your disaster recovery environment must have an identical hostname to the license server in your production environment. At no time does Citrix allow customers’ usage to exceed license entitlement.
Can both Production and Disaster Recovery servers run simultaneously?
No, disaster recovery servers should only be used when the production server is not in use or during disaster recovery testing.
Can you define the different configurations of Disaster Recovery sites?
Hot Site (Active/Active)
A second, active license server that mirrors the production license server in the quantity of licenses deployed.
Warm Site (Active/Warm)
A second license server with Citrix Licensing, but no license files are installed or available for use and no license files are being read by the license server. Alternatively, license files can be installed with services disabled.
Cold Site (Active/Passive)
A second, passive license server that mirrors the production license server, but is powered down unless there is a disaster or test scenario
You may deploy network architectures that use hardware or software to reduce the number of Users or Devices that directly access the product server software or service. This is referred to as multiplexing or pooling. This does not reduce the number of licenses required to access or use the server software or service under either license model. A license is required for each User or Device that is connected to the multiplexing or pooling software or hardware front end. You must acquire and assign a license to each User or Device that accesses instances of the server software or service directly or indirectly, frequently or infrequently, even if the authorized User or Device is an automaton.
NetScaler license files are to be installed on the designated appliance (or virtual machine). License files are prohibited from being installed anywhere other than the designated appliance or virtual machine.
With respect to an audit under the end user license terms, excess license usage will be determined based on peak license deployment and billed at the then-current Citrix suggested retail price for licenses and for maintenance on those licenses (for the lesser of the duration of the excess usage or two years). Charges for any additional findings, as well as audit fees, may apply.
With respect to your purchase of a product trade-up or upgrade, or your implementation of a product release with new product licenses under Maintenance, you are permitted a 90 day grace period to run both your new and the old product licenses in production. This period runs from your purchase of the trade-up or upgrade, and from your download of the new release under your maintenance program. You agree to destroy the old licenses and retain no copies after the grace period.
In order to receive Customer Success Services (CSS) benefits, customers must have active CSS for 100% of its licenses within one product line* and under a single ORG ID. This is known as the “All-in Rule.”
Partial CSS coverage within a product line* is not permitted. If the customer has licenses that are no longer in use, they have the option to permanently rescind such licenses in order to exclude these from pool of licenses for which CSS is being purchased. License transfers to new or existing ORG IDs, for the purpose of avoiding the All-in Rule is not permitted. A customer is not permitted to extend the benefits of CSS to any licenses that do not have an active CSS agreement.
Customers should only deploy the license keys for assets that are maintained on active support.
*Product line is defined as any license group (Virtual Desktop, Virtual App, Workspace, and Endpoint Management/ XenMobile and any edition of these) that is in production.
When customers upgrade from one edition to another within the same product line, they are no longer entitled to the previous editions. An upgrade is when moving from one edition to another and a trade-up is when a customer trades in an old standalone product for a new product and/or bundle. Please refer to the rules contained in the “Grace Period” section under the "On-premise product and license models" tab.
Customers are prohibited from using Proof of Concept (PoC) and/or trial licenses in a production environment or for multiple terms beyond the initial expiration of the PoC or trial licenses, unless approved in writing by Citrix.