Product Documentation

FAQ for Licensing

May 22, 2017

These questions are asked frequently about your licensing environment.

Can I rename the license server?

License files run only on the license server for which they were made. More specifically, license files contain the hostname or binding identifier of the license server you specify when you allocate the licenses. You cannot use the license file that you generated, which specifies a particular license server name, or a MAC address (in the case of an appliance.), with a different license server name or appliance.

Create license files that reference the new server name or MAC address by reallocating and generating the new file on citrix.com.

If I upgrade my license server does it affect my license files?

No. The license server and all product licenses are fully backward compatible and do not introduce any issues into your environment.

Can a single license server supply licenses to users connecting from different servers using different product editions?

Yes. One license server can contain licenses for multiple editions of a Citrix product. The type of license checked out corresponds to the edition that is configured on the product server. A product server is configured to consume an edition of a license and checks out that edition of a license.

For example:

ProductServerA is configured to check out Enterprise licenses.

ProductServerB is configured to check out Platinum licenses.

LicenseServer1 contains both Enterprise and Platinum licenses.

  • Users who connect to LicenseServer1 from ProductServerA check out Enterprise licenses only. After the number of Enterprise licenses on LicenseServer1 is exceeded, new requests from ProductServerA users are denied until existing Enterprise connection licenses are released.
  • Users who connect to LicenseServer1 from ProductServerB check out Platinum licenses only. If the number of Platinum licenses on LicenseServer1 is exceeded, new requests from ProductServerB users are denied until Platinum connection licenses are released.

Note

License checkout times might increase if many product servers with many users are contacting the same license server simultaneously. One license server can accept only 10,000 inbound TCP/IP requests at one time. If you are planning to have more than 10,000 Citrix product servers (XenApp, XenDesktop, Delivery Controllers, Appliances) connecting at the same time, we recommend that you use several license servers.

Examples of Possible Deployments:

Scenario 1: Two farms

  • FarmA contains product servers configured for Enterprise edition
  • FarmB contains product servers configured for Platinum edition
  • One license server (shared)
  • User1, User2, User3, User4...User5000 connect only to FarmA
  • User5001, User5002, User5003...User10000 connect only to FarmB

Scenario 2: One farm

  • The farm has two sets of published applications
  • Product servers configured for Enterprise edition host one set of applications 
  • Product servers configured for Platinum edition host one set of applications 
  • One license server (shared)
  • User1, User2, User3, User4...User5000 connect only to product servers that have the first set of applications
  • User5001, User5002, User5003...User10000 connect only to product servers that have the second set of applications

Differences in License Server version numbers

The License Administration Console and the Windows Programs and Features display different version numbers, but they display the same build number to aid in identification.

localized image

We use two different versioning systems for our licensing technology:

  • The License Administration Console and the registry version key use the License Server version plus an internal build number (11.13.1 build 16002 in the previous graphic).
  • Internally and for the MSI, we use the Licensing SDK version and our build number (11.1.0.1 build 16002 in the previous graphic).

To avoid confusion, we recommend using the License Administration Console or registry to find your correct version number. For more information, see Finding information for your version of licensing.