Product Documentation

Types of licenses

Mar 16, 2015

Your product uses one of the following types of licenses (some products allow you to choose more than one type). It is important that you are aware of which types of licenses your company has purchased and how they are consumed. This ensures that you do not run out of licenses. The license types are:

User/Device licenses

With XenDesktop 5 Service Pack 1 or later and XenApp 6.5 or later, the license server can assign licenses to a user or a device and monitor license consumption. When assigned to a user, the license allows access from an unlimited number of devices. When assigned to a device, the license allows access from the device by an unlimited number of users.

A licensed device requires a unique device ID and is authorized for use by any individuals to access instances of XenDesktop. Use this type of license for shared devices, such as classroom or hospital.

A licensed user requires a unique user ID, such as an Active Directory entry. When assigned to a user, the license allows the user to connect to their desktops and applications with multiple devices, such as desktop computer, laptop, netbook, smartphone, or thin client. A licensed user can connect to multiple instances of XenDesktop concurrently.

When users or devices connect to an application or desktop, they consume a license for the 90 day license assignment period. The assignment period begins when a connection is made, is renewed to the full 90 days during the life of the connection, and expires (allowing reassignment) 90 days after the last connection terminates (logs off or disconnects). If you have to manually end a license assignment before the 90 day period elapses (for example, an employee consuming a User license leaves the company), use the udadmin command line tool.

Optimization

Using the optimization process, the License Server determines how to minimize consumption based on users and connections. The license server optimizes every 5 seconds until there are 5000 unique connections. At 5000 unique connections optimization occurs every 5 minutes, which might delay status information until the next optimization impacting when license usage statistics are updated in various consoles..

Examples of unique connections - Note that optimization is not consumption and these examples show when optimization occurs.

Optimization occurs every 5 seconds for 1-4999 uses and every 5 minutes for 5000 or more uses.

700 users * 1 device each = 700 (optimize every 5 seconds)

5000 users * 1 device each = 5000 (optimize every 5 minutes)

5000 devices * 1 user each = 5000 (optimize every 5 minutes)

2500 users * 2 devices each = 5000 (optimize every 5 minutes)

Note: Optimization can be CPU intensive depending on the number of unique connections. Citrix recommends using machines with multiple cores if you have an extremely large deployment.

Concurrent licenses

This type of license is not tied to a specific user. When a user launches a product, the product requests the license and it is checked out to the specific computer or device that the user is using. When the user logs off or disconnects from the session, the license is checked back in and is available for another user. Using this logic, keep the following scenarios in mind:

  • Multiple sessions at different computers use multiple licenses. Each time a user launches a Citrix session from a different computer or device, a license is checked out until the user closes the session at that computer or device (at which point the license is checked back in). For example, if a user launches a session from one computer and then launches another from another computer (before closing the session on the first), two licenses are checked out.
  • Because, license servers do not communicate with each other, if you are running multiple license servers you may consume more than one license (for example, with load balancing). If you are using load balancing, Citrix recommends that the product servers point to the same license server.
  • Different editions consume different licenses. If a user connects to an application published on a computer running Advanced edition and then uses the same client to connect to an application published on a computer running Enterprise edition, two licenses are consumed.
  • Only one license is consumed when a user makes multiple connections from a single device to different product servers configured as the same edition and pointing to the same license server.
  • When a user connects from a single device to two product servers that are the same edition but different versions, one or two licenses might be consumed based on the order in which the user makes the connections. For example, the two servers are XenApp 6.0 and XenApp 6.5 (though this applies to nearly all Citrix products and versions):
    • The user connects to XenApp 6.0 first - Two licenses might be consumed - An older license first and then a newer license.
    • The user connects to XenApp 6.5 first - Only one license is consumed.
  • RDP connections consume a license (RDP connections to a console do not consume a license).

Per user licenses (Only user licenses - not the same as User/Device licenses)

A licensed user requires a unique user ID, such as an Active Directory entry. When assigned to a user, the license allows the user to connect to their desktops and applications with multiple devices, such as desktop computer, laptop, netbook, smartphone, or thin client. A licensed user can connect to multiple instances of a product concurrently. When users connect to an application or desktop, they consume a license for the 90 day license assignment period. The assignment period begins when a connection is made, is renewed to the full 90 days during the life of the connection, and expires (allowing reassignment) 90 days after the last connection terminates (logs off or disconnects). If you have to manually end a license assignment before the 90 day period elapses (for example, an employee consuming a User license leaves the company), use the udadmin command line tool.

Per device licenses (Only device licenses - not the same as User/Device licenses)

A licensed device requires a unique device ID and is authorized for use by any individuals to access instances of a product. Use this type of license for shared devices, such as classroom or hospital. It allows an unlimited number of users per device. When devices connect to an application or desktop, they consume a license for the 90 day license assignment period. The assignment period begins when a connection is made, is renewed to the full 90 days during the life of the connection, and expires (allowing reassignment) 90 days after the last connection terminates (logs off or disconnects). If you have to manually end a license assignment before the 90 day period elapses (for example, an employee consuming a User license leaves the company), use the udadmin command line tool.

Per socket licenses

Licenses are consumed per CPU socket actually used by a CPU and cores are not counted. For example, if a computer with two CPU sockets has only one CPU, only one license is used. In another example, if that same computer with two sockets has two CPUs, each with a quad core, only two licenses are used.

Named user licenses

When a product requests a license, it is checked out to the user until a preconfigured period of time expires. This type of check-out is not tied to a computer or device; once the license is checked out, the user can run multiple sessions on different computers without checking out more licenses.