Product Documentation

About Citrix Licensing

Mar 13, 2015

Version 11.10

What's New

Citrix License Server VPX. A self-contained Linux-based virtual appliance that allows you to easily deploy licensing in your Citrix environment. You can bring the appliance online by:

  • Importing the appliance to your host or pool of hosts.
  • Configuring basic networking - specifying IP address, hostname, and other network information.
  • Using the License Administration Console to upload licenses for your hosts.

Microsoft Active Directory support for Windows license servers - The License Administration Console supports Active Directory Users and Groups. During installation, the license server detects Active Directory membership. If you are in a domain, the license server adds the installing user (domain\user) as a default License Administration Console administrator. In a workgroup or VPX installation, the license server prompts for the default admin user password.

Fixed Issues

  • The Citrix License Server might crash immediately after startup. Workaround: Delete the following files, and then start the license server. These files are automatically regenerated when the license server starts. [#253576]

    C:\Program Files\Citrix\Licensing\ls\conf\activation_state.xml and concurrent_state.xml on a 32-bit server

    C:\Program Files(x86)\Citrix\Licensing\ls\conf\activation_state.xml and concurrent_state.xml on a 64-bit server

    /opt/citrix/licensing/LS/conf/activation_state.xml and concurrent_state.xml for License Server VPX

  • If you select Use default port when configuring the Vendor Daemon Port, critical alerts might appear on the Dashboard when you close the console and restart the license service. If this occurs, you cannot use a random port. Workaround: Specify a new installation path that does not include parentheses in the pathname. Windows only [#0266589]

Known Issues

This section contains:

Contents

  • Installation Issues - Windows Only
  • Other Known Issues - Windows Only
  • Other Known Issues and Considerations - License Server VPX Only
  • Other Known Issues - Windows and VPX
  • License Files
  • Event Log Viewer Messages
  • Product-Specific Issues

Installation Issues - Windows Only

  • Windows Firewall exception rules for Licensing components are not automatically created on Windows Server 2003 (32-bit and 64-bit), as expected. If Windows Firewall is enabled when you install Citrix Licensing 11.10, you cannot connect remotely to the License Administration Console and licenses cannot be checked out. If you enable Windows Firewall, create exceptions for Licensing components on the Exceptions tab of the Windows Firewall panel. Create an exception for each of the following: CITRIX.exe and lmadmin.exe. This issue occurs with Windows Server 2003. [#232674]
  • If Citrix Licensing is installed in a clustered environment and Windows Firewall is enabled (the default configuration for Windows 2008), connections can fail. Connecting remotely to the console or checking out licenses works until failover occurs in the cluster. Exception rules for CITRIX.exe and lmadmin.exe are created during installation of Licensing, but do not work after a cluster failover. To work around this issue, create exceptions for Licensing components on the Exceptions tab of the Windows Firewall panel. Create an exception for each of the following ports: Console Web Server port (default port is 8082); License Server Manager port (default port is 27000); and Vendor Daemon port (default port is 7279). This issue occurs with Windows Server 2008 (32-bit and 64-bit) and Windows Server 2008 R2. For more information, see http://support.microsoft.com/kb/2568645[#232365]
  • At the end of installation, the "License Server Configuration" tool is presented. If you choose to cancel on this page, the license server does not start. You must reopen the License Server Configuration tool and finish the settings before the license server can start. You can open the tool from: C:\Program Files\Citrix\Licensing\LS\resource\LSPostConfigTool.exe.
  • During installation, localized characters in the installation path can cause the installation to fail. Accept the default installation path or enter only ASCII alphabetic letter characters for the installation directory. [#229456]
  • When configuring the product-side setting for the license server name, do not use localhost. Use the host name, IP address, or FQDN instead. [#165986]
  • The Citrix License Server might stop during installation on Windows 2003 x86 and x64. Workaround: Install all the Microsoft Service Packs and updates. [#32050]

Other Known Issues - Windows Only

  • If you include a backslash in a locally managed user name (for example, test\), you cannot delete the user. [#0270349]
  • Changing the licensing port after licenses are installed might cause the No such product or vendor exists: CITRIX message to appear on the Dashboard instead of the installed licenses. [#0269423]
  • When a locally managed user having an administrator role does not exist, a domain administrator can only add domain users or groups as administrators to the license server. To edit and delete domain administrators or groups on the User Configuration page in the License Administration Console, a Locally Managed User having the Administrator role must exist. [#0263016 and #0269719]

Other Known Issues and Considerations - License Server VPX Only

  • You cannot import licenses containing a parentheses in the pathname. [#0264908]
  • Though XenDesktop 5 Service Pack 1 through XenDesktop 5.6 are compatible with License Server VPX, you cannot use the Desktop Studio to view or manage licenses. Use the License Administration Console.
  • If you do use Desktop Studio to initially point XenDesktop to the License Server VPX, the following condition might occur - CtxLSPortSvc is consuming 100% CPU on VPX. If this happens, restart the licensing support service by logging onto the License Server VPX console as root. Within the shell, execute /etc/init.d/citrixlicensingsupportservice restart.
  • Clustered license servers are not supported for VPX. You can use the High Availability (HA) feature on XenServer 5.6 - 6.0.
  • Though /opt/citrix/licensing/LS/conf contains a self-signed SSL certificate and .key file, you can generate and use your own.
  • Ports 1-1024 are reserved by the operating system. When configuring the VPX ports, use ports above 1024. If you use SSL, use port 10443, which is open in the firewall. If you choose a different port for SSL, reconfigure the firewall in the iptables.
  • Upgrades are not supported for License Server VPX.
  • The License Server VPX does not support Active Directory.

Other Known Issues - Windows and VPX

  • In the License Administration console, localized characters in user names and passwords can display with unexpected results. To avoid this issue, use US-ASCII alphabetic letter characters for user names and passwords in the License Administration Console. [#0272738, #0273089, #0156833, #0156839, #0156969, #223870, #242767]

License Files

  • Certain license types are not covered by Subscription Advantage and therefore appear in alerts in the Dashboard of the License Administration Console indicating that the Subscription Advantage date is expired. You can ignore such alerts for any license not covered by Subscription Advantage. This includes Evaluation licenses, Not for Resale licenses, Early Release licenses and Technology Preview licenses. These types of licenses do not need Subscription Advantage and your Citrix products do not stop working when the Subscription Advantage date is expired. You can verify the status of any license for which you receive an alert by clicking the license on the Dashboard. The license information expands to show the license type (such as Technology Preview), the license expiration date, and the Subscription Advantage date. [#231847]
  • License Files with multiple lines referencing HOSTNAME= are ignored by the license server. Licenses in these files cannot be checked out. This issue is caused when you download licenses associated to different license server hostnames into the same license file. Any of the following error messages might appear in the Event Log Viewer:
    • Event ID: 724 Description: (2196) Invalid license key.
    • Event ID: 764 (2196) Wrong hostid on SERVER line in license file.

    In addition, the License Administration Console displays the following error message: "…Error List Returned…Unknown Host."

    To resolve this issue, re-download separate license files for each Citrix product tied to different license server names.

  • After you replace evaluation license files on the license server with new license files, the Citrix product might continue to display the following license expiration message when users log on: "Warning: The following Citrix Product is using an Evaluation license. This license will expire in…"

    To resolve this issue:

    1. Remove the old evaluation license files from the license server. (See Deleting License Files.)
    2. At the license server, restart the Citrix Licensing service.
    3. At the Citrix product server, point to a fictional license server and then point the product back to the actual license server. (See your product's administrator's guide for information about changing these settings.)
    4. If the problem persists, restart the product server.

Event Log Viewer Messages

  • The following message appears in the Event Log Viewer: (1224) Client/server comm version mismatch. The client and server programs are running potentially incompatible versions of FLEXnet comm software.

    This is an informational message indicating that a Citrix product licensing client is communicating with a different version of the Citrix License Server. Ignore this message.

  • After upgrading the license server, messages such as the following examples might appear in the Event Log Viewer (product and component numbers may vary from these examples):
    • Detection of product '{8AAA9207-A30A-4158-9640-8886AA9BD86F}', feature 'CTX_LS', component '{F826569F-BFB0-4D4F-9B01-341070F968D5}' failed. The resource 'C:\bin\CfgEngine\Configuration.xml' does not exist.
    • Detection of product '{B91F5D65-61AD-48C6-B595-71F58844529C}', feature 'CTX_LS' failed during request for component '{FB1869D6-3FE1-446B-AF01-3858F849CDA5}'
    • Detection of product '{B91F5D65-61AD-48C6-B595-71F58844529C}', feature 'Complete', component '{303994BA-6487-47AE-AF1D-7AF6088EEBDB}' failed. The resource '' does not exist.
    • A provider, MgmtEventProv, has been registered in the Windows Management Instrumentation namespace Root\Citrix\Management to use the LocalSystem account. This account is privileged and the provider may cause a security violation if it does not correctly impersonate user requests.
    • Failed to connect to server. Error: 0x80070005.

    Ignore these messages. The upgrade is successful. [#207927, #183919]

Product-Specific Issues

Access Essentials / XenApp Fundamentals

  • After installing Licensing 11.10 and starting the Quick Start tool, a .NET Framework error message indicates that “The service object for the service “CitrixLicensing” could not be acquired. Probably not installed or there is a permission problem.” This issue occurs in Access Essentials 2.0 or XenApp Fundamentals 3.0. To resolve the issue, uninstall Licensing 11.6.1 Build 10007 and install Licensing 11.6.1 Build 9020, available from the License Server Downloads page. [#232048]
  • Before installing the license server version 11.10 on systems running Access Essentials 2.0, you must install Hotfixes AEE200W2K3001 and AEE200W2K3002. Failure to do so might render Access Essentials inoperable.

Citrix Branch Repeater with Windows Server

  • If you install the same license twice, the second time may trigger a change in the Send Bandwidth Limit, which will be set to the maximum licensed speed. To solve this issue, do not install the same license twice. If you must do so, verify that the Send Bandwidth Limit is set correctly. [#53894]

Citrix MetaFrame Access Suite 3.0

  • Upgrading licensing from Citrix MetaFrame Access Suite 3.0 to a newer version of licensing. During the upgrade process of the license server, the licensing components are detected as installed but there is a prompt to remove them. You cannot upgrade licensing in a Citrix product that has licensing 1.0.0 installed as it is incompatible with the licensing that is used in Citrix products today. Uninstall the licensing components and reinstall the latest version. [#217704]

Citrix XenApp Management Pack

  • Details about the Citrix License Server are always blank on the Monitoring tab of the System Center Operations Manager for Citrix Managed Servers. There is no workaround for this issue. [#192159]

Finding information for your version of licensing

See the tables below for a list of license server versions and their associated documentation.

Important: Citrix does not provide hotfixes for license server components and does not support older license servers with newer products. The latest versions of the license server often contain resolutions to issues appearing in earlier versions. When you upgrade or install new Citrix products, upgrade the licensing components as well. New license servers are backward compatible and will work with older products and license files; however, new products often require the newest license server to check out licenses correctly. You can find the latest version from the Citrix Downloads site.

To find your license server version number

If you are unsure if your license server version is current, you can verify it by comparing your version with the number on the Downloads site.

On a license server with the License Administration Console:

  1. Start the License Administration Console from the programs menu: Citrix > Management Consoles > License Administration Console.
  2. Click Administration and select the System Information tab. See the release version in the information list.

On a license server without the License Administration Console:

  1. Open the Registry Editor (Start > Run > regedit).
    Note: Use Registry Editor to view the license server information only. Editing the Registry can cause serious problems that may require you to reinstall your operating system.
  2. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\LicenseServer\Install.

    The version number appears in the Version key in the format: 11.12.1.0 build 14100.

    On servers running Windows 2008 Server 64-bit the registry key is

    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\LicenseServer\Install