-
-
-
-
-
about_Broker_Licensing
-
-
-
-
-
-
-
-
-
-
-
This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
about_Broker_Licensing
Topic
Citrix Broker - Licensing
Short Description
Overview of broker licensing configuration.
Long Description
As part of the licensing setup for a site, the types of product licenses used by the broker when creating connections to virtual desktops or applications can be configured using the Central Configuration Service SDK.
The following licensing related properties can be specified using the Set-ConfigSite cmdlet:
- LicensingModel - Sets the licensing model to use. Values can be ‘Concurrent’ or ‘UserDevice’.
- ProductCode - Specifies which product license is supported by the site. Values can be ‘MPS’ for XenApp licenses or ‘XDT’ for XenDesktop licenses.
- ProductEdition - Sets the licensing edition to use.
A license matching the specified model, product code, and edition must be available within the site’s license server in order for the broker to grant licenses.
These properties are part of the site object returned by the Get-ConfigSite cmdlet.
Concurrent License Model
A concurrent license is tied to a XenDesktop session. When a user launches a session, a license is checked out to that session. When a user logs off from a session, the license is checked back in again, making it available for another session.
User Device License Model
With user device licensing, the license server automatically assigns licenses to users or devices based on usage:
- User licensing allows users to access their desktops and applications from multiple devices.
- Device licensing allows multiple users to access their desktops and applications from a single device.
When users or devices connect to an application or desktop, they consume a license for a 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. A license assignment can be manually ended before the 90-day period elapses using the udadmin command line installed on the license server.
Licensing State
The broker site contains the following properties related to licensing state:
- LicensingGracePeriodActive - Reports if the broker is in licensing grace period.
- LicensingOutOfBoxGracePeriodActive - Reports if the broker is in out-of-box grace period.
- LicensingGraceHoursLeft - The number of grace hours remaining, if the broker is in grace period, else it is null.
- LicensedSessionsActive - The number of active, licensed sessions.
- LicenseGraceSessionsRemaining - The number of concurrent grace sessions available for the site Product Code, if the broker is in licensing grace period, else it is null.
These properties are part of the site object returned by the Get-BrokerSite cmdlet.
License Server Test
The broker SDK cmdlet Test-BrokerLicenseServer checks whether or not a given server can be used as a license server by the broker.
Resetting License Server Connection
The broker SDK cmdlet Reset-BrokerLicensingConnection resets the broker’s connection to the license server.
License Burn-In Date
The version of the product that is supported within the site is denoted by a licensing burn-in date. This date can be accessed through the LicensingBurnInDate field of the site object returned by the Get-ConfigSite cmdlet.
See Also
Share
Share
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Citrix product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.